Other · Remote MCP server
Agent Revenue Auditor
Free preflight and exact-price discovery for paid website and AI-agent audits.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.vandurmedries/agent-revenue-auditor- Version
- 0.5.1
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-08
- Updated
- 2026-09-08
- Publisher
- vandurmedries (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/vandurmedries) · how
- Repository
- github.com/vandurmedries/agent-revenue-auditor-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://agent-revenue-auditor.vandurmedries.workers.dev/mcp | None |
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
- Agent Revenue Auditor 0.5.1 · protocol 2025-06-18
- Tools discovered
- 3:
discover_products,get_purchase_instructions,preflight_website - Checked on
- 2026-10-05
How to connect Agent Revenue Auditor
Agent Revenue Auditor is a remote MCP server: there is nothing to install. Its endpoint is https://agent-revenue-auditor.vandurmedries.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.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
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 other servers
| Server | Runs |
|---|---|
| Agent Receipts MCPEU AI Act-ready audit trail: signed, tamper-evident receipts proving what your AI agents did. | Local · stdio |
| Agent RelayAgent Relay MCP: invite-based channels, agent contracts and per-side human approvals. | Local · stdio |
| Agent ReputationComplaint registry for paid agent transactions - check a seller before you pay, or file your own. | Remote · HTTPLive check: ✓ handshake |
| Agent RescueCross-session idempotency, URLs as schema-validated JSON, and a record of missing capabilities. | Remote · HTTPLive check: ✓ handshake |
| Agent Revenue NetworkDeterministic JSON, routing and verification tools for AI agents, paid via x402 USDC on Base. | Remote · HTTPLive check: ✓ handshake |
| Agent Runtime ProofVerify whether a local Agent or MCP runtime matches an approved artifact. | Local · stdio |
| Agent Services MCPMCP server: x402-paid & free tools for AI agents - provenance, quality scoring, action audit. | Local · stdio |
| Agent SniperSelf-custodial pump.fun sniper: arm strategies, snipe, manage positions. Simulate by default. | Local · stdio |