Is io.bosonprotocol/agentic-commerce up? Live MCP status
Yes, it is up. It answered an MCP initialize with no credential and negotiated protocol 2025-06-18.
A stock client connected with no credential and negotiated 2025-06-18. Use it.
| Outcome | usable |
|---|---|
| HTTP status | 200 |
| Protocol version | 2025-06-18 |
| Server says it is | boson-protocol-server 1.2.11 |
| Answered in | 462 ms |
| Endpoint checked | https://mcp.bosonprotocol.io/mcp |
| Checked |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Not published (HTTP 404)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://mcp.bosonprotocol.io/mcp/server-card |
| MCP server card (SEP-1649 location) | Published, does not validate: `authentication` needs `required` and `schemes` (and 1 more). SEP-1649 shape; boson-protocol 1.2.11; MCP 2025-06-18; streamable-http./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://mcp.bosonprotocol.io with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 63 tools: approve_exchange_token, cancel_voucher, commit_to_buyer_offer, commit_to_conditional_offer, commit_to_conditional_offer_and_redeem_voucher, commit_to_offer, commit_to_offer_and_redeem_voucher, complete_exchange, create_buyer, create_dispute_resolution_proposal, create_offer, create_offer_and_commit, create_offer_commit_and_redeem, create_offer_with_condition, create_seller, decide_dispute, deposit_funds, escalate_dispute, expire_dispute, expire_dispute_batch, expire_escalated_dispute, extend_dispute_timeout, get_all_products_with_not_voided_variants, get_config_ids, get_dispute_by_id, get_dispute_resolvers, get_disputes, get_exchanges, get_funds, get_offers, get_registered_agents, get_sellers, get_sellers_by_address, get_supported_tokens, raise_dispute, redeem_voucher, refuse_escalated_dispute, register_agent, render_contractual_agreement, resolve_dispute, retract_dispute, revoke_voucher, search_products, send_forwarded_meta_transaction, send_meta_transaction, send_native_meta_transaction, send_signed_transaction, sign_full_offer, sign_receive_with_dai_permit, sign_receive_with_erc2612_permit, sign_receive_with_erc3009_authorization, sign_receive_with_permit2, store_base_metadata, store_bundle_item_nft_metadata, store_bundle_item_product_v1_metadata, store_bundle_metadata, store_product_v1_metadata, update_seller, validate_metadata, void_non_listed_offer, void_non_listed_offer_batch, void_offer, withdraw_funds.
No change to its tools between 2026-09 and 2026-10.
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | io.bosonprotocol/agentic-commerce |
|---|---|
| Description | MCP server for Boson Protocol — on-chain agentic commerce for physical & digital goods. |
| Endpoint | https://mcp.bosonprotocol.io/mcp |
| Publisher repository | none listed |
| Version | 1.0.0 |
| Listing updated |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt