# RNWY (remote · rnwy.com)

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

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `rnwy.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/com-rnwy-rnwy/api-mcp.md), [page](https://verifymcp.io/servers/com-rnwy-rnwy/api-mcp)

## Channel facts

- Endpoint: `https://rnwy.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.6.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1221 tokens (~111/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the RNWY MCP server?

RNWY is a hosted endpoint at https://rnwy.com/api/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.

### Claude

```bash
claude mcp add --transport http com-rnwy-rnwy 'https://rnwy.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-rnwy-rnwy": {
      "url": "https://rnwy.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-rnwy-rnwy": {
      "type": "http",
      "url": "https://rnwy.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-rnwy-rnwy]
url = "https://rnwy.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-rnwy-rnwy": {
      "type": "remote",
      "url": "https://rnwy.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-rnwy-rnwy --url 'https://rnwy.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-rnwy-rnwy:
    url: "https://rnwy.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-rnwy-rnwy": {
      "Transport": "http",
      "Url": "https://rnwy.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-rnwy-rnwy -t streamable-http -u 'https://rnwy.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-rnwy-rnwy": {
      "type": "http",
      "url": "https://rnwy.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 77, +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.

### 2026-11-16 (score 76, +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.

### 2026-11-15 (score 75, 0)

- [security] Tool “network_stats” rewrote its description, which is the text the model reads

### 2026-11-13 (score 75, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “address_age” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional] New tool “leave_note”
- [cosmetic] “address_age” reworded the description of “chain”

### 2026-11-12 (score 74, 0)

- [security] Tool “address_age” rewrote its description, which is the text the model reads
- [security] Tool “commerce_stats” rewrote its description, which is the text the model reads
- [security] Tool “network_stats” rewrote its description, which is the text the model reads
- [security] Tool “reviewer_analysis” rewrote its description, which is the text the model reads
- [security] Tool “trust_check” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03

### 2026-11-11 (score 74)

First indexed and scored.

## MCP tools (11)

### `trust_check` (~156 tokens)

Before dealing with an on-chain AI agent: a pass/fail trust verdict with score, tier, badges and the reasoning behind it, for ERC-8004, Olas or Virtuals agents. Each answer states the date its score was computed. Example: id 1380, chain base.

Input parameters:

- `chain` (string, required): Chain slug: ethereum, base, bnb, gnosis, avalanche, celo, arbitrum, polygon, monad, megaeth, optimism
- `id` (string, required): Agent ID (token ID or Mech ID)
- `registry` (string): Registry: erc8004 (default), olas, virtuals
- `threshold` (number): Pass/fail threshold (default 50)

### `reviewer_analysis` (~58 tokens)

Who reviewed this agent, and how old are their addresses? Returns the age of every reviewer address and flags patterns such as many addresses created on the same day.

Input parameters:

- `chain` (string, required): Chain slug
- `id` (string, required): Agent ID

### `compare_agents` (~70 tokens)

Side-by-side trust comparison of 2-10 agents, ranked by score with reviewer quality summary for each.

Input parameters:

- `agents` (string, required): Comma-separated chain:id pairs. Example: base:1380,base:16907
- `threshold` (number): Pass/fail threshold (default 50)

### `address_age` (~89 tokens)

Age in days of an address on Base or Ethereum, from its first recorded activity. The answer carries a status: known, no_history (looked up, nothing found on that chain) or unknown (the lookup failed); only known carries a number of days.

Input parameters:

- `address` (string, required): Wallet address (0x...)
- `chain` (string): base or ethereum (optional, defaults to base)

### `network_stats` (~50 tokens)

Network-wide statistics; total agents by registry, chain distribution, commerce job counts, trust score tier distribution, and every ERC-8004 registration on Ethereum, BNB Chain and Base counted from a daily list.

### `reviewer_wallet` (~93 tokens)

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.

Input parameters:

- `address` (string, required): Wallet address (0x...)
- `chain` (string, required): Chain slug: base, ethereum, bnb, etc.
- `summary` (boolean): If true, omits individual review list (default true)

### `commerce_stats` (~129 tokens)

Paid work history for an agent or address: job count, unique counterparties, repeat client rate, total earnings. Covers Olas Mechs and Virtuals ACP. Give either address, or id together with chain.

Input parameters:

- `address` (string): Wallet or contract address (0x...). Use this for Virtuals ACP lookups.
- `chain` (string): Chain slug (required with id)
- `id` (string): Agent ID. Use with chain and registry for linked agent commerce data.
- `registry` (string): Registry: erc8004, olas (default erc8004)

### `entity` (~49 tokens)

Full operator footprint for any wallet address — all agents owned, trust scores, sybil signals, wallet intelligence, and MCP servers associated with that operator.

Input parameters:

- `wallet` (string, required): Wallet address (0x...)

### `mcp_attestation` (~73 tokens)

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.

Input parameters:

- `canonical_id` (string, required): MCP server canonical ID (e.g. vujasinovic/keycloak-source-mcp)

### `risk_terms` (~137 tokens)

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

Input parameters:

- `agent_id` (number, required): Agent ID (integer)
- `chain` (string, required): Chain slug: base, ethereum, bnb, gnosis, avalanche, celo, arbitrum, polygon, monad, megaeth, optimism
- `registry` (string): Registry: erc8004 (default), olas

### `leave_note` (~189 tokens)

A private note to RNWY: what you were looking for and did not find, a request, a correction, a question. What callers ask for shapes what RNWY builds next. No name, email or key. Stored privately and read by a person at RNWY; never published; a reply is not promised. No IP address is stored with it. Limits: 5 notes per caller per UTC day, 2,000 characters.

Input parameters:

- `about_chain` (string): Optional: chain slug of an agent the note is about
- `about_id` (string): Optional: id of that agent
- `body` (string, required): The note, plain text, up to 2,000 characters
- `reply_to` (string): Optional: a way to reach the sender, up to 200 characters
- `signature` (string): Optional: a signature, up to 200 characters

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-rnwy-rnwy/api-mcp#diagnostics

## Score history

- 2026-11-21: 78
- 2026-11-20: 78
- 2026-11-19: 77
- 2026-11-18: 77
- 2026-11-17: 76
- 2026-11-16: 76
- 2026-11-15: 75
- 2026-11-14: 75
- 2026-11-13: 75
- 2026-11-12: 74
- 2026-11-11: 74

## Common questions

### What is the RNWY MCP server?

RNWY is an MCP server listed in the public MCP registry as com.rnwy/rnwy. Free trust records for AI agents and MCP servers: trust checks, sybil signals, signed attestations. This page covers its hosted endpoint (https://rnwy.com/api/mcp).

### Is the RNWY MCP server safe to use?

RNWY scores 78 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 RNWY MCP server expose?

RNWY exposes 11 tools: trust_check, reviewer_analysis, compare_agents, address_age, network_stats, and 6 more. Their descriptions and schemas cost roughly 1,093 tokens of context every time the server is loaded.

### Does the RNWY MCP server require authentication?

No. We connected to RNWY without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the RNWY MCP server still maintained?

RNWY is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the RNWY MCP server?

VerifyMCP ran 13 checks on RNWY, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://rnwy.com/api/mcp
- Website: https://rnwy.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-rnwy-rnwy/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-rnwy-rnwy/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-rnwy-rnwy/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-rnwy-rnwy/api-mcp
