Bizfile MCP
REMOTE · BIZFILE-MCP-PRODUCTION.UP.RAILWAY.APP · 2 COMPONENTS
Company intelligence via UK Companies House and risk screening across 386 risk data sources.
Available components
Last scanned (23 hours ago)
Scores higher than 60% of remote servers
Unreachable for 1 day in a row. Last reached 3 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 8 Sept 26 0
- Server version: 4.10.58 → 4.10.60 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- Server version: 4.10.57 → 4.10.58 functional
- 24 Aug 26 0
- Server version: 4.10.56 → 4.10.57 functional
- 19 Aug 26 0
- Server version: 4.10.55 → 4.10.56 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://bizfile-mcp-production.up.railway.app
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bizfile-mcp-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bizfile-mcp-production.up.railway.app | Unreachable | ||
| http (plaintext) | http://bizfile-mcp-production.up.railway.app | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
screen_counterparty ~327
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 | Type | Req | Description |
|---|---|---|---|
| company_name | string | yes | Name of the company to screen |
| country | string | – | Optional: ISO country code to narrow search (e.g. ru, cn, ir, kp) |
| entity_type | string | – | Optional: Person, Company, or Vessel. Defaults to Thing (all types). |
| officers | array | – | Optional: array of officer objects from validate_counterparty to screen all directors simultaneously |
| Name | Type | Req | Description |
|---|---|---|---|
| _disclaimer | string | – | – |
| block_count | integer | – | – |
| checked_at | string | yes | – |
| company_name | string | – | – |
| edd_count | integer | – | – |
| entities_screened | integer | – | – |
| lists_checked | integer | – | – |
| overall_summary | string | – | – |
| overall_verdict | string | yes | – |
| screening_results | array | yes | – |
| source_url | string | yes | – |
| trade_finance_note | string | – | – |
No examples provided.
validate_counterparty ~341
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 | Type | Req | Description |
|---|---|---|---|
| company_name | string | yes | Full or partial name of the company to validate |
| company_number | string | – | Optional: UK Companies House registration number for exact match (more accurate) |
| Name | Type | Req | Description |
|---|---|---|---|
| _disclaimer | string | – | – |
| accounts_last_filed | string|null | – | – |
| active | boolean | – | – |
| agent_action | string | yes | Machine-readable verdict |
| checked_at | string | yes | – |
| company_found | boolean | yes | Whether a matching company was found in UK Companies House |
| directors_and_officers | array | – | – |
| incorporation_date | string | – | – |
| kyc_confidence | string | – | – |
| name_match | boolean | – | – |
| number_match | boolean | – | – |
| positive_indicators | array | – | – |
| recommended_actions | array | – | – |
| registered_address | string | – | – |
| registered_name | string | – | – |
| registration_number | string | – | – |
| risk_factors | array | – | – |
| risk_level | string | – | – |
| risk_score | number | – | – |
| risk_summary | string | – | – |
| sanctions_screening_note | string | – | – |
| sic_codes | array | – | – |
| source_url | string | yes | – |
| status | string | – | Registry status, e.g. active, dissolved, liquidation |
| total_officers | integer | – | – |
No examples provided.
validate_counterparty_lite ~213
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 | Type | Req | Description |
|---|---|---|---|
| company_name | string | yes | Full or partial name of the company to look up |
| company_number | string | – | Optional: registration number for exact match |
| Name | Type | Req | Description |
|---|---|---|---|
| _disclaimer | string | – | – |
| active | boolean | – | – |
| agent_action | string | yes | – |
| analysis_type | string | – | – |
| checked_at | string | yes | – |
| company_found | boolean | yes | – |
| incorporation_date | string | – | – |
| kyc_confidence | string | – | – |
| registered_address | string | – | – |
| registered_name | string | – | – |
| registration_number | string | – | – |
| source_url | string | yes | – |
| status | string | – | – |
No examples provided.
How do I install the Bizfile MCP server?
Bizfile MCP is a hosted endpoint at https://bizfile-mcp-production.up.railway.app/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · bizfile-mcp-production.up.railway.app
claude mcp add --transport http ojaskord-bizfile-mcp 'https://bizfile-mcp-production.up.railway.app/'
What is the Bizfile MCP server?
Bizfile MCP is listed in the public MCP registry as io.github.OjasKord/bizfile-mcp. Company intelligence via UK Companies House and risk screening across 386 risk data sources. This page covers its hosted endpoint (https://bizfile-mcp-production.up.railway.app).
Is the Bizfile MCP server safe to use?
Bizfile MCP scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Bizfile MCP server expose?
Bizfile MCP exposes 3 tools: validate_counterparty, screen_counterparty, validate_counterparty_lite. Their descriptions and schemas cost roughly 881 tokens of context every time the server is loaded.
Does the Bizfile MCP server require authentication?
Its publisher declares no required credentials for Bizfile MCP. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Bizfile MCP server still maintained?
Bizfile MCP is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.