Skip to content

Revenue Agent — OpenAPI Audit & Change Detection MCP server

news.prh/revenue-agentprh.newsstreamable-httpv0.1.1Scanned

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

2 tools: 1 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 1 write, 1 read.
  • Reads private data · 1
  • Reads text others write · 2
  • Can send data out · 1
  • 1 finding

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Revenue Agent — OpenAPI Audit & Change Detection MCP server can do

The Revenue Agent — OpenAPI Audit & Change Detection MCP server is published by prh.news, a domain the MCP Registry verified. It has 2 tools. It can create or change data (1 tool: check_openapi), but cannot delete data. 1 tool only reads.

1 tool reads private data (compare_openapi); 2 tools bring in text other people can write (check_openapi and compare_openapi); 1 tool can send data out of your system (check_openapi). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.

Last scanned Nov 5, 2026, version 0.1.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Changes things 1Claude Code: ask
  • check_openapiDeveloper tool for OpenAPI audit, API analysis, Swagger analysis, and API contract change validation (not general OpenAPI conformance linting).Reads text others writeCan send data out1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Info

      The input schema at properties.url.description mentions "credentials".

      Matched text

      inputSchema.properties.url.description: "...ger JSON or YAML URL (http or https, no credentials or query string)"

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: OpenAPI Audit & Breaking-Change Detection
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • compare_openapiValidates explicit before and after public OpenAPI/Swagger URLs and returns purchase terms for an immediate deterministic semantic comparison, including structural oneOf/anyOf bran…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "compare_openapi" says "compare": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "validate" and "branch": it reads repositories.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Immediate Stateless OpenAPI Comparison
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

2 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__revenue-agent__check_openapi"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 19:16 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
502
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 502.

Posture changes

  1. Nov 20, 2026
    • HTTP status of an anonymous initialize: 200 to 502
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

1 info
  • The input schema at properties.url.description mentions "credentials".

    Matched text

    inputSchema.properties.url.description: "...ger JSON or YAML URL (http or https, no credentials or query string)"

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 502; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 1 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 502
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 0.1.1. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__revenue-agent__compare_openapi"
    ],
    "ask": [
      "mcp__revenue-agent__check_openapi"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as revenue-agent. Review it before you use it.

Capability tags behind 2 rules
  • mcp__revenue-agent__check_openapi untrusted-input, outbound
  • mcp__revenue-agent__compare_openapi private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/news.prh/revenue-agent/verify?hash=6eadbe753e573d5021f1fb5ff423ecb3d737217a5b93e9d042de7cf5859cb08a" | jq -e '.changed == false'

Pinned hash 6eadbe753e57, from Nov 5, 2026, 03:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/news.prh/revenue-agent/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for news.prh/revenue-agent
[![Anlyon Radar](https://radar.anlyon.com/badge/news.prh/revenue-agent.svg)](https://radar.anlyon.com/servers/news.prh/revenue-agent)

Source: MCP Registry. Synced Oct 21, 2026, 18:54 UTC.

Revenue Agent — OpenAPI Audit & Change Detection MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Revenue Agent — OpenAPI Audit & Change Detection MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Revenue Agent — OpenAPI Audit & Change Detection MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Revenue Agent — OpenAPI Audit & Change Detection MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Revenue Agent — OpenAPI Audit & Change Detection MCP server have?

2 tools: 1 write, 1 read. check_openapi and compare_openapi.

Does the Revenue Agent — OpenAPI Audit & Change Detection MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Revenue Agent — OpenAPI Audit & Change Detection MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_openapi.

Has the Revenue Agent — OpenAPI Audit & Change Detection MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 5, 2026.