mcp-registry/io.bosonprotocol/agentic-commerce · v1.2.11
As of 2026-10-20 14:51 UTC, the Bosonprotocol Agentic Commerce MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 3 minutes.
MCP server for Boson Protocol — on-chain agentic commerce for physical & digital goods.
Claude Code
claude mcp add --transport http bosonprotocol-agentic-commerce-mcp-serve https://mcp.bosonprotocol.io/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"bosonprotocol-agentic-commerce-mcp-serve": {
"type": "http",
"url": "https://mcp.bosonprotocol.io/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
11 tool definition(s) exceed ~1,200 tokens each (largest: create_offer_commit_and_redeem, ~2,199).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~12,840 tokens every session. How to fix →
63 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 →
191 parameter(s) across 31 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
1 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 ~42,385 tokens before any work — more than 99% 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 →
Handshake + tools/list takes ~2,185 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 →
In the last 30 days: 0 tool(s) removed and 3 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 31 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.bosonprotocol%2Fagentic-commerce/fixes
{
"name": "get_dispute_by_id",
"description": "Reads a single dispute by its ID (equals the exchangeId). Read-only. Returns: dispute entity with state, timeout, buyerPercent. Use get_disputes to search first.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"disputeId",
"configId"
],
"properties": {
"configId": {
"type": "string",
"description": "Boson/Fermion Protocol deployment identifier. Format: '<env>-<chainId>-<index>' e.g. 'production-137-0' (Polygon mainnet), 'testing-80002-0' (Amoy testnet). Call get_config_ids to list all valid values for this server."
},
"disputeId": {
"type": "string",
"description": "Numeric ID of the dispute to retrieve. Note: disputeId equals the exchangeId of the associated exchange."
},
"queryVars": {
"description": "Optional additional subgraph query variables for field selection. Leave empty for default fields.",
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"title": "Get Dispute by ID",
"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.bosonprotocol/agentic-commerce"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.bosonprotocol/agentic-commerce"}) over MCP.
create_offer_commit_and_redeem ~2,199 tokenscreate_offer_and_commit ~2,189 tokenssign_full_offer ~2,125 tokensvoid_non_listed_offer ~1,957 tokensvoid_non_listed_offer_batch ~1,934 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.bosonprotocol%2Fagentic-commerce?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.bosonprotocol%2Fagentic-commerce?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.bosonprotocol%2Fagentic-commerce.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.bosonprotocol%2Fagentic-commerce.svg :target: https://glimind.com/server/mcp-registry%2Fio.bosonprotocol%2Fagentic-commerce?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:82eb4f259fc71cee…, first seen 2026-10-17, included at leaf 11198 of 33,495. Version history · verify what your client received.
Compare: most reliable other servers · most reliable blockchain servers · most reliable data servers · most reliable knowledge 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-20 14:51 UTC, the Bosonprotocol Agentic Commerce MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 3 minutes.
Bosonprotocol Agentic Commerce MCP server advertises 63 tools, including approve_exchange_token, cancel_voucher, commit_to_buyer_offer, commit_to_conditional_offer, commit_to_conditional_offer_and_redeem_voucher.
Point your MCP client at this streamable-http endpoint: https://mcp.bosonprotocol.io/mcp
Glimind scanned all 63 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.