Agent MCP Server

Pay-per-call data tools for AI agents: crypto signal, web reader, SEO audit. x402 USDC on Base.

Local serverstdio

What is the Agent MCP server?

If you already use Agent, the agent mcp server is the piece that lets your assistant work with it directly. Pay-per-call data tools for AI agents: crypto signal, web reader, SEO audit. x402 USDC on Base.

What the server does

Pay-per-call data tools for AI agents, settled per call in USDC on Base via the x402 protocol. The buyer is another agent: it discovers an endpoint, auto-pays per request (HTTP 402 → payment → data), and gets structured JSON back. No API key, no signup, no account — the seller's only setup is one public wallet address.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • market_signal — GET /signal
  • web_read — GET /extract
  • repo_audit — GET /audit?owner=&repo=

Installation

PAY_TO on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Credentials and setup notes

Configuration is passed through the environment: CDP_API_KEY_ID, CDP_API_KEY_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Agent's toolset — market_signal, web_read, repo_audit — is a fair guide to whether it matches your workflow. It is maintained by dev.charliemorrison; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
market_signalGET /signal
web_readGET /extract
repo_auditGET /audit?owner=&repo=

How to install the Agent MCP server

{
  "mcpServers": {
    "agent-web-reader": {
      "command": "npx",
      "args": ["-y", "PAY_TO"],
      "env": {
        "CDP_API_KEY_ID": "your-value",
        "CDP_API_KEY_SECRET": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
CDP_API_KEY_IDCredential the server authenticates with.Yes
CDP_API_KEY_SECRETCredential the server authenticates with.Yes

Example prompts to try

  • Use Agent to market signal.
  • Use Agent to web read.
  • Use Agent to repo audit.

Frequently asked questions

It connects Agent to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (market_signal, web_read, repo_audit) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Agent directly.