mcp-registry/io.github.everest-an/protocol-banks · registry v1.1.0 · server reports v1.0.0
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clientsAs of 2026-11-22 19:08 UTC, the Protocol Banks MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Control plane for agent commerce: orders, payments, cards and trading under one mandate.
Point your MCP client at this streamable-http endpoint: https://www.protocolbanks.com/api/mcp
23 of 23 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 →
6 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 →
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.everest-an%2Fprotocol-banks/fixes
{
"name": "check_payment_status",
"description": "Check the status of a payment by ID. Requires authentication.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"payment_id": {
"type": "string",
"description": "The payment ID to check."
},
"readOnlyHint": true
}
}{
"name": "compare_chain_fees",
"description": "Compare transfer fees across all supported chains for a token. Identifies the cheapest chain. No authentication required.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"token": {
"type": "string",
"description": "Token symbol (e.g. \"USDC\")."
},
"amount": {
"type": "string",
"description": "Transfer amount (e.g. \"100\")."
},
"to_address": {
"type": "string",
"description": "Recipient address (0x...)."
},
"readOnlyHint": true
}
}{
"name": "complete_commerce_order",
"description": "Buyer: confirm a paid, delivered order. Requires authentication.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"orderId"
],
"properties": {
"orderId": {
"type": "string",
"description": "Order id."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "complete_commerce_order"
}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.everest-an/protocol-banks"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.everest-an/protocol-banks"}) over MCP.
control_trading_agent ~275 tokenscreate_commerce_quote ~248 tokensdeliver_commerce_order ~169 tokenslist_agent_services ~127 tokensget_activity ~120 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.
Shows whether the server is live and its agent-readiness score; it updates within the hour.
[](https://glimind.com/server/mcp-registry%2Fio.github.everest-an%2Fprotocol-banks?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.everest-an%2Fprotocol-banks?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.github.everest-an%2Fprotocol-banks.svg" alt="MCP server status"></a>
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:0181b789de1f561b…, first seen 2026-11-16, included at leaf 302187 of 384,944. Version history · verify what your client received.
Compare: most reliable payments servers · most reliable finance servers · most reliable other 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?ref=install-server
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp?ref=install-server"
}
}
}
A free Glimind key lets your agent check whether a server works right now before it calls it, and switch to a live one when it doesn't. No signup, no card.
As of 2026-11-22 19:08 UTC, the Protocol Banks MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Protocol Banks MCP server advertises 23 tools, including accept_commerce_quote, check_payment_status, compare_chain_fees, complete_commerce_order, control_trading_agent.
Point your MCP client at this streamable-http endpoint: https://www.protocolbanks.com/api/mcp
Glimind scanned all 23 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.