Revenue Agent — OpenAPI Audit & Change Detection MCP Server

by prh Your server? Claim it

answering

Revenue Agent — OpenAPI Audit & Change Detection is answering right now. Last checked 11 min ago. It exposes 1 tools.

Paid OpenAPI audit and API change detection for agents. $0.10 USDC per analysis via x402 on Base.

Uptime history 55 hours of history

55 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

538 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Revenue Agent — OpenAPI Audit & Change Detection every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add revenue-agent --transport http https://agent.prh.news/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "revenue-agent": {
      "url": "https://agent.prh.news/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.revenue-agent]
url = "https://agent.prh.news/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "revenue-agent": {
      "url": "https://agent.prh.news/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "revenue-agent": {
      "url": "https://agent.prh.news/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

openapi

check_openapi

Audit a public OpenAPI/Swagger spec (JSON or YAML) for API contract changes: breaking-change detection, API drift detection and semantic specification comparison, suitable for ongoing spec monitoring. The paid analysis compares the spec with the service's last stored snapshot of that URL (the first check records the baseline) and returns a deterministic JSON report, classifying changes to endpoints, methods, request/response fields, types and required/optional status as breaking, potentially breaking, non-breaking or informational, plus a Markdown summary. Cost: 0.10 USDC per completed analysis via x402 on Base (eip155:8453), settled only after the analysis is computed. This MCP tool itself is free: it validates the URL and returns the x402 endpoint and payment terms; it does not run the analysis or move funds. To get the analysis, POST {"url": "<spec URL>"} to the returned endpoint with an x402-capable HTTP client.

Endpoints

URL	Transport	State	Latency	Checked
https://agent.prh.news/mcp	streamable-http	answering	586 ms	11 min ago

Alternatives to Revenue Agent — OpenAPI Audit & Change Detection

same job, measured the same way

X402 API

by fernsugi

DeFi data API for AI agents — pay-per-call via x402/USDC on Base

39 installs/wk local only

Agentreader MCP

by ajanani1

11 pay-per-call web tools for AI agents, auto-paid in USDC on Base via x402. No API keys.

21 installs/wk local only

Verdoc

by verdochello

Deterministic AGENTS.md and repo analysis for coding agents, paid per call in USDC over x402.

local only

Boo X402 MCP

by lucle87

Pay-per-call crypto data for AI agents. USDC on Base via x402. No API key.

34 installs/wk local only

Agent Embassy

by tacticalnoot

Agents pay for work and prove it. Verified checks $0.15, recovery $1.00. USDC on Base via x402.

5 tools answering

Agent Newsstand

by agentnewsstand

Market data and web intelligence for AI agents, paid per call in USDC on Base via x402.

16 tools answering

X402 MCP Server

by jmthomasofficial

JMT x402: 35 pay-per-call Base/USDC tools for agents, auto-paid via x402 v2. No API key.

57 installs/wk local only

Alien Plugg x402 API

by michaelhutchings626-hub

32 paid x402 endpoints for crypto, Zora & on-chain analysis. 10 MCP tools. USDC on Base.

10 tools answering

Revenue Agent — OpenAPI Audit & Change Detection — questions

Answers built from our own checks of this server.

What can Revenue Agent — OpenAPI Audit & Change Detection do?

It exposes 1 tools, read directly from the server on our last check. Among them: check_openapi. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Revenue Agent — OpenAPI Audit & Change Detection working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 538 ms. The bar chart above shows every period we have measured.

How do I connect Revenue Agent — OpenAPI Audit & Change Detection?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Revenue Agent — OpenAPI Audit & Change Detection need an API key?

No. Revenue Agent — OpenAPI Audit & Change Detection completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Revenue Agent — OpenAPI Audit & Change Detection?

It answers our handshake in 538 ms on average, which is faster than 28% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.