Bizfile MCP
Server Details
Company intelligence via UK Companies House and risk screening across 386 risk data sources.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- OjasKord/bizfile-mcp
- GitHub Stars
- 0
- Server Listing
- Bizfile MCP
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.5/5 across 3 of 3 tools scored.
Each tool has a clearly distinct purpose: validate_counterparty does full validation with AI risk scoring, validate_counterparty_lite is a fast registry check for batch filtering, and screen_counterparty checks sanctions on officers. No overlap in functionality.
All tool names use snake_case and follow a verb_counterparty pattern. 'validate' is used for two tools with a '_lite' suffix, and 'screen' for another. The slight variation in verbs is still consistent in structure.
Three tools is appropriate for the domain: a full validation, a lightweight pre-screen, and a sanctions check. The set is neither too sparse nor overloaded.
The tool set covers the core workflow of pre-payment validation: registry check (lite), full validation with officers, and sanctions screening. A minor gap is ongoing monitoring or entity updates, but the stated purpose is well-served.
Available Tools
3 toolsscreen_counterpartyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| country | No | Optional: ISO country code to narrow search (e.g. ru, cn, ir, kp) | |
| officers | No | Optional: array of officer objects from validate_counterparty to screen all directors simultaneously | |
| entity_type | No | Optional: Person, Company, or Vessel. Defaults to Thing (all types). | |
| company_name | Yes | Name of the company to screen |
Output Schema
| Name | Required | Description |
|---|---|---|
| edd_count | No | |
| checked_at | Yes | |
| source_url | Yes | |
| _disclaimer | No | |
| block_count | No | |
| company_name | No | |
| lists_checked | No | |
| overall_summary | No | |
| overall_verdict | Yes | |
| entities_screened | No | |
| screening_results | Yes | |
| trade_finance_note | No |
validate_counterpartyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| company_name | Yes | Full or partial name of the company to validate | |
| company_number | No | Optional: UK Companies House registration number for exact match (more accurate) |
Output Schema
| Name | Required | Description |
|---|---|---|
| active | No | |
| status | No | Registry status, e.g. active, dissolved, liquidation |
| sic_codes | No | |
| checked_at | Yes | |
| name_match | No | |
| risk_level | No | |
| risk_score | No | |
| source_url | Yes | |
| _disclaimer | No | |
| agent_action | Yes | Machine-readable verdict |
| number_match | No | |
| risk_factors | No | |
| risk_summary | No | |
| company_found | Yes | Whether a matching company was found in UK Companies House |
| kyc_confidence | No | |
| total_officers | No | |
| registered_name | No | |
| incorporation_date | No | |
| registered_address | No | |
| accounts_last_filed | No | |
| positive_indicators | No | |
| recommended_actions | No | |
| registration_number | No | |
| directors_and_officers | No | |
| sanctions_screening_note | No |
validate_counterparty_liteInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| company_name | Yes | Full or partial name of the company to look up | |
| company_number | No | Optional: registration number for exact match |
Output Schema
| Name | Required | Description |
|---|---|---|
| active | No | |
| status | No | |
| checked_at | Yes | |
| source_url | Yes | |
| _disclaimer | No | |
| agent_action | Yes | |
| analysis_type | No | |
| company_found | Yes | |
| kyc_confidence | No | |
| registered_name | No | |
| incorporation_date | No | |
| registered_address | No | |
| registration_number | No |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Your Connectors
Sign in to create a connector for this server.