# Bizfile MCP (remote · bizfile-mcp-production.up.railway.app)

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

- Trust score: 60/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `bizfile-mcp-production.up.railway.app`: 60/100 (this document), [markdown](https://verifymcp.io/servers/ojaskord-bizfile-mcp/bizfile-mcp-production.md), [page](https://verifymcp.io/servers/ojaskord-bizfile-mcp/bizfile-mcp-production)
- npm · `bizfile-mcp`: 35/100, [markdown](https://verifymcp.io/servers/ojaskord-bizfile-mcp/bizfile-mcp.md), [page](https://verifymcp.io/servers/ojaskord-bizfile-mcp/bizfile-mcp)

## Channel facts

- Endpoint: `https://bizfile-mcp-production.up.railway.app`
- Transports: `streamable-http`
- Auth: `none`
- Version: `4.10.47`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ojaskord-bizfile-mcp https://bizfile-mcp-production.up.railway.app/
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ojaskord-bizfile-mcp --url https://bizfile-mcp-production.up.railway.app/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ojaskord-bizfile-mcp:
    url: "https://bizfile-mcp-production.up.railway.app/"
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 60, +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.

### 2026-07-31 (score 59, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 58, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 58, +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.

### 2026-07-27 (score 57, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 56)

First indexed and scored.

## MCP tools (3)

### `validate_counterparty` (~341 tokens)

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.

Input parameters:

- `company_name` (string, required): Full or partial name of the company to validate
- `company_number` (string): Optional: UK Companies House registration number for exact match (more accurate)

Output parameters:

- `_disclaimer` (string)
- `accounts_last_filed` (string|null)
- `active` (boolean)
- `agent_action` (string): Machine-readable verdict
- `checked_at` (string)
- `company_found` (boolean): 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)
- `status` (string): Registry status, e.g. active, dissolved, liquidation
- `total_officers` (integer)

### `screen_counterparty` (~327 tokens)

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.

Input parameters:

- `company_name` (string, required): 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

Output parameters:

- `_disclaimer` (string)
- `block_count` (integer)
- `checked_at` (string)
- `company_name` (string)
- `edd_count` (integer)
- `entities_screened` (integer)
- `lists_checked` (integer)
- `overall_summary` (string)
- `overall_verdict` (string)
- `screening_results` (array)
- `source_url` (string)
- `trade_finance_note` (string)

### `validate_counterparty_lite` (~213 tokens)

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.

Input parameters:

- `company_name` (string, required): Full or partial name of the company to look up
- `company_number` (string): Optional: registration number for exact match

Output parameters:

- `_disclaimer` (string)
- `active` (boolean)
- `agent_action` (string)
- `analysis_type` (string)
- `checked_at` (string)
- `company_found` (boolean)
- `incorporation_date` (string)
- `kyc_confidence` (string)
- `registered_address` (string)
- `registered_name` (string)
- `registration_number` (string)
- `source_url` (string)
- `status` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ojaskord-bizfile-mcp/bizfile-mcp-production#diagnostics

## Score history

- 2026-08-03: 60
- 2026-08-02: 60
- 2026-08-01: 59
- 2026-07-31: 59
- 2026-07-30: 58
- 2026-07-29: 58
- 2026-07-28: 57
- 2026-07-27: 57
- 2026-07-26: 56

## Links

- Remote endpoint: https://bizfile-mcp-production.up.railway.app/
- Repository: https://github.com/OjasKord/bizfile-mcp
- Website: https://kordagencies.com/
- Changelog RSS feed: https://verifymcp.io/servers/ojaskord-bizfile-mcp/bizfile-mcp-production/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ojaskord-bizfile-mcp/bizfile-mcp-production/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ojaskord-bizfile-mcp/bizfile-mcp-production