Skip to main content
Glama
Ownership verified

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.

MCP client
Glama
MCP server

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.

100% free. Your data is private.
Tool DescriptionsA

Average 4.5/5 across 3 of 3 tools scored.

Server CoherenceA
Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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 tools
screen_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.

ParametersJSON Schema
NameRequiredDescriptionDefault
countryNoOptional: ISO country code to narrow search (e.g. ru, cn, ir, kp)
officersNoOptional: array of officer objects from validate_counterparty to screen all directors simultaneously
entity_typeNoOptional: Person, Company, or Vessel. Defaults to Thing (all types).
company_nameYesName of the company to screen

Output Schema

ParametersJSON Schema
NameRequiredDescription
edd_countNo
checked_atYes
source_urlYes
_disclaimerNo
block_countNo
company_nameNo
lists_checkedNo
overall_summaryNo
overall_verdictYes
entities_screenedNo
screening_resultsYes
trade_finance_noteNo
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.

ParametersJSON Schema
NameRequiredDescriptionDefault
company_nameYesFull or partial name of the company to validate
company_numberNoOptional: UK Companies House registration number for exact match (more accurate)

Output Schema

ParametersJSON Schema
NameRequiredDescription
activeNo
statusNoRegistry status, e.g. active, dissolved, liquidation
sic_codesNo
checked_atYes
name_matchNo
risk_levelNo
risk_scoreNo
source_urlYes
_disclaimerNo
agent_actionYesMachine-readable verdict
number_matchNo
risk_factorsNo
risk_summaryNo
company_foundYesWhether a matching company was found in UK Companies House
kyc_confidenceNo
total_officersNo
registered_nameNo
incorporation_dateNo
registered_addressNo
accounts_last_filedNo
positive_indicatorsNo
recommended_actionsNo
registration_numberNo
directors_and_officersNo
sanctions_screening_noteNo
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.

ParametersJSON Schema
NameRequiredDescriptionDefault
company_nameYesFull or partial name of the company to look up
company_numberNoOptional: registration number for exact match

Output Schema

ParametersJSON Schema
NameRequiredDescription
activeNo
statusNo
checked_atYes
source_urlYes
_disclaimerNo
agent_actionYes
analysis_typeNo
company_foundYes
kyc_confidenceNo
registered_nameNo
incorporation_dateNo
registered_addressNo
registration_numberNo

Discussions

No comments yet. Be the first to start the discussion!

Try in Browser

Your Connectors

Sign in to create a connector for this server.