# RNWY Trust Intelligence (remote · rnwy.com)

Check if an AI agent is trustworthy. Sybil detection, signed attestations, 150,000+ agents. Free.

- Trust score: 64/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

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

## Channel facts

- Endpoint: `https://rnwy.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 817 tokens (~81/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Other

```json
{
  "mcpServers": {
    "rnwy-mcp": {
      "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-08-02 (score 64, +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-07-31 (score 63, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 62, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 62, +1)

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

### 2026-07-28 (score 61, +1)

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

### 2026-07-27 (score 60, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 60)

First indexed and scored.

## MCP tools (10)

### `trust_check` (~130 tokens)

Pass/fail trust verdict for any AI agent across ERC-8004, Olas, or Virtuals registries. Returns score, tier, badges, and reasoning.

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` (~51 tokens)

Analyze wallet ages of every reviewer who left feedback on an agent. Detects sybil patterns like same-day wallet creation clusters.

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` (~57 tokens)

Look up wallet age in days for any address. The uncheatable signal; time cannot be faked.

Input parameters:

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

### `network_stats` (~38 tokens)

Network-wide statistics; total agents by registry, chain distribution, commerce job counts, and trust score tier distribution across 180,000+ indexed agents.

### `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` (~119 tokens)

Commerce activity for an agent or address; job count, unique counterparties, repeat client rate, total earnings. Covers Olas Mechs and Virtuals ACP protocols.

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

## Diagnostics

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

## Score history

- 2026-08-03: 64
- 2026-08-02: 64
- 2026-08-01: 63
- 2026-07-31: 63
- 2026-07-30: 62
- 2026-07-29: 62
- 2026-07-28: 61
- 2026-07-27: 60
- 2026-07-26: 60

## Links

- Remote endpoint: https://rnwy.com/api/mcp
- Repository: https://github.com/rnwy/mcp
- Changelog RSS feed: https://verifymcp.io/servers/rnwy-mcp/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/rnwy-mcp/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/rnwy-mcp/api-mcp