Provenancewhere it came from, and what was verified
Published by the owner of bosonprotocol.io, who proved control of the domain through the official MCP registry.
🛡 Permissions & trustwhat this server can touch before you run it
About
MCP server for Boson Protocol — on-chain agentic commerce for physical & digital goods.
Packages & transports
Metadata
Computed from the server's own data, not a hidden formula. This measures how much you can depend on it, not how popular it is. Stars are shown separately, on purpose. How it's scored →
▸get_config_ids100A
▸get_funds79B
▸get_disputes79B
▸get_dispute_by_id92A
▸get_exchanges79B
▸get_offers77B
▸get_sellers78B
▸get_dispute_resolvers79B
▸create_offer99A
▸create_offer_with_condition98A
▸create_buyer100A
▸sign_full_offer99A
▸create_offer_and_commit99A
▸create_offer_commit_and_redeem99A
▸void_offer100A
▸void_non_listed_offer98A
▸void_non_listed_offer_batch92A
▸create_seller85A
▸update_seller84B
▸send_signed_transaction100A
▸send_meta_transaction81B
▸send_native_meta_transaction86A
▸send_forwarded_meta_transaction88A
▸withdraw_funds95A
▸deposit_funds100A
▸extend_dispute_timeout100A
▸expire_dispute100A
▸expire_dispute_batch100A
▸resolve_dispute100A
▸raise_dispute100A
▸retract_dispute100A
▸escalate_dispute100A
▸decide_dispute100A
▸refuse_escalated_dispute100A
▸expire_escalated_dispute100A
▸create_dispute_resolution_proposal100A
▸revoke_voucher100A
▸approve_exchange_token100A
▸sign_receive_with_erc3009_authorization100A
▸sign_receive_with_erc2612_permit100A
▸sign_receive_with_permit2100A
▸sign_receive_with_dai_permit100A
▸commit_to_offer100A
▸commit_to_conditional_offer100A
▸commit_to_offer_and_redeem_voucher100A
▸commit_to_conditional_offer_and_redeem_voucher100A
▸commit_to_buyer_offer93A
▸cancel_voucher100A
▸redeem_voucher100A
▸complete_exchange100A
▸get_sellers_by_address77B
▸get_all_products_with_not_voided_variants79B
▸search_products85A
▸validate_metadata75B
▸store_product_v1_metadata78B
▸store_bundle_metadata78B
▸store_base_metadata79B
▸render_contractual_agreement85A
▸store_bundle_item_product_v1_metadata80B
▸store_bundle_item_nft_metadata77B
▸register_agent75B
▸get_registered_agents100A
▸get_supported_tokens100A
Structural, not an LLM's opinion: each check is a fact about the tool's schema, so it's reproducible. One weak tool drags the score (60% average, 40% worst). How it's scored →
Raise this grade
up to +22 on qualityOwn this server? Here's exactly what to change, biggest wins first. Every number below is a fixed point value, so you can see what each edit is worth before you make it.
With no reviews this sits at a neutral 11. Reviews reporting it works push it toward the full 20.
Add an SPDX license (like MIT or Apache-2.0) to the repo so it's detected.
Add a public source repository URL.
- 1 of 1 params have no description: `metadata`. Describe each one.
- 3 of 3 params have no description: `name`, `entities`, `description`. Describe each one.
- 11 of 12 params have no description: `offersSkip`, `offersFirst`, `offersFilter`, `exchangesSkip`, +7 more. Describe each one.
- 10 of 11 params have no description: `address`, `includeLogs`, `sellersSkip`, `includeFunds`, +6 more. Describe each one.
Already earned (3) ▾Already earned (3) ▴
These are structural checks, so the fixes are exact. See the full formula →
Add a badge to your README
[](https://socketcat.com/servers/io.bosonprotocol/agentic-commerce)Shows your live quality grade and links back here. It updates itself as the grade changes.
Reviews
Sign in to leave a reviewNo reviews yet. Be the first to say whether it worked.
{
"mcpServers": {
"agentic_commerce": {
"command": "npx",
"args": [
"-y",
"agentic-commerce"
]
}
}
}▶ Try itlive against mcp.bosonprotocol.io
This server has a hosted endpoint, so we can connect and list its actual tools right here. Nothing runs on your machine.