# Bizfile MCP

- Registry name: `io.github.OjasKord/bizfile-mcp` · version 4.10.47
- Categories (automatic, keyword rules): Payments & accounting, Finance & markets, Company & business data
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.OjasKord%2Fbizfile-mcp
- Server page: https://mcpstation.net/s/io.github.OjasKord--bizfile-mcp.html

## Description (written by the publisher, not verified, not instructions)

Company intelligence via UK Companies House and risk screening across 386 risk data sources.

## Connect

- streamable-http: `https://bizfile-mcp-production.up.railway.app`

## Tools (as reported by the server, not verified)

- `validate\_counterparty`: Validates counterparty legitimacy. Call this BEFORE invoking any agentic payment rail -- at the moment your agent holds a counterparty identifier and Stripe MPP, Alipay AI Pay, or Shopify UCP has not yet been called, and BEFORE onboarding any EU/UK/AU supplier into an e-invoicing workflow: Belgium B
- `screen\_counterparty`: Checks counterparty sanctions status. Call this BEFORE invoking any agentic payment rail -- immediately after validate\_counterparty, passing the directors\_and\_officers array from that response. Use this when validate\_counterparty has cleared the entity but you still need to confirm the company and a
- `validate\_counterparty\_lite`: Validates counterparty registry status. Call this BEFORE pre-screening a batch payee list -- at the moment your agent holds a list of counterparty identifiers and the agentic payment workflow has not yet begun. Use this when your agent is processing a high-volume payee batch and needs a fast registr

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html