mcp-registry/io.github.ojaskord/bizfile-mcp · v4.10.60
As of 2026-10-22 10:44 UTC, the Ojaskord Bizfile MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 5 minutes.
Company intelligence and sanctions screening across 130+ jurisdictions and 328 sanctions lists.
Claude Code
claude mcp add --transport http ojaskord-bizfile-mcp-server https://bizfile-mcp-production.up.railway.app
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"ojaskord-bizfile-mcp-server": {
"type": "http",
"url": "https://bizfile-mcp-production.up.railway.app"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
3 of 3 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.ojaskord%2Fbizfile-mcp/fixes
{
"name": "screen_counterparty",
"description": "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 2",
"inputSchema": {
"type": "object",
"required": [
"company_name"
],
"properties": {
"country": {
"type": "string",
"description": "Optional: ISO country code to narrow search (e.g. ru, cn, ir, kp)"
},
"officers": {
"type": "array",
"items": {
"type": "object"
},
"description": "Optional: array of officer objects from validate_counterparty to screen all directors simultaneously"
},
"entity_type": {
"type": "string",
"description": "Optional: Person, Company, or Vessel. Defaults to Thing (all types)."
},
"company_name": {
"type": "string",
"description": "Name of the company to screen"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "validate_counterparty",
"description": "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 p",
"inputSchema": {
"type": "object",
"required": [
"company_name"
],
"properties": {
"company_name": {
"type": "string",
"description": "Full or partial name of the company to validate"
},
"company_number": {
"type": "string",
"description": "Optional: UK Companies House registration number for exact match (more accurate)"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "validate_counterparty_lite",
"description": "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 v",
"inputSchema": {
"type": "object",
"required": [
"company_name"
],
"properties": {
"company_name": {
"type": "string",
"description": "Full or partial name of the company to look up"
},
"company_number": {
"type": "string",
"description": "Optional: registration number for exact match"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.ojaskord/bizfile-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.ojaskord/bizfile-mcp"}) over MCP.
screen_counterparty ~306 tokensvalidate_counterparty ~237 tokensvalidate_counterparty_lite ~229 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.ojaskord%2Fbizfile-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.ojaskord%2Fbizfile-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.ojaskord%2Fbizfile-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.ojaskord%2Fbizfile-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.ojaskord%2Fbizfile-mcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:5683348c97c708cb…, first seen 2026-10-17, included at leaf 6890 of 45,491. Version history · verify what your client received.
Compare: most reliable security servers · most reliable finance servers · most reliable data servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 10:44 UTC, the Ojaskord Bizfile MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 5 minutes.
Ojaskord Bizfile MCP server advertises 3 tools, including screen_counterparty, validate_counterparty, validate_counterparty_lite.
Point your MCP client at this streamable-http endpoint: https://bizfile-mcp-production.up.railway.app
Glimind scanned all 3 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.