mcp-registry/io.github.bnmbnmai/bnm-data-shop · v1.0.0
As of 2026-10-25 05:07 UTC, the Bnmbnmai Bnm Data Shop MCP server is up with a Glimind reliability score of 51/100 (grade D). Over the last 30 days it answered 93.9% of Glimind's liveness checks. It had 628 outages in 90 days, with a median recovery of 7 minutes.
Official public-data caches sold per pull via x402/USDC on Base.
Claude Code
claude mcp add --transport http bnmbnmai-bnm-data-shop-mcp-server https://ticks.bnm.farm/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"bnmbnmai-bnm-data-shop-mcp-server": {
"type": "http",
"url": "https://ticks.bnm.farm/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
Reachable 93.9% of the time over the last 30 days; median recovery 7 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
62 of 62 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 →
62 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
14 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Loading this server's tool list costs an agent ~18,136 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
Negotiates MCP 2025-03-26. 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 →
Handshake + tools/list takes ~7,476 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. 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.bnmbnmai%2Fbnm-data-shop/fixes
{
"name": "bis-orders",
"description": "GET https://ticks.bnm.farm/bis-orders — $0.05 USDC on Base to 0xf59621FC406D266e18f314Ae18eF0a33b8401004. BIS institution charging-letter / order text GET ?id= is one official text ($0.02). Newest chunk on a plain GET ($0.05); older chunk if they ask (?before, $0.05); newer than a watermark ?since= ($0.05). Unpaid returns HTTP 402. After a valid X-PAYMENT, the same URL returns JSON. Not a new SKU.",
"inputSchema": {
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "Official catalog id. That one official text, $0.02. Same door, not a new SKU."
},
"page": {
"type": "string",
"description": "1-based page. Page 1 is the newest chunk. Ignored when since/before is set."
},
"since": {
"type": "string",
"description": "ISO timestamp or official catalog id. Official texts newer than this watermark, $0.05. Empty new set is 304 or recordCount 0."
},
"before": {
"type": "string",
"description": "Official catalog id or YYYY-MM-DD. Next older chunk on the same URL, another $0.05. Omit for the newest chunk."
},
"x_payment": {
"type": "string",
"description": "Optional x402 X-PAYMENT value forwarded to the paid GET as the X-PAYMENT header."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "cfpb-orders",
"description": "GET https://ticks.bnm.farm/cfpb-orders — $0.05 USDC on Base to 0xf59621FC406D266e18f314Ae18eF0a33b8401004. CFPB consent-order / administrative-order text GET ?id= is one official text ($0.02). Newest chunk on a plain GET ($0.05); older chunk if they ask (?before, $0.05); newer than a watermark ?since= ($0.05). Unpaid returns HTTP 402. After a valid X-PAYMENT, the same URL returns JSON. Not a new SKU.",
"inputSchema": {
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "Official catalog id. That one official text, $0.02. Same door, not a new SKU."
},
"page": {
"type": "string",
"description": "1-based page. Page 1 is the newest chunk. Ignored when since/before is set."
},
"since": {
"type": "string",
"description": "ISO timestamp or official catalog id. Official texts newer than this watermark, $0.05. Empty new set is 304 or recordCount 0."
},
"before": {
"type": "string",
"description": "Official catalog id or YYYY-MM-DD. Next older chunk on the same URL, another $0.05. Omit for the newest chunk."
},
"x_payment": {
"type": "string",
"description": "Optional x402 X-PAYMENT value forwarded to the paid GET as the X-PAYMENT header."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "cftc-orders",
"description": "GET https://ticks.bnm.farm/cftc-orders — $0.05 USDC on Base to 0xf59621FC406D266e18f314Ae18eF0a33b8401004. CFTC institution enforcement-order / settlement text GET ?id= is one official text ($0.02). Newest chunk on a plain GET ($0.05); older chunk if they ask (?before, $0.05); newer than a watermark ?since= ($0.05). Unpaid returns HTTP 402. After a valid X-PAYMENT, the same URL returns JSON. Not a new SKU.",
"inputSchema": {
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "Official catalog id. That one official text, $0.02. Same door, not a new SKU."
},
"page": {
"type": "string",
"description": "1-based page. Page 1 is the newest chunk. Ignored when since/before is set."
},
"since": {
"type": "string",
"description": "ISO timestamp or official catalog id. Official texts newer than this watermark, $0.05. Empty new set is 304 or recordCount 0."
},
"before": {
"type": "string",
"description": "Official catalog id or YYYY-MM-DD. Next older chunk on the same URL, another $0.05. Omit for the newest chunk."
},
"x_payment": {
"type": "string",
"description": "Optional x402 X-PAYMENT value forwarded to the paid GET as the X-PAYMENT header."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}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.bnmbnmai/bnm-data-shop"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.bnmbnmai/bnm-data-shop"}) over MCP.
get-page ~413 tokenssearch ~353 tokensfaa-civil-penalty ~339 tokensofwat-enforcement ~339 tokensofsted-inspections ~338 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.bnmbnmai%2Fbnm-data-shop?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.bnmbnmai%2Fbnm-data-shop?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.bnmbnmai%2Fbnm-data-shop.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.bnmbnmai%2Fbnm-data-shop.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.bnmbnmai%2Fbnm-data-shop?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:83b6024ad123a8ff…, first seen 2026-10-17, included at leaf 3017 of 64,042. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable retrieval servers · most reliable data servers · most reliable other servers · most reliable search 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-25 05:07 UTC, the Bnmbnmai Bnm Data Shop MCP server is up with a Glimind reliability score of 51/100 (grade D). Over the last 30 days it answered 93.9% of Glimind's liveness checks. It had 628 outages in 90 days, with a median recovery of 7 minutes.
Bnmbnmai Bnm Data Shop MCP server advertises 62 tools, including aaib-reports, air-letters, awa, bis-orders, bsee-reports.
Point your MCP client at this streamable-http endpoint: https://ticks.bnm.farm/mcp
Glimind scanned all 62 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.