Home / MCP registry index / io.bosonprotocol/agentic-commerce
io.bosonprotocol/agentic-commerce
io.bosonprotocol/agentic-commerce in the official MCP registry.
Endpoint https://mcp.bosonprotocol.io/mcp.
The registry describes it as: MCP server for Boson Protocol — on-chain agentic commerce for physical & digital goods.
We read its 63 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
get_config_ids get_funds get_disputes get_dispute_by_id get_exchanges get_offers get_sellers get_dispute_resolvers create_offer create_offer_with_condition create_buyer sign_full_offer create_offer_and_commit create_offer_commit_and_redeem void_offer void_non_listed_offer void_non_listed_offer_batch create_seller update_seller send_signed_transaction send_meta_transaction send_native_meta_transaction send_forwarded_meta_transaction withdraw_funds deposit_funds extend_dispute_timeout expire_dispute expire_dispute_batch resolve_dispute raise_dispute retract_dispute escalate_dispute decide_dispute refuse_escalated_dispute expire_escalated_dispute create_dispute_resolution_proposal revoke_voucher approve_exchange_token sign_receive_with_erc3009_authorization sign_receive_with_erc2612_permit sign_receive_with_permit2 sign_receive_with_dai_permit commit_to_offer commit_to_conditional_offer commit_to_offer_and_redeem_voucher commit_to_conditional_offer_and_redeem_voucher commit_to_buyer_offer cancel_voucher redeem_voucher complete_exchange get_sellers_by_address get_all_products_with_not_voided_variants search_products validate_metadata store_product_v1_metadata store_bundle_metadata store_base_metadata render_contractual_agreement store_bundle_item_product_v1_metadata store_bundle_item_nft_metadata and 3 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-bosonprotocol-agentic-commerce)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.