Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Bizfile MCP

REMOTE · BIZFILE-MCP-PRODUCTION.UP.RAILWAY.APP · 2 COMPONENTS · SCANNED AUG 3

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

+3 this week 60 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 881 tokens (~293/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · bizfile-mcp-production.up.railway.app

# add to Claude Code
claude mcp add --transport http ojaskord-bizfile-mcp https://bizfile-mcp-production.up.railway.app/
# ~/.codex/config.toml
[mcp_servers.ojaskord-bizfile-mcp]
url = "https://bizfile-mcp-production.up.railway.app/"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ojaskord-bizfile-mcp": {
      "type": "remote",
      "url": "https://bizfile-mcp-production.up.railway.app/",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ojaskord-bizfile-mcp --url https://bizfile-mcp-production.up.railway.app/ --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ojaskord-bizfile-mcp:
    url: "https://bizfile-mcp-production.up.railway.app/"
// mcp.json
{
  "mcpServers": {
    "ojaskord-bizfile-mcp": {
      "type": "http",
      "url": "https://bizfile-mcp-production.up.railway.app/"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 2 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 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
  • 29 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 56

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Probed https://bizfile-mcp-production.up.railway.app

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.up.railway.app CN=YE1,O=Let's Encrypt,C=US 29 Jul 2026 27 Oct 2026 ECDSA 256 ECDSA-SHA384 6da79bb561da3efeb0e751ca21abd3999fe
SANs: *.up.railway.app, up.railway.app
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
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 No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://bizfile-mcp-production.up.railway.app Verified 200
http (plaintext) http://bizfile-mcp-production.up.railway.app HTTPS enforced 301 https://bizfile-mcp-production.up.railway.app/
MCP tools — 3 exposed · ~881 tokens

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.

Tool Tokens
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.

NameTypeReqDescription
company_namestringyesName of the company to screen
countrystringOptional: ISO country code to narrow search (e.g. ru, cn, ir, kp)
entity_typestringOptional: Person, Company, or Vessel. Defaults to Thing (all types).
officersarrayOptional: array of officer objects from validate_counterparty to screen all directors simultaneously
NameTypeReqDescription
_disclaimerstring
block_countinteger
checked_atstringyes
company_namestring
edd_countinteger
entities_screenedinteger
lists_checkedinteger
overall_summarystring
overall_verdictstringyes
screening_resultsarrayyes
source_urlstringyes
trade_finance_notestring

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.

NameTypeReqDescription
company_namestringyesFull or partial name of the company to validate
company_numberstringOptional: UK Companies House registration number for exact match (more accurate)
NameTypeReqDescription
_disclaimerstring
accounts_last_filedstring|null
activeboolean
agent_actionstringyesMachine-readable verdict
checked_atstringyes
company_foundbooleanyesWhether a matching company was found in UK Companies House
directors_and_officersarray
incorporation_datestring
kyc_confidencestring
name_matchboolean
number_matchboolean
positive_indicatorsarray
recommended_actionsarray
registered_addressstring
registered_namestring
registration_numberstring
risk_factorsarray
risk_levelstring
risk_scorenumber
risk_summarystring
sanctions_screening_notestring
sic_codesarray
source_urlstringyes
statusstringRegistry status, e.g. active, dissolved, liquidation
total_officersinteger

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.

NameTypeReqDescription
company_namestringyesFull or partial name of the company to look up
company_numberstringOptional: registration number for exact match
NameTypeReqDescription
_disclaimerstring
activeboolean
agent_actionstringyes
analysis_typestring
checked_atstringyes
company_foundbooleanyes
incorporation_datestring
kyc_confidencestring
registered_addressstring
registered_namestring
registration_numberstring
source_urlstringyes
statusstring

No examples provided.