API Tools
prh.news
Audits OpenAPI/Swagger specifications for breaking changes, API drift, and semantic differences to support ongoing API contract monitoring.
ENDPOINT 1
https://agent.prh.news/mcp
MCP server metadata
- Name
- revenue-agent-mcp
- Version
- 0.1.1
Call check_openapi with a public OpenAPI/Swagger JSON or YAML URL to get purchase details (free). The analysis is delivered only by POSTing {"url": "<spec URL>"} to https://agent.prh.news/v1/check with an x402-aware HTTP client: the endpoint replies HTTP 402 with x402 v2 requirements (0.10 USDC, Base mainnet, exact scheme); pay and retry the same request to receive the JSON and Markdown change report. This MCP server never executes the check or moves funds.
Known tools 1
check_openapiAudit 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.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.revenue-agent-mcp]
url = "https://agent.prh.news/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"revenue-agent-mcp": {
"type": "http",
"url": "https://agent.prh.news/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: revenue-agent-mcp
Remote MCP URL: https://agent.prh.news/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"revenue-agent-mcp": {
"url": "https://agent.prh.news/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"revenue-agent-mcp": {
"type": "http",
"url": "https://agent.prh.news/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "revenue-agent-mcp",
"transport": "streamable-http",
"url": "https://agent.prh.news/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.