All servers · Payments & accounting · Company & business data

Bizfile MCP

io.github.OjasKord/bizfile-mcp · v4.10.47

No registry update 90+ days

Measured by MCP Station

Last check	Reachable
Checked at	—
Check success 7 / 30 days	—
First-try success 30 days	—
Median response	—
Lookups 30 days	—
Authentication	No auth
MCP version	2024-11-05
Rank score	—
Declared risk	Not declared (tools carry no read/destructive hints)
Capabilities declared	prompts, resources, tools
Tool definitions	3 tools · with description 100% · input schema is an object 100% · read/destructive hints 0%

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

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

claude mcp add --transport http bizfile-mcp https://bizfile-mcp-production.up.railway.app

{
  "mcpServers": {
    "bizfile-mcp": {
      "url": "https://bizfile-mcp-production.up.railway.app"
    }
  }
}

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

Repository · Website · JSON · Text for agents · Registry updated 2026-06-25