Productivity · Remote MCP server
AgentPay Doc Tools
Pay-per-call PDF to text, RSS/Atom to JSON, sitemap to URLs for agents. x402 USDC, Base/Algorand.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.noah-silver/agentpay-tools- Version
- 1.1.0
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP
- Published
- 2026-10-01
- Updated
- 2026-10-01
- Publisher
- noah-silver (GitHub) · 5 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/noah-silver) · how
- Listed under
- PDF MCP servers
- Website
- agentpay-tools.agentpay-apis.workers.dev
- Repository
- github.com/noah-silver/agentpay
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://agentpay-tools.agentpay-apis.workers.dev/mcp | Authorization (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- Doc Tools 1.1.0 · protocol 2025-06-18
- Tools discovered
- 3:
tools_pdf_text,tools_feed,tools_sitemap - Checked on
- 2026-10-05
How to connect AgentPay Doc Tools
AgentPay Doc Tools is a remote MCP server: there is nothing to install. Its endpoint is https://agentpay-tools.agentpay-apis.workers.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from noah-silver (GitHub)
| Server | Runs |
|---|---|
| AgentPay (all tools)Pay-per-call web extract, DNS/WHOIS/IP lookup, PDF/RSS/sitemap tools. x402 USDC on Base/Algorand. | Remote · HTTPLive check: ✓ handshake |
| AgentPay Domain & Network LookupPay-per-call DNS, WHOIS/RDAP, IP and domain reports for agents. x402 USDC on Base or Algorand. | Remote · HTTPLive check: ✓ handshake |
| AgentPay Web ExtractPay-per-call web page to markdown, metadata and links for agents. x402 USDC on Base or Algorand. | Remote · HTTPLive check: ✓ handshake |
| GridPulse: U.S. Energy DataU.S. grid mix, retail electricity prices and Henry Hub gas prices (EIA), paid per call via x402. | Local · stdio |
More productivity servers
| Server | Runs |
|---|---|
| AgentMeshBe an agent on the AgentMesh network: find agents, hire them, be hired, and read your mesh inbox. | Remote · HTTPLive check: sign-in required |
| AgentpackRepo-native task continuity for AI coding agents: a reviewed task-state ledger served over MCP. | Local · stdio |
| AgentPayX402 micropayments MCP: Xiaohongshu notes and paid APIs settled in USDC on Base. | Remote & Local · HTTP, stdioLive check: ✗ no handshake |
| AgentPingLet your AI agent notify you by email, Slack, Discord, or webhook. One tool: send_notification. | Remote · HTTPLive check: sign-in required |
| Agentrender MCPURL to screenshot, PDF, or structured extract for AI agents via MCP. | Local · stdio |
| AgentsProgrammatic control of the Hiro security platform: scans, tasks, plans, and approvals. | Remote · HTTPLive check: sign-in required |
| agentsbase - Email for AI AgentsEmail for AI agents. Create mailboxes, send/receive emails, and auto-extract verification codes. | Local · stdio |