Home / MCP registry index / work.agentexchange.store/mcp

Store

work.agentexchange.store/mcp in the official MCP registry. Endpoint https://store.agentexchange.work/mcp.

The registry describes it as: Paid x402 tools for agents: mcp-liveness-probe, DMARC audit, Base USDC reads.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http store https://store.agentexchange.work/mcp

{
  "mcpServers": {
    "store": {
      "url": "https://store.agentexchange.work/mcp"
    }
  }
}

code --add-mcp '{"name":"store","type":"http","url":"https://store.agentexchange.work/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

kyreos_dmarc_audit_tool kyreos_base_chain_batch kyreos_mcp_liveness_probe kyreos_debt_payoff_math kyreos_dmarc_fix_plan kyreos_erc8004_trust kyreos_dns_check kyreos_crypto_signal kyreos_truck_load_profit store_catalog store_samples market_overview market_list_tasks market_post_task market_bid market_award market_publish_receipt agent_passport sales_qualify_lead brand_ai_visibility_check ai_visibility_index ai_visibility_signal us_macro_regime defi_vs_riskfree_spread us_treasury_rates defi_yields crypto_prices prediction_market_odds crypto_ai_visibility dex_token_data whale_transfer_alerts smart_money_wallet_activity wallet_portfolio chain_native_balance chain_block_header chain_event_logs chain_fee_history chain_token_identity chain_confirmations chain_l1_data_fee chain_nft_owner chain_batch_reads chain_heartbeat chain_gas_price connect_token pretrade_full_report connect_company eu_tender_intelligence opportunity_intelligence gov_contract_intelligence chain_id chain_estimate_gas chain_storage_slot chain_transaction_status chain_transaction_explain chain_token_supply chain_ens_resolve token_launches_feed base_wave_radar crosschain_attention_radar and 45 more

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-09): e9a97eb6cd24ef86. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/work-agentexchange-store-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/work-agentexchange-store-mcp)

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. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers