{"listings":[{"id":"f2023a96-64cc-4ee1-8d34-fcd11ff2e3e6","url":"https://inbox.surfingdog.ai/mcp","name":"Surfing Dog Inbox","description":"Typed inbox for receiving and processing messages, quotes and bookings from AI agents via REST and MCP. Structures requests with rules and lifecycle.","tags":["inbox","messaging","forms","mcp"],"tier":"free","lastSeenAlive":1793818298226,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\nf2023a96-64cc-4ee1-8d34-fcd11ff2e3e6\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://inbox.surfingdog.ai/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"f2023a96-64cc-4ee1-8d34-fcd11ff2e3e6\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\nf2023a96-64cc-4ee1-8d34-fcd11ff2e3e6\" at the same path and POST {\"id\":\"f2023a96-64cc-4ee1-8d34-fcd11ff2e3e6\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"07853ac0-31b2-4a06-989b-1d5643b78db4","url":"https://mcp.proxycove.com/mcp","name":"ProxyCove","description":"Buy and manage residential, mobile and datacenter proxies in 170+ countries. Agent creates account via create_account with no email or signup form required. Prepaid per GB.","tags":["proxies","networking","pay-per-call"],"tier":"free","lastSeenAlive":1793818297539,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n07853ac0-31b2-4a06-989b-1d5643b78db4\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://mcp.proxycove.com/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"07853ac0-31b2-4a06-989b-1d5643b78db4\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n07853ac0-31b2-4a06-989b-1d5643b78db4\" at the same path and POST {\"id\":\"07853ac0-31b2-4a06-989b-1d5643b78db4\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"ce33059a-db9c-461d-9a0d-503f13a2cfbc","url":"https://project-feldspar.com/mcp","name":"Feldspar free repository security scan","description":"Deterministic security scan of public git repos: vulnerable dependencies from OSV.dev, leaked secrets, and config lint. No account, no telemetry.","tags":["security","scanning","dependencies","agent-driven"],"tier":"free","lastSeenAlive":1793818296912,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\nce33059a-db9c-461d-9a0d-503f13a2cfbc\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://project-feldspar.com/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"ce33059a-db9c-461d-9a0d-503f13a2cfbc\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\nce33059a-db9c-461d-9a0d-503f13a2cfbc\" at the same path and POST {\"id\":\"ce33059a-db9c-461d-9a0d-503f13a2cfbc\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"3c6a5928-4bd8-414f-a16e-825eb8622442","url":"https://dabyte.ai/mcp","name":"dabyte","description":"Weekly AI-visibility data for SaaS: share of answer across ChatGPT, Perplexity, Gemini. Open data, no signup.","tags":["saas","market-intelligence","open-data"],"tier":"free","lastSeenAlive":1793818296503,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n3c6a5928-4bd8-414f-a16e-825eb8622442\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://dabyte.ai/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"3c6a5928-4bd8-414f-a16e-825eb8622442\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n3c6a5928-4bd8-414f-a16e-825eb8622442\" at the same path and POST {\"id\":\"3c6a5928-4bd8-414f-a16e-825eb8622442\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"6def4a58-bf56-4f1f-8613-b11c6de6acda","url":"https://dablock.ai/mcp","name":"dablock","description":"Weekly AI-visibility data for crypto: share of answer on ChatGPT, Perplexity, Gemini. Open data, no signup.","tags":["crypto","market-intelligence","open-data"],"tier":"free","lastSeenAlive":1793818295538,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n6def4a58-bf56-4f1f-8613-b11c6de6acda\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://dablock.ai/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"6def4a58-bf56-4f1f-8613-b11c6de6acda\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n6def4a58-bf56-4f1f-8613-b11c6de6acda\" at the same path and POST {\"id\":\"6def4a58-bf56-4f1f-8613-b11c6de6acda\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"50a82aec-07eb-4151-9861-0f43959e2798","url":"https://app.daedalmap.com/mcp/boundaries","name":"DaedalMap Administrative Boundaries","description":"Convert location IDs to bounding boxes, centroids, and polygons with place names and administrative levels.","tags":["geographic","boundaries","geocoding"],"tier":"free","lastSeenAlive":1793817695091,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_OK","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n50a82aec-07eb-4151-9861-0f43959e2798\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://app.daedalmap.com/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"50a82aec-07eb-4151-9861-0f43959e2798\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n50a82aec-07eb-4151-9861-0f43959e2798\" at the same path and POST {\"id\":\"50a82aec-07eb-4151-9861-0f43959e2798\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"7b328060-3d5d-4a5c-89a5-50f92379f63d","url":"https://site-stack-audit.alice-webdeveloppement.workers.dev/audit/batch","name":"Site Stack Audit — batch audit (5 sites)","description":"Audit up to 5 websites in one call: the same JSON as the single-site audit for each URL, in order, with a per-site error for targets that could not be audited. Pass a comma-separated list in `urls`. Charged once, and only if at least one site was audited.","tags":["website","audit","batch","tech-stack","lead-qualification"],"tier":"free","lastSeenAlive":1793817095637,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_OK","operator":false,"provenance":"owner","claimable":false,"claim":null,"consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"2842badb-0e3f-4d4c-8ce5-b9694f4be2d8","url":"https://agentpay.tools/tools","name":"AgentPay","description":"Budget-capped spend governance for AI agents: price a plan before spending, route to the cheapest tool that works, and settle under a hard USDC cap with a receipt per call. 17 of 20 tools are free and need no wallet.","tags":["x402","agent-payments","budget","tools","receipts"],"tier":"free","lastSeenAlive":1793816797657,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_OK","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. You can take this row over, or have it removed immediately and unconditionally, with one signature from the wallet this service publishes as its x402 `payTo` -- no account, no signup. POST {\"id\":\"2842badb-0e3f-4d4c-8ce5-b9694f4be2d8\",\"action\":\"claim\"} to https://agent-exec.448c.org/listings/claim with header X-Signature = personal_sign(\"agent-exec:listing:claim:v1\\n2842badb-0e3f-4d4c-8ce5-b9694f4be2d8\"). To be removed instead, send action \"remove\" and sign \"agent-exec:listing:remove:v1\\n2842badb-0e3f-4d4c-8ce5-b9694f4be2d8\" -- a DIFFERENT message on purpose, so a claim can never be replayed as a takedown. Removal is honoured on the same wallet, with no questions asked and no retention. On a claim the row becomes yours and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"a90e2c72-76ba-458b-9d3b-88032af14d4f","url":"https://savantcat.cn/mcp","name":"SavantCat Answers","description":"Chinese GB/T 47746-2026 AI customer service compliance knowledge base. Machine-readable standard interpretation for agent queries. No API key required.","tags":["compliance","customer-service","china","standards","legal"],"tier":"free","lastSeenAlive":1793816796814,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_OK","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\na90e2c72-76ba-458b-9d3b-88032af14d4f\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://savantcat.cn/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"a90e2c72-76ba-458b-9d3b-88032af14d4f\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\na90e2c72-76ba-458b-9d3b-88032af14d4f\" at the same path and POST {\"id\":\"a90e2c72-76ba-458b-9d3b-88032af14d4f\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"bb8a0e59-c534-4061-9c14-2f94d2b75528","url":"https://api.agishub.com/mcp/webhook","name":"AgisHub Webhook Relay","description":"Fire-and-forget webhooks for agents with guaranteed delivery, automatic retries, and status polling via x402.","tags":["webhook","messaging","mcp","x402"],"tier":"free","lastSeenAlive":1793816196641,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\nbb8a0e59-c534-4061-9c14-2f94d2b75528\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://api.agishub.com/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"bb8a0e59-c534-4061-9c14-2f94d2b75528\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\nbb8a0e59-c534-4061-9c14-2f94d2b75528\" at the same path and POST {\"id\":\"bb8a0e59-c534-4061-9c14-2f94d2b75528\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"c6c32fc4-bd16-4db7-8d2e-6e2211ac7f11","url":"https://flapjax-check.run402.com","name":"FlapJax Agent/Wallet Checker","description":"Pay-per-call x402 API returning an agent-likeness score (ERC-8004 registry plus public BSC-agent crawl), sybil first-funder cluster flags, FLAPJAX holding, and basic BSC/Base chain facts. $0.02 USDC per call over x402 on Base mainnet. Operated by FlapJax; revenue is earmarked for FLAPJAX buybacks.","tags":["x402","base","usdc","wallets","sybil","erc-8004","agents","flapjax"],"tier":"free","lastSeenAlive":1793815902415,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_OK","operator":false,"provenance":"owner","claimable":false,"claim":null,"consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"d3bcc6e9-e026-41a7-b130-da02a31ba849","url":"https://sati-grumpy.fly.dev/mcp","name":"Salvage & Surplus (sati-grumpy)","description":"MCP commerce surface for refurbished datacenter hardware (GPU rigs, servers, storage). Inventory search, cart, checkout with x402 agent-payment discovery.","tags":["commerce","hardware","x402","inventory"],"tier":"free","lastSeenAlive":1793815901433,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. You can take this row over, or have it removed immediately and unconditionally, with one signature from the wallet this service publishes as its x402 `payTo` -- no account, no signup. POST {\"id\":\"d3bcc6e9-e026-41a7-b130-da02a31ba849\",\"action\":\"claim\"} to https://agent-exec.448c.org/listings/claim with header X-Signature = personal_sign(\"agent-exec:listing:claim:v1\\nd3bcc6e9-e026-41a7-b130-da02a31ba849\"). To be removed instead, send action \"remove\" and sign \"agent-exec:listing:remove:v1\\nd3bcc6e9-e026-41a7-b130-da02a31ba849\" -- a DIFFERENT message on purpose, so a claim can never be replayed as a takedown. Removal is honoured on the same wallet, with no questions asked and no retention. On a claim the row becomes yours and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"4971b488-9007-4549-9f8c-1894395e23ae","url":"https://mcp.pops4.com/mcp","name":"POPS4","description":"AI-native corporate gifting and event infrastructure. Search 70,000+ SKU catalog, generate event programs with P&L, get wholesale quotes. For enterprise events.","tags":["corporate-gifting","events","catalog"],"tier":"free","lastSeenAlive":1793815900063,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n4971b488-9007-4549-9f8c-1894395e23ae\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://mcp.pops4.com/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"4971b488-9007-4549-9f8c-1894395e23ae\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n4971b488-9007-4549-9f8c-1894395e23ae\" at the same path and POST {\"id\":\"4971b488-9007-4549-9f8c-1894395e23ae\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"2b833901-8d9e-4eb1-9646-9942aaa30b5c","url":"https://yhwcaodofmbusjurawhp.supabase.co/functions/v1/mcp/rpc","name":"NCTR Alliance Rewards","description":"Rewards program discovery and interaction MCP. Search bounties, check earning rates and tier progression, get promotions, discover impact communities.","tags":["rewards","loyalty","bounties"],"tier":"free","lastSeenAlive":1793815899443,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_OK","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n2b833901-8d9e-4eb1-9646-9942aaa30b5c\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://yhwcaodofmbusjurawhp.supabase.co/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"2b833901-8d9e-4eb1-9646-9942aaa30b5c\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n2b833901-8d9e-4eb1-9646-9942aaa30b5c\" at the same path and POST {\"id\":\"2b833901-8d9e-4eb1-9646-9942aaa30b5c\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"d0600b62-3f7e-42f6-8e70-527a0b527203","url":"https://mcp.hirenimbus.com/mcp","name":"HireNimbus","description":"Home services platform MCP for provider search, profiles, reviews, booking requests, and follow-up. Self-hostable with OAuth 2.0 support and rate limiting.","tags":["home-services","booking","provider-search"],"tier":"free","lastSeenAlive":1793815898662,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\nd0600b62-3f7e-42f6-8e70-527a0b527203\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://mcp.hirenimbus.com/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"d0600b62-3f7e-42f6-8e70-527a0b527203\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\nd0600b62-3f7e-42f6-8e70-527a0b527203\" at the same path and POST {\"id\":\"d0600b62-3f7e-42f6-8e70-527a0b527203\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"ddc469de-b679-47ee-8e05-5f699d78b553","url":"https://apizone.io/api/mcp","name":"APIzone","description":"Real-time status and uptime monitoring for 294+ popular APIs (Stripe, OpenAI, AWS, GitHub, Twilio). Independent probes from own infrastructure report actual observed status.","tags":["api-status","uptime-monitoring","incidents"],"tier":"free","lastSeenAlive":1793815897622,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\nddc469de-b679-47ee-8e05-5f699d78b553\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://apizone.io/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"ddc469de-b679-47ee-8e05-5f699d78b553\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\nddc469de-b679-47ee-8e05-5f699d78b553\" at the same path and POST {\"id\":\"ddc469de-b679-47ee-8e05-5f699d78b553\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"a128164f-e349-46dd-9683-4b5ff0f5716d","url":"https://quorum-api-j15n.onrender.com/mcp","name":"Quorum","description":"Market evidence with verifiable receipts. Every claim resolves to a real stored record agents can fetch and verify. Prevents fabricated citations by design.","tags":["market-research","evidence","verification"],"tier":"free","lastSeenAlive":1793815896914,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\na128164f-e349-46dd-9683-4b5ff0f5716d\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://quorum-api-j15n.onrender.com/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"a128164f-e349-46dd-9683-4b5ff0f5716d\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\na128164f-e349-46dd-9683-4b5ff0f5716d\" at the same path and POST {\"id\":\"a128164f-e349-46dd-9683-4b5ff0f5716d\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"d3a3c865-d3f9-4ab1-91f6-e5257447ff17","url":"https://mcp.agentgauge.ai/mcp","name":"AgentGauge","description":"Scan websites for AI readiness: AI search visibility (citability, llms.txt, schema, crawler access) and agent usability (tools, identity, commerce). Free scanning with AgentReady standard conformance grading.","tags":["ai-readiness","website-audit","agent-tools"],"tier":"free","lastSeenAlive":1793815895831,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\nd3a3c865-d3f9-4ab1-91f6-e5257447ff17\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://mcp.agentgauge.ai/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"d3a3c865-d3f9-4ab1-91f6-e5257447ff17\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\nd3a3c865-d3f9-4ab1-91f6-e5257447ff17\" at the same path and POST {\"id\":\"d3a3c865-d3f9-4ab1-91f6-e5257447ff17\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"2c451653-32d2-4371-8d7d-b615ff46d512","url":"https://mcp.scarai.xyz/mcp","name":"web3ctx","description":"Version-true web3 docs, ABIs, and human-validated integration recipes served as tools over MCP. 632 integration projects, 1.35M units, 26 curated recipes.","tags":["web3","integration","recipes","abi"],"tier":"free","lastSeenAlive":1793815895351,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n2c451653-32d2-4371-8d7d-b615ff46d512\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://mcp.scarai.xyz/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"2c451653-32d2-4371-8d7d-b615ff46d512\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n2c451653-32d2-4371-8d7d-b615ff46d512\" at the same path and POST {\"id\":\"2c451653-32d2-4371-8d7d-b615ff46d512\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"14ea5cd6-28dd-4015-a652-a6b70550cc22","url":"https://humanitycommons.org/mcp","name":"Humanity Commons","description":"Federated public knowledge layer with provenance, uncertainty, references, visible disagreement. External agents can contribute, verify, and challenge structured records.","tags":["knowledge","collaboration","provenance","agents"],"tier":"free","lastSeenAlive":1793815608726,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_OK","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n14ea5cd6-28dd-4015-a652-a6b70550cc22\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://humanitycommons.org/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"14ea5cd6-28dd-4015-a652-a6b70550cc22\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n14ea5cd6-28dd-4015-a652-a6b70550cc22\" at the same path and POST {\"id\":\"14ea5cd6-28dd-4015-a652-a6b70550cc22\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"80314efc-cd84-4ced-b737-738c980783ba","url":"https://api.socialfetch.dev","name":"SocialFetch","description":"Social media data APIs covering TikTok, Instagram, YouTube, Twitter/X, LinkedIn, Reddit.","tags":["social","data","agents"],"tier":"free","lastSeenAlive":1793815608052,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_OK","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n80314efc-cd84-4ced-b737-738c980783ba\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://api.socialfetch.dev/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"80314efc-cd84-4ced-b737-738c980783ba\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n80314efc-cd84-4ced-b737-738c980783ba\" at the same path and POST {\"id\":\"80314efc-cd84-4ced-b737-738c980783ba\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"cd32a7bf-f486-4e11-ad2f-f25e57ffffba","url":"https://safety.openpulsechain.com/api/v1/alerts/recent","name":"OpenPulsechain Token Safety","description":"PulseChain analytics for agents: token safety scores, DEX pair analytics, deployer reputation, whale alerts and AML funding-tree tracing.","tags":["onchain","token-safety","analytics","x402","mcp"],"tier":"free","lastSeenAlive":1793815607654,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_OK","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. You can take this row over, or have it removed immediately and unconditionally, with one signature from the wallet this service publishes as its x402 `payTo` -- no account, no signup. POST {\"id\":\"cd32a7bf-f486-4e11-ad2f-f25e57ffffba\",\"action\":\"claim\"} to https://agent-exec.448c.org/listings/claim with header X-Signature = personal_sign(\"agent-exec:listing:claim:v1\\ncd32a7bf-f486-4e11-ad2f-f25e57ffffba\"). To be removed instead, send action \"remove\" and sign \"agent-exec:listing:remove:v1\\ncd32a7bf-f486-4e11-ad2f-f25e57ffffba\" -- a DIFFERENT message on purpose, so a claim can never be replayed as a takedown. Removal is honoured on the same wallet, with no questions asked and no retention. On a claim the row becomes yours and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"335a45ab-7387-449a-be0a-2de8191aee3e","url":"https://dartapi.ljaysk.com/v1/events","name":"KR-DART Events","description":"Korean corporate disclosure (DART) filings as a cursor-based event stream polled every 15s, classified into 31 categories with importance scores and English labels.","tags":["filings","korea","market-data","x402","regulatory"],"tier":"free","lastSeenAlive":1793815607209,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_OK","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. You can take this row over, or have it removed immediately and unconditionally, with one signature from the wallet this service publishes as its x402 `payTo` -- no account, no signup. POST {\"id\":\"335a45ab-7387-449a-be0a-2de8191aee3e\",\"action\":\"claim\"} to https://agent-exec.448c.org/listings/claim with header X-Signature = personal_sign(\"agent-exec:listing:claim:v1\\n335a45ab-7387-449a-be0a-2de8191aee3e\"). To be removed instead, send action \"remove\" and sign \"agent-exec:listing:remove:v1\\n335a45ab-7387-449a-be0a-2de8191aee3e\" -- a DIFFERENT message on purpose, so a claim can never be replayed as a takedown. Removal is honoured on the same wallet, with no questions asked and no retention. On a claim the row becomes yours and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"119c2270-12a8-4d3a-b180-107a93e30451","url":"https://api.quantoracle.dev/v1/stats/zscore","name":"QuantOracle","description":"63 deterministic quantitative calculators plus 10 composite workflows covering options, derivatives, risk, portfolio optimisation, statistics, FX and macro. Returns JSON, paid per call over x402.","tags":["quant","finance","derivatives","x402","a2a"],"tier":"free","lastSeenAlive":1793815605923,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. You can take this row over, or have it removed immediately and unconditionally, with one signature from the wallet this service publishes as its x402 `payTo` -- no account, no signup. POST {\"id\":\"119c2270-12a8-4d3a-b180-107a93e30451\",\"action\":\"claim\"} to https://agent-exec.448c.org/listings/claim with header X-Signature = personal_sign(\"agent-exec:listing:claim:v1\\n119c2270-12a8-4d3a-b180-107a93e30451\"). To be removed instead, send action \"remove\" and sign \"agent-exec:listing:remove:v1\\n119c2270-12a8-4d3a-b180-107a93e30451\" -- a DIFFERENT message on purpose, so a claim can never be replayed as a takedown. Removal is honoured on the same wallet, with no questions asked and no retention. On a claim the row becomes yours and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"48bb7168-e2a0-4dbe-a4e2-cb271f00acca","url":"https://gtfi.ai/mcp","name":"GroundTruth","description":"Subsurface scan QA and trade estimating. Two independent AI models read GPR and pipe scans to flag no-core zones.","tags":["subsurface","gpr","ai","mcp"],"tier":"free","lastSeenAlive":1793815605000,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n48bb7168-e2a0-4dbe-a4e2-cb271f00acca\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://gtfi.ai/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"48bb7168-e2a0-4dbe-a4e2-cb271f00acca\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n48bb7168-e2a0-4dbe-a4e2-cb271f00acca\" at the same path and POST {\"id\":\"48bb7168-e2a0-4dbe-a4e2-cb271f00acca\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"f4f3feec-6d2a-46d6-9fb3-4844db397636","url":"https://getminds.ai/mcp","name":"Minds","description":"Run AI market research: synthetic customer panels for concept testing, message testing, and segmentation.","tags":["research","synthetic","marketing","mcp"],"tier":"free","lastSeenAlive":1793815604095,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_OK","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\nf4f3feec-6d2a-46d6-9fb3-4844db397636\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://getminds.ai/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"f4f3feec-6d2a-46d6-9fb3-4844db397636\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\nf4f3feec-6d2a-46d6-9fb3-4844db397636\" at the same path and POST {\"id\":\"f4f3feec-6d2a-46d6-9fb3-4844db397636\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"eb6bcc49-b035-44d6-a989-d35c89f35290","url":"https://framethrower.ai/api/mcp","name":"FrameThrower","description":"Film stills from 5,489 films, searchable by lighting, lens character, shot size, colour and mood.","tags":["film","visual","search","mcp"],"tier":"free","lastSeenAlive":1793815597846,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_OK","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\neb6bcc49-b035-44d6-a989-d35c89f35290\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://framethrower.ai/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"eb6bcc49-b035-44d6-a989-d35c89f35290\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\neb6bcc49-b035-44d6-a989-d35c89f35290\" at the same path and POST {\"id\":\"eb6bcc49-b035-44d6-a989-d35c89f35290\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"72804dc3-36f1-4819-82ea-f1b264457dbe","url":"https://mcp.foura.ai/mcp","name":"Foura","description":"Web scraping for AI agents: fetch any page via proxy or full browser, bypassing anti-bot defenses.","tags":["scrape","web","proxy","mcp"],"tier":"free","lastSeenAlive":1793815597370,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n72804dc3-36f1-4819-82ea-f1b264457dbe\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://mcp.foura.ai/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"72804dc3-36f1-4819-82ea-f1b264457dbe\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n72804dc3-36f1-4819-82ea-f1b264457dbe\" at the same path and POST {\"id\":\"72804dc3-36f1-4819-82ea-f1b264457dbe\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"a3cf8462-1e32-41b7-89ee-58e8ea31fde3","url":"https://mcp.example4.ai/mcp","name":"xmp4","description":"Semantic code intelligence with SCIP over 856 pre-indexed OSS libraries. Hosted, free.","tags":["code","semantic","oss","mcp"],"tier":"free","lastSeenAlive":1793815597026,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\na3cf8462-1e32-41b7-89ee-58e8ea31fde3\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://mcp.example4.ai/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"a3cf8462-1e32-41b7-89ee-58e8ea31fde3\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\na3cf8462-1e32-41b7-89ee-58e8ea31fde3\" at the same path and POST {\"id\":\"a3cf8462-1e32-41b7-89ee-58e8ea31fde3\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"9410f8f8-af71-4134-bb40-e75b07515551","url":"https://mcp.exa.ai/mcp","name":"Exa","description":"Fast, intelligent web search and web crawling. Exa-code is a context tool for coding.","tags":["search","crawl","web","mcp"],"tier":"free","lastSeenAlive":1793815596665,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n9410f8f8-af71-4134-bb40-e75b07515551\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://mcp.exa.ai/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"9410f8f8-af71-4134-bb40-e75b07515551\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n9410f8f8-af71-4134-bb40-e75b07515551\" at the same path and POST {\"id\":\"9410f8f8-af71-4134-bb40-e75b07515551\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"2eee0de7-a3a7-4cfb-9261-a438aaf80e51","url":"https://mcp.sendraven.ai/mcp","name":"SendRaven","description":"Email infrastructure MCP for agents: send, read reply threads, run campaigns—priced per email, no per-contact cost, with per-API-key rate limits.","tags":["email","campaigns","agents","infrastructure"],"tier":"free","lastSeenAlive":1793815596176,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n2eee0de7-a3a7-4cfb-9261-a438aaf80e51\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://mcp.sendraven.ai/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"2eee0de7-a3a7-4cfb-9261-a438aaf80e51\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n2eee0de7-a3a7-4cfb-9261-a438aaf80e51\" at the same path and POST {\"id\":\"2eee0de7-a3a7-4cfb-9261-a438aaf80e51\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"66d89dce-1dfe-483d-a8b9-1bcfd93c9203","url":"https://api.riskstate.ai/mcp","name":"RiskState","description":"Crypto risk engine MCP providing live BTC/ETH risk policy, market structure, and trade playbooks from 30+ signals—free public tier requires no key.","tags":["crypto","risk","trading","agents"],"tier":"free","lastSeenAlive":1793815595579,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n66d89dce-1dfe-483d-a8b9-1bcfd93c9203\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://api.riskstate.ai/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"66d89dce-1dfe-483d-a8b9-1bcfd93c9203\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n66d89dce-1dfe-483d-a8b9-1bcfd93c9203\" at the same path and POST {\"id\":\"66d89dce-1dfe-483d-a8b9-1bcfd93c9203\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"85b017a2-1194-426c-9c00-ec0716937078","url":"https://www.tlders.com/api/mcp","name":"TLDers Domain Prices","description":"Compare domain prices across 145+ registrars and 1,100+ TLDs. Find promotions and check availability.","tags":["domains","pricing","commerce"],"tier":"free","lastSeenAlive":1793815295374,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n85b017a2-1194-426c-9c00-ec0716937078\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://www.tlders.com/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"85b017a2-1194-426c-9c00-ec0716937078\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n85b017a2-1194-426c-9c00-ec0716937078\" at the same path and POST {\"id\":\"85b017a2-1194-426c-9c00-ec0716937078\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"0120fea1-d33f-4da8-9767-41f98878e9fa","url":"https://app.relvato.com/api/mcp","name":"Relvato","description":"Website monitoring: list sites, run scans, read results, and generate remediation prompts via MCP.","tags":["monitoring","website","security"],"tier":"free","lastSeenAlive":1793815008648,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n0120fea1-d33f-4da8-9767-41f98878e9fa\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://app.relvato.com/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"0120fea1-d33f-4da8-9767-41f98878e9fa\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n0120fea1-d33f-4da8-9767-41f98878e9fa\" at the same path and POST {\"id\":\"0120fea1-d33f-4da8-9767-41f98878e9fa\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"8c5c95c4-63c6-4649-9751-f81afa67311c","url":"https://mcp.polyxd.com/mcp","name":"Polyxd","description":"Write, validate and render Polyxd UI documents as real screens in any design system package.","tags":["ui","design","documents"],"tier":"free","lastSeenAlive":1793815008021,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n8c5c95c4-63c6-4649-9751-f81afa67311c\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://mcp.polyxd.com/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"8c5c95c4-63c6-4649-9751-f81afa67311c\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n8c5c95c4-63c6-4649-9751-f81afa67311c\" at the same path and POST {\"id\":\"8c5c95c4-63c6-4649-9751-f81afa67311c\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"e5eaf79f-17ff-497b-87f3-6221d597adb6","url":"https://www.oxfordledge.com/mcp","name":"Oxford Ledge","description":"Access public SEC filings, 13F holdings, insider trades, and BDC loan data through agent queries.","tags":["finance","sec","data","trading"],"tier":"free","lastSeenAlive":1793815007169,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_OK","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\ne5eaf79f-17ff-497b-87f3-6221d597adb6\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://www.oxfordledge.com/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"e5eaf79f-17ff-497b-87f3-6221d597adb6\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\ne5eaf79f-17ff-497b-87f3-6221d597adb6\" at the same path and POST {\"id\":\"e5eaf79f-17ff-497b-87f3-6221d597adb6\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"2d982748-3a45-4647-b748-886a48a69075","url":"https://growingupvideo.com/mcp","name":"GrowingUpVideo","description":"Create AI morphing videos showing how a person, couple or pet changes across years from photos.","tags":["video","ai","morphing","photos"],"tier":"free","lastSeenAlive":1793815006137,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n2d982748-3a45-4647-b748-886a48a69075\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://growingupvideo.com/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"2d982748-3a45-4647-b748-886a48a69075\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n2d982748-3a45-4647-b748-886a48a69075\" at the same path and POST {\"id\":\"2d982748-3a45-4647-b748-886a48a69075\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"233104cc-2380-4d8a-96f6-89519a14dbc5","url":"https://mcp.furringline.com","name":"FURRINGLINE","description":"Thai building materials: product search, pricing before VAT, stock levels, and material calculators.","tags":["materials","commerce","thailand","search"],"tier":"free","lastSeenAlive":1793815005301,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_OK","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n233104cc-2380-4d8a-96f6-89519a14dbc5\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://mcp.furringline.com/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"233104cc-2380-4d8a-96f6-89519a14dbc5\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n233104cc-2380-4d8a-96f6-89519a14dbc5\" at the same path and POST {\"id\":\"233104cc-2380-4d8a-96f6-89519a14dbc5\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"be0a0456-660f-41c4-970c-6c81c730fcd6","url":"https://mcp.brianbooms.com/mcp","name":"Quiet Menders","description":"Privacy-focused pay-per-call data APIs for AI agents via x402 wallet. Data access without storing keys.","tags":["data","privacy","pay-per-call","x402"],"tier":"free","lastSeenAlive":1793815004666,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\nbe0a0456-660f-41c4-970c-6c81c730fcd6\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://mcp.brianbooms.com/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"be0a0456-660f-41c4-970c-6c81c730fcd6\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\nbe0a0456-660f-41c4-970c-6c81c730fcd6\" at the same path and POST {\"id\":\"be0a0456-660f-41c4-970c-6c81c730fcd6\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"13c6d302-b455-49d5-98a3-1c518fed6ef5","url":"https://mcp.rightcard.ai/mcp","name":"RightCard","description":"Stateless credit card selector MCP: determines which card earns best at any merchant from bank-verified reward data, no login or account required.","tags":["finance","cards","rewards","agents"],"tier":"free","lastSeenAlive":1793815004047,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_OK","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n13c6d302-b455-49d5-98a3-1c518fed6ef5\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://mcp.rightcard.ai/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"13c6d302-b455-49d5-98a3-1c518fed6ef5\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n13c6d302-b455-49d5-98a3-1c518fed6ef5\" at the same path and POST {\"id\":\"13c6d302-b455-49d5-98a3-1c518fed6ef5\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"8c188ffa-434b-49c0-88e3-8903d9cfb9a7","url":"https://mcp.ravenmcp.ai/api/mcp","name":"Raven","description":"Design intelligence MCP for coding agents: design principles, UI patterns, accessibility audits, design tokens, and brand guidance from Nielsen and WCAG standards.","tags":["design","code","agents","patterns"],"tier":"free","lastSeenAlive":1793815003153,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n8c188ffa-434b-49c0-88e3-8903d9cfb9a7\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://mcp.ravenmcp.ai/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"8c188ffa-434b-49c0-88e3-8903d9cfb9a7\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n8c188ffa-434b-49c0-88e3-8903d9cfb9a7\" at the same path and POST {\"id\":\"8c188ffa-434b-49c0-88e3-8903d9cfb9a7\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"1767cf78-7edd-4550-8822-2ac5820b3f19","url":"https://radmail.ai/api/mcp/sandbox","name":"RadMail","description":"Email triage, search, and hard-stop protections against money transfers, banking changes, and prompt injection—zero-auth sandbox MCP for agents.","tags":["email","safety","agents","sandbox"],"tier":"free","lastSeenAlive":1793815002530,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_OK","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n1767cf78-7edd-4550-8822-2ac5820b3f19\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://radmail.ai/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"1767cf78-7edd-4550-8822-2ac5820b3f19\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n1767cf78-7edd-4550-8822-2ac5820b3f19\" at the same path and POST {\"id\":\"1767cf78-7edd-4550-8822-2ac5820b3f19\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"307681da-8759-408c-ab5d-b27331cd496c","url":"https://crypto.api.trendsmcp.ai/mcp","name":"Crypto Trends MCP","description":"Cryptocurrency token and narrative trend volume over time with growth signals. Monitor crypto market sentiment and adoption trends.","tags":["crypto","trends","tokens","sentiment","analytics"],"tier":"free","lastSeenAlive":1793815002055,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n307681da-8759-408c-ab5d-b27331cd496c\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://crypto.api.trendsmcp.ai/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"307681da-8759-408c-ab5d-b27331cd496c\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n307681da-8759-408c-ab5d-b27331cd496c\" at the same path and POST {\"id\":\"307681da-8759-408c-ab5d-b27331cd496c\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"0731eea9-716e-4841-82e8-71fdb72796b2","url":"https://content-strategy.api.trendsmcp.ai/mcp","name":"Content Strategy Trends MCP","description":"Identify topics gaining momentum before they peak. Trend volume and growth signals across multiple sources for content planning and strategy.","tags":["trends","content","momentum","strategy","analytics"],"tier":"free","lastSeenAlive":1793815001173,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n0731eea9-716e-4841-82e8-71fdb72796b2\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://content-strategy.api.trendsmcp.ai/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"0731eea9-716e-4841-82e8-71fdb72796b2\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n0731eea9-716e-4841-82e8-71fdb72796b2\" at the same path and POST {\"id\":\"0731eea9-716e-4841-82e8-71fdb72796b2\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"368dae9a-d7bf-4854-9b6b-a8ab049e2dee","url":"https://competitor-tracking.api.trendsmcp.ai/mcp","name":"Competitor Tracking Trends MCP","description":"Brand and competitor search trend volume over time with growth signals. Monitor trend momentum across 30+ data sources via one MCP connection.","tags":["trends","competitors","sentiment","growth","analytics"],"tier":"free","lastSeenAlive":1793815000487,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n368dae9a-d7bf-4854-9b6b-a8ab049e2dee\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://competitor-tracking.api.trendsmcp.ai/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"368dae9a-d7bf-4854-9b6b-a8ab049e2dee\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n368dae9a-d7bf-4854-9b6b-a8ab049e2dee\" at the same path and POST {\"id\":\"368dae9a-d7bf-4854-9b6b-a8ab049e2dee\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"733a7e3c-5e9c-44af-a14a-c6afdf9baef9","url":"https://app-store.api.trendsmcp.ai/mcp","name":"App Store Trends MCP","description":"App Store and Google Play download trends over time. Charts, growth metrics and rankings for iOS and Android apps, no signup required.","tags":["analytics","downloads","trends","mobile","data"],"tier":"free","lastSeenAlive":1793814999812,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n733a7e3c-5e9c-44af-a14a-c6afdf9baef9\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://app-store.api.trendsmcp.ai/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"733a7e3c-5e9c-44af-a14a-c6afdf9baef9\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n733a7e3c-5e9c-44af-a14a-c6afdf9baef9\" at the same path and POST {\"id\":\"733a7e3c-5e9c-44af-a14a-c6afdf9baef9\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"43959aec-dff8-4b7e-85c2-bb291f0f80ad","url":"https://tooldirectory.ai/api/mcp","name":"AI Tool Directory","description":"Search 2,000+ live AI tools with pricing, features and verified status. Maintains curated AI Graveyard dataset of defunct and acquired products.","tags":["discovery","tools","pricing","status","alternatives"],"tier":"free","lastSeenAlive":1793814998932,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_OK","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n43959aec-dff8-4b7e-85c2-bb291f0f80ad\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://tooldirectory.ai/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"43959aec-dff8-4b7e-85c2-bb291f0f80ad\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n43959aec-dff8-4b7e-85c2-bb291f0f80ad\" at the same path and POST {\"id\":\"43959aec-dff8-4b7e-85c2-bb291f0f80ad\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"333372d8-53bb-4c7f-9ac5-e345cfa5a529","url":"https://mcp.tickerscout.ai/mcp","name":"TickerScout","description":"SEC filings data layer: assembled financial statements (income, balance sheet, cash flow) for US public companies, no API key or signup required.","tags":["finance","SEC","statements","filings","data"],"tier":"free","lastSeenAlive":1793814998124,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n333372d8-53bb-4c7f-9ac5-e345cfa5a529\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://mcp.tickerscout.ai/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"333372d8-53bb-4c7f-9ac5-e345cfa5a529\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n333372d8-53bb-4c7f-9ac5-e345cfa5a529\" at the same path and POST {\"id\":\"333372d8-53bb-4c7f-9ac5-e345cfa5a529\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"f410726a-3cf4-41f7-bcfb-a3ad8532e781","url":"https://mcp.unulu.ai","name":"unulu","description":"AI agent website builder for link-in-bio sites. Agents create, read, update, and publish sites via MCP or REST API without authentication.","tags":["website-builder","mcp","rest-api"],"tier":"free","lastSeenAlive":1793814997353,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_OK","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\nf410726a-3cf4-41f7-bcfb-a3ad8532e781\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://mcp.unulu.ai/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"f410726a-3cf4-41f7-bcfb-a3ad8532e781\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\nf410726a-3cf4-41f7-bcfb-a3ad8532e781\" at the same path and POST {\"id\":\"f410726a-3cf4-41f7-bcfb-a3ad8532e781\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}},{"id":"2df52004-a908-41bd-b712-ae8d61d747b4","url":"https://apick.app/mcp/ai","name":"APICK AI","description":"LLM chat, text summarization, and text polishing services exposed as MCP tools for Korean and multilingual AI agents.","tags":["LLM","text-processing","summarization","Korean","MCP"],"tier":"free","lastSeenAlive":1793814996651,"paidUntil":null,"dead":false,"lastProbeCode":"PROBE_METHOD_NOT_ALLOWED","operator":false,"provenance":"curated","claimable":true,"claim":"agent-exec listed this service; it is NOT ours and we make no claim to it. It publishes no x402 card, so there is no wallet on file to check a signature against -- prove you control it instead by serving a file at its own origin: put the exact text \"agent-exec:listing:claim:v1\\n2df52004-a908-41bd-b712-ae8d61d747b4\\n<your wallet address, lowercase>\" (with your actual chosen wallet address in place of the placeholder, all lowercase, nothing else) at https://apick.app/.well-known/agent-exec-listing-claim.txt, then POST {\"id\":\"2df52004-a908-41bd-b712-ae8d61d747b4\",\"action\":\"claim\",\"newOwner\":\"<the SAME wallet address>\"} to https://agent-exec.448c.org/listings/claim with NO X-Signature header -- the file must name the exact address you send as newOwner, since binding them together is what stops a third party who never controlled this origin from claiming to a different address than the one you published. To be removed instead, put the exact text \"agent-exec:listing:remove:v1\n2df52004-a908-41bd-b712-ae8d61d747b4\" at the same path and POST {\"id\":\"2df52004-a908-41bd-b712-ae8d61d747b4\",\"action\":\"remove\"} the same way (no newOwner needed). A DIFFERENT file content per action on purpose, so a claim proof can never double as a takedown proof. Removal is honoured the moment the file is reachable, with no retention. On a claim the row transfers to newOwner and keeps its id, its age and its full uptime history. Full details: https://agent-exec.448c.org/llms.txt","consecutiveFailures":0,"deadSince":null,"evictsAt":null,"remedy":null,"promote":{"url":"https://agent-exec.448c.org/listings/promote","method":"POST","plans":[{"duration":"day","name":"day","days":1,"priceUsd":0.0667,"price":"$0.0667"},{"duration":"week","name":"week","days":7,"priceUsd":0.3333,"price":"$0.3333"},{"duration":"month","name":"month","days":30,"priceUsd":1,"price":"$1.0000"}]}}],"nextCursor":"eyJhc09mIjoxNzkzODE4NDkwNjg3LCJvZmZzZXQiOjUwfQ"}