Skip to content

RNWY MCP server

com.rnwy/rnwyrnwy.comstreamable-httpv0.6.0Scanned

Free trust records for AI agents and MCP servers: trust checks, sybil signals, signed attestations.

10 tools: 8 change things and 2 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

8 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the RNWY MCP server can do

The RNWY MCP server is published by rnwy.com, a domain the MCP Registry verified. It has 10 tools. It can create or change data (8 tools: trust_check, address_age, network_stats, reviewer_wallet and 4 more), but cannot delete data. 2 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 11, 2026, version 0.6.0.

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.

10 tools

Changes things 8Claude Code: ask
  • address_ageLook up wallet age in days for any address.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Look up wallet age in days for any address. The uncheatable signal; time cannot be faked.
  • commerce_statsCommerce activity for an agent or address; job count, unique counterparties, repeat client rate, total earnings.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Commerce activity for an agent or address; job count, unique counterparties, repeat client rate, total earnings. Covers Olas Mechs and Virtuals ACP protocols.
  • entityFull operator footprint for any wallet address — all agents owned, trust scores, sybil signals, wallet intelligence, and MCP servers associated with that operator.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Full operator footprint for any wallet address — all agents owned, trust scores, sybil signals, wallet intelligence, and MCP servers associated with that operator.
  • mcp_attestationES256-signed attestation for any MCP server.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    ES256-signed attestation for any MCP server. Returns risk score, threat findings, and a signed envelope verifiable against the JWKS endpoint using kid rnwy-mcp-v1.
  • network_statsNetwork-wide statistics; total agents by registry, chain distribution, commerce job counts, and and trust score tier distribution, live.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Network-wide statistics; total agents by registry, chain distribution, commerce job counts, and and trust score tier distribution, live.
  • reviewer_walletBehavior profile for any reviewer wallet; velocity, sweep patterns, score clustering, and sybil signals across the entire ERC-8004 ecosystem.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Behavior profile for any reviewer wallet; velocity, sweep patterns, score clustering, and sybil signals across the entire ERC-8004 ecosystem. Shows how this wallet behaves when reviewing agents.
  • risk_termsCounterparty risk intelligence for any agent.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Counterparty risk intelligence for any agent. Returns risk tier (low/moderate/elevated/high/severe/critical), raw trust signals, data coverage, and methodology reference. Designed for marketplace operators and escrow providers setting transaction parameters before a deal. Full methodology: https://rnwy.com/risk-intelligence
  • trust_checkPass/fail trust verdict for any AI agent across ERC-8004, Olas, or Virtuals registries.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Pass/fail trust verdict for any AI agent across ERC-8004, Olas, or Virtuals registries. Returns score, tier, badges, and reasoning.
Only reads 2Show 2 read-only tools
  • compare_agentsSide-by-side trust comparison of 2-10 agents, ranked by score with reviewer quality summary for each.No findings

    Why it is in this group

    • The name "compare_agents" says "compare": a word for reading.
    Description, as the server wrote it
    Side-by-side trust comparison of 2-10 agents, ranked by score with reviewer quality summary for each.
  • reviewer_analysisAnalyze wallet ages of every reviewer who left feedback on an agent.No findings

    Why it is in this group

    • The description's first verb is "analyze": a word for reading.
    Description, as the server wrote it
    Analyze wallet ages of every reviewer who left feedback on an agent. Detects sybil patterns like same-day wallet creation clusters.

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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

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.

Tools listed without sign-in

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

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
10
Protocol version
2025-06-18
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
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 10 tools that change things (10 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://rnwy.com/api/mcp: tools/list returned 11 tools to an anonymous client, including trust_check (write), reviewer_analysis (write), address_age (write), network_stats (write), reviewer_wallet (write) and 5 more

    What this check looks for

Posture changes

  1. Nov 18, 2026
    • Tools that change things, listed without credentials: 8 to 10

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

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

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 8 -> 10.View diff
    • Tools that change things, listed without credentials: 8 to 10

Install

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

claude mcp add --transport http rnwy https://rnwy.com/api/mcp
claude mcp add --transport http rnwy https://rnwy.com/api/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__rnwy__reviewer_analysis",
      "mcp__rnwy__compare_agents"
    ],
    "ask": [
      "mcp__rnwy__trust_check",
      "mcp__rnwy__address_age",
      "mcp__rnwy__network_stats",
      "mcp__rnwy__reviewer_wallet",
      "mcp__rnwy__commerce_stats",
      "mcp__rnwy__entity",
      "mcp__rnwy__mcp_attestation",
      "mcp__rnwy__risk_terms"
    ],
    "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 rnwy. Review it before you use it.

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/com.rnwy/rnwy/verify?hash=f7881bacbbc561d51d67f62fc3ec54d3cb93dd54899830cd2ccce92ec7155e2f" | jq -e '.changed == false'

Pinned hash f7881bacbbc5, from Nov 11, 2026, 01:18 UTC.

Watch

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

https://radar.anlyon.com/servers/com.rnwy/rnwy/changes.xml

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

Badge

Anlyon Radar badge for com.rnwy/rnwy
[![Anlyon Radar](https://radar.anlyon.com/badge/com.rnwy/rnwy.svg)](https://radar.anlyon.com/servers/com.rnwy/rnwy)

Source: MCP Registry. Synced Nov 11, 2026, 01:17 UTC.

RNWY MCP server: questions and answers

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

Is the RNWY MCP server safe?

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

Can the RNWY MCP server delete data?

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

Can the RNWY 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 RNWY MCP server have?

10 tools: 8 write, 2 read. trust_check, address_age, network_stats, reviewer_wallet, commerce_stats, entity, mcp_attestation, risk_terms and 2 more.

Does the RNWY MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the RNWY MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the RNWY MCP server changed its tools?

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