Bizfile MCP

io.github.OjasKordPublished by GitHub account OjasKordv4.10.47Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableFinanceSecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

Checks business counterparties against UK Companies House and sanctions lists, with AI risk scoring, before an agent approves or pays a supplier.

What you can do
  • Validate a counterparty's registry status and legitimacy, with AI risk scoring
  • Run a fast registry-only check for high-volume payee batches
  • Screen a company and its directors and officers against sanctions and risk data sources
  • Return officer details that feed into the sanctions screening step
When to use it
Use it when an agent handles supplier onboarding, payment approval or AML/KYC due diligence and needs live company registry and sanctions data rather than model memory. It is meant to run before calling a payment rail or adding an EU/UK/AU supplier to an e-invoicing workflow.
Requirements
A remote endpoint or the local npm package over stdio. An Anthropic API key is required as the ANTHROPIC_API_KEY environment variable for AI-powered risk scoring. Screening calls are paid; the free tier allows 20 calls per month.
Before you install
Screening is a paid tier and pay-as-you-go queries are metered, so usage can cost money. The server sends counterparty identifiers and officer names to external sources (UK Companies House, OpenSanctions) and to Anthropic for scoring. Results are risk signals, not a compliance determination.

Installation

In SourceWeft

  1. Open Bizfile MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.OjasKord%2Fbizfile-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

Bizfile MCP — Counterparty Validator

[ToolRank]

AI-powered KYC, company verification, and sanctions screening for AI agents.

Real-time counterparty verification against UK Companies House, with AI risk scoring and risk screening against 386 risk data sources. Built for supplier onboarding agents, payment approval workflows, and AML compliance pipelines.

What This Solves

Every unverified counterparty is a liability. The most common failure points — shell companies, dissolved entities, sanctioned parties — share one signal: a company that looks legitimate but isn't. Claude and other LLMs cannot reliably check live company registry data or current sanctions lists from training data.

This tool calls authoritative sources directly:

  • UK Companies House API — live filing data, officer history
  • OpenSanctions — 386 risk data sources, updated daily

Tools

ToolFree TierUse When
validate_counterparty20/monthBefore any new supplier approval or contract
validate_counterparty_lite20/monthHigh-volume registry check, no AI scoring
screen_counterpartyPaidBefore any payment to a KYC-approved counterparty

Add to Your Agent

Claude Code — add to .mcp.json: { "mcpServers": { "bizfile": { "type": "sse", "url": "https://bizfile-mcp-production.up.railway.app/sse" } } }

LangChain: from langchain_mcp import MCPClient client = MCPClient( "https://bizfile-mcp-production.up.railway.app/sse" )

OpenAI Agents SDK: from agents.mcp import MCPServerSse mcp_server = MCPServerSse( params={ "url": "https://bizfile-mcp-production.up.railway.app/sse" } )

Pricing

TierCallsPrice
Free20/monthNo card required
Bundle 500500, never expire$20
Bundle 20002,000, never expire$70
Pay-as-you-goMetered$0.019/query (validate_counterparty), $0.008/query (lite), $0.50/screen (sanctions)

Upgrade: https://kordagencies.com

Search Terms

company verification MCP · KYC check agent · sanctions screening MCP · AML compliance tool · counterparty due diligence · Companies House API · supplier onboarding agent · payment verification MCP · OFAC screening · MAS Singapore sanctions · UK company check · corporate intelligence agent · counterparty risk scoring · AI KYC tool · know your customer API · business verification agent · supplier risk screening · AML agent tool · MCP sanctions check

Source: README.md at commit 28a9a21

Tools

3

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 B2B (active Jan 2026), France B2B (Sep 2026), Poland KSeF (Feb 2026), UK Making Tax Digital (ongoing), AU GST digital reporting (ongoing). Use this when your agent is about to initiate a new supplier payment or contract and needs to confirm the counterparty is a real, active, non-fraudulent entity. Validates against UK Companies House (api.company-information.service.gov.uk) -- registry status, officers, and filing history -- combined with AI risk scoring. Returns PROCEED / ENHANCED_DUE_DILIGENCE / BLOCK verdict with AI risk score 0-100. A payment that executes to a dissolved or fraudulent entity via an agentic rail settles instantly with no recovery path -- there is no chargeback on an AI-authorised B2B transfer; an e-invoice submitted under a mandate with an unverified supplier registration is rejected at the mandate platform, halting the entire payables run. Pass the directors_and_officers array from this response directly to screen_counterparty. One call, machine-ready verdict, no further analysis needed.

Parameterscompany_namerequiredcompany_number

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 all its officers are not on any global sanctions list, and when completing e-invoicing supplier onboarding under mandates requiring sanctions clearance: Belgium B2B (active Jan 2026), France B2B (Sep 2026), Poland KSeF (Feb 2026), UK Making Tax Digital (ongoing), AU GST digital reporting (ongoing). Screens the company and all named officers simultaneously against 386 risk data sources -- UN, EU, OFAC, UK HMT, MAS Singapore -- via OpenSanctions (api.opensanctions.org), updated daily. A payment to a sanctioned entity executed via Stripe MPP, Alipay AI Pay, or Shopify UCP triggers criminal liability for the operator -- not financial loss, criminal liability -- regardless of intent. Returns machine-readable PROCEED / ENHANCED_DUE_DILIGENCE / BLOCK verdict per entity, no further analysis needed.

Parameterscountryofficersentity_typecompany_namerequired

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 registry check to filter dissolved or unregistered entities before full validation. Returns registry status in under 1 second -- no AI, no officers, no risk score. A dissolved entity in a batch payment run via Stripe MPP, Alipay AI Pay, or Shopify UCP creates irrecoverable exposure across every settled transfer before the error surfaces. Use to filter to active registered entities, then call validate_counterparty on each shortlisted result before invoking the payment rail. Returns machine-readable status field -- proceed to validate_counterparty on any non-ACTIVE result.

Parameterscompany_namerequiredcompany_number

Version history

1
  1. v4.10.47LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts