MCP servers observed by Lowdown
io.bosonprotocol/agentic-commerce MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-11 to 2026-11-17) (Lowdown checks this server every 3 days); 63 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; no tool definition change in 2 compared days; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.bosonprotocol/agentic-commerce
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.bosonprotocol/agentic-commerce?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-17: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 2 compared days.
What tools does it list?
63 tools on 2026-11-17:
approve_exchange_tokencancel_vouchercommit_to_buyer_offercommit_to_conditional_offercommit_to_conditional_offer_and_redeem_vouchercommit_to_offercommit_to_offer_and_redeem_vouchercomplete_exchangecreate_buyercreate_dispute_resolution_proposalcreate_offercreate_offer_and_commitcreate_offer_commit_and_redeemcreate_offer_with_conditioncreate_sellerdecide_disputedeposit_fundsescalate_disputeexpire_disputeexpire_dispute_batchexpire_escalated_disputeextend_dispute_timeoutget_all_products_with_not_voided_variantsget_config_idsget_dispute_by_idget_dispute_resolversget_disputesget_exchangesget_fundsget_offersget_registered_agentsget_sellersget_sellers_by_addressget_supported_tokensraise_disputeredeem_voucherrefuse_escalated_disputeregister_agentrender_contractual_agreementresolve_disputeretract_disputerevoke_vouchersearch_productssend_forwarded_meta_transactionsend_meta_transactionsend_native_meta_transactionsend_signed_transactionsign_full_offersign_receive_with_dai_permitsign_receive_with_erc2612_permitsign_receive_with_erc3009_authorizationsign_receive_with_permit2store_base_metadatastore_bundle_item_nft_metadatastore_bundle_item_product_v1_metadatastore_bundle_metadatastore_product_v1_metadataupdate_sellervalidate_metadatavoid_non_listed_offervoid_non_listed_offer_batchvoid_offerwithdraw_funds
MCP Registry declaration
- Registry name:
io.bosonprotocol/agentic-commerce - Declared version: 1.0.0
- Status: active
- Declared hosts:
mcp.bosonprotocol.io
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.bosonprotocol/agentic-commerce", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.bosonprotocol/agentic-commerce?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).