Revenue Agent — OpenAPI Audit & Change Detection
REMOTE · AGENT.PRH.NEWS · SCANNED OCT 7
Paid OpenAPI audit and API change detection for agents. $0.10 USDC per analysis via x402 on Base.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 557 tokens (~278/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 33% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Revenue Agent — OpenAPI Audit & Change Detection MCP server?
Revenue Agent — OpenAPI Audit & Change Detection is a hosted endpoint at https://agent.prh.news/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · agent.prh.news
claude mcp add --transport http news-prh-revenue-agent 'https://agent.prh.news/mcp'
{
"mcpServers": {
"news-prh-revenue-agent": {
"url": "https://agent.prh.news/mcp"
}
}
} {
"servers": {
"news-prh-revenue-agent": {
"type": "http",
"url": "https://agent.prh.news/mcp"
}
}
} [mcp_servers.news-prh-revenue-agent] url = "https://agent.prh.news/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"news-prh-revenue-agent": {
"type": "remote",
"url": "https://agent.prh.news/mcp",
"enabled": true
}
}
} openclaw mcp add news-prh-revenue-agent --url 'https://agent.prh.news/mcp' --transport streamable-http
mcp_servers:
news-prh-revenue-agent:
url: "https://agent.prh.news/mcp" {
"McpServers": {
"news-prh-revenue-agent": {
"Transport": "http",
"Url": "https://agent.prh.news/mcp"
}
}
} assistant mcp add news-prh-revenue-agent -t streamable-http -u 'https://agent.prh.news/mcp'
{
"mcpServers": {
"news-prh-revenue-agent": {
"type": "http",
"url": "https://agent.prh.news/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 7 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 50 to 60. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_openapi” rewrote its description, which is the text the model reads security
- Schema quality: 338 → 375 ▼ functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 7 Oct 2026 · Probed https://agent.prh.news/mcp
TLS valid
Negotiated TLS 1.2 with TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agent.prh.news | CN=YE1,O=Let's Encrypt,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 53f25732625194adb9c085b5a5f3ef2a949 |
| SANs: agent.prh.news | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agent.prh.news. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| news. | present | 39979 | 8 | Verified |
| prh.news. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agent.prh.news/mcp | Verified | 200 | |
| http (plaintext) | http://agent.prh.news/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_openapi OpenAPI Audit & Breaking-Change Detection ~277
Developer tool for OpenAPI audit, API analysis, Swagger analysis, and API contract change validation (not general OpenAPI conformance linting). The paid analysis detects breaking changes and API drift by comparing a public OpenAPI/Swagger JSON or YAML contract with the service's last stored snapshot of that URL (the first check records the baseline). It returns deterministic JSON classifying endpoint, method, media-type, status, request/response field, type, requiredness, and structural oneOf/anyOf branch changes as breaking, potentially breaking, non-breaking or informational, plus a Markdown summary. It does not infer schema satisfiability or branch overlap; not and external references are unsupported. 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. Canonical service OpenAPI: https://agent.prh.news/openapi.json. To get the analysis, POST {"url": "<spec URL>"} to the returned endpoint with an x402-capable HTTP client.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public OpenAPI/Swagger JSON or YAML URL (http or https, no credentials or query string) |
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | – |
| openapi | string | yes | – |
| payment | object | yes | – |
| purchase | object | yes | – |
No examples provided.
compare_openapi Immediate Stateless OpenAPI Comparison ~134
Validates explicit before and after public OpenAPI/Swagger URLs and returns purchase terms for an immediate deterministic semantic comparison, including structural oneOf/anyOf branch changes. It does not infer schema satisfiability or branch overlap; not and external references are unsupported. The paid endpoint returns breaking, potentially breaking, non-breaking and informational findings plus Markdown without reading or advancing snapshot history. Cost: 0.25 USDC via x402 on Base (eip155:8453). This MCP tool is free and never executes analysis or moves funds.
| Name | Type | Req | Description |
|---|---|---|---|
| after_url | string | yes | – |
| before_url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | yes | – |
| openapi | string | yes | – |
| payment | object | yes | – |
| purchase | object | yes | – |
No examples provided.
What is the Revenue Agent — OpenAPI Audit & Change Detection MCP server?
Revenue Agent — OpenAPI Audit & Change Detection is an MCP server listed in the public MCP registry as news.prh/revenue-agent. Paid OpenAPI audit and API change detection for agents. $0.10 USDC per analysis via x402 on Base. This page covers its hosted endpoint (https://agent.prh.news/mcp).
Is the Revenue Agent — OpenAPI Audit & Change Detection MCP server safe to use?
Revenue Agent — OpenAPI Audit & Change Detection scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Revenue Agent — OpenAPI Audit & Change Detection MCP server expose?
Revenue Agent — OpenAPI Audit & Change Detection exposes 2 tools: check_openapi, compare_openapi. Their descriptions and schemas cost roughly 411 tokens of context every time the server is loaded.
Does the Revenue Agent — OpenAPI Audit & Change Detection MCP server require authentication?
No. We connected to Revenue Agent — OpenAPI Audit & Change Detection without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Revenue Agent — OpenAPI Audit & Change Detection MCP server still maintained?
Revenue Agent — OpenAPI Audit & Change Detection is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.