Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AgentPay (all tools)

REMOTE · AGENTPAY.AGENTPAY-APIS.WORKERS.DEV

Pay-per-call web extract, DNS/WHOIS/IP lookup, PDF/RSS/sitemap tools. x402 USDC on Base/Algorand.

+1 this week 81 Trust /100

Last scanned (6 hours ago)

Scores higher than 84% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Web Scraping

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 566 tokens (~70/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 31 Oct 26 +1
    • Stability: 0.97 → pass security
  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://agentpay.agentpay-apis.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agentpay-apis.workers.dev CN=YE1,O=Let's Encrypt,C=US 1 Oct 2026 30 Dec 2026 ECDSA 256 ECDSA-SHA384 6e781679bb5373a73eb6dbddd7fcaaa04f8
SANs: *.agentpay-apis.workers.dev, agentpay-apis.workers.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agentpay.agentpay-apis.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agentpay.agentpay-apis.workers.dev/mcp Verified 200
http (plaintext) http://agentpay.agentpay-apis.workers.dev/mcp Inconclusive 405
MCP tools · 8 exposed · ~473 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
extract_page ~69

Fetch a URL and return markdown, metadata and links. Costs $0.005 USDC per call (x402 or credits).

NameTypeReqDescription
maxCharsinteger–Max markdown characters (1000-200000, default 50000)
urlstringyeshttp(s) URL to read

No output schema declared.

No examples provided.

lookup_dns ~75

Resolve DNS records (A, AAAA, CNAME, MX, NS, TXT, SOA, CAA, PTR, SRV). Costs $0.005 USDC per call (x402 or credits).

NameTypeReqDescription
namestringyesHostname to resolve
typestring–Record type, default A

No output schema declared.

No examples provided.

lookup_domain_report ~52

One-call domain report: registration, DNS, email provider, SPF/DMARC, hosting. Costs $0.02 USDC per call (x402 or credits).

NameTypeReqDescription
domainstringyesDomain name

No output schema declared.

No examples provided.

lookup_ip ~47

IP network owner, range, country and reverse DNS. Costs $0.01 USDC per call (x402 or credits).

NameTypeReqDescription
ipstringyesIPv4 or IPv6 address

No output schema declared.

No examples provided.

lookup_whois ~54

Domain registration data (registrar, created/expires, status, nameservers) via RDAP. Costs $0.01 USDC per call (x402 or credits).

NameTypeReqDescription
domainstringyesDomain name

No output schema declared.

No examples provided.

tools_feed ~58

Parse an RSS, Atom or JSON Feed into normalized JSON items. Costs $0.005 USDC per call (x402 or credits).

NameTypeReqDescription
limitinteger–Max items (default 50)
urlstringyesFeed URL

No output schema declared.

No examples provided.

tools_pdf_text ~50

Extract per-page text from a PDF URL (up to 20MB). Costs $0.01 USDC per call (x402 or credits).

NameTypeReqDescription
urlstringyesURL of a PDF

No output schema declared.

No examples provided.

tools_sitemap ~68

List a site's URLs from its sitemaps (follows robots.txt and sitemap indexes). Costs $0.005 USDC per call (x402 or credits).

NameTypeReqDescription
limitinteger–Max URLs (default 5000)
urlstringyesSite origin or sitemap URL

No output schema declared.

No examples provided.

Install

How do I install the AgentPay (all tools) MCP server?

AgentPay (all tools) is a hosted endpoint at https://agentpay.agentpay-apis.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · agentpay.agentpay-apis.workers.dev

# add to Claude Code
claude mcp add --transport http noah-silver-agentpay-bundle 'https://agentpay.agentpay-apis.workers.dev/mcp'
Common questions

What is the AgentPay (all tools) MCP server?

AgentPay (all tools) is an MCP server listed in the public MCP registry as io.github.noah-silver/agentpay-bundle. Pay-per-call web extract, DNS/WHOIS/IP lookup, PDF/RSS/sitemap tools. x402 USDC on Base/Algorand. This page covers its hosted endpoint (https://agentpay.agentpay-apis.workers.dev/mcp).

Is the AgentPay (all tools) MCP server safe to use?

AgentPay (all tools) scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the AgentPay (all tools) MCP server expose?

AgentPay (all tools) exposes 8 tools: extract_page, lookup_dns, lookup_whois, lookup_ip, lookup_domain_report, and 3 more. Their descriptions and schemas cost roughly 473 tokens of context every time the server is loaded.

Does the AgentPay (all tools) MCP server require authentication?

No. We connected to AgentPay (all tools) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AgentPay (all tools) MCP server still maintained?

AgentPay (all tools) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.