RNWY Trust Intelligence

REMOTE · RNWY.COM · SCANNED AUG 3

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

Available components

+4 this week 64 64 Trust /100

Trust breakdown (6 categories)

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 →

Endpoint Security63

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
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. See how to fix → View diagnostics → Unverified
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
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 Usability71

AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 817 tokens (~81/item across 10 items; 10 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities20

Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · rnwy.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.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
    }
  }
}

# add to OpenClaw

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

# ~/.hermes/config.yaml

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

// mcp.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 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.

2 Aug 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.
31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 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
29 Jul 26 +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.
28 Jul 26 +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.
27 Jul 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
26 Jul 26 60

First indexed and scored.

Show 6 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 2026 · Probed https://rnwy.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=rnwy.com	CN=WE1,O=Google Trust Services,C=US	12 Jun 2026	10 Sept 2026	ECDSA 256	ECDSA-SHA256	d9c052147b972ec3132e1f94832e0d4a
SANs: rnwy.com, *.rnwy.com
CN=WE1,O=Google Trust Services,C=US (CA)	CN=GTS Root R4,O=Google Trust Services LLC,C=US	13 Dec 2023	20 Feb 2029	ECDSA 256	ECDSA-SHA384	7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA)	CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE	15 Nov 2023	28 Jan 2028	ECDSA 384	SHA256-RSA	7fe530bf331343bedd821610493d8a1b

DNSSEC insecure

Validation of rnwy.com. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
com.	present	19718	13	Verified
rnwy.com.	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

Header	Value
strict-transport-security	max-age=63072000

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://rnwy.com/api/mcp	Verified	200
http (plaintext)	http://rnwy.com/api/mcp	HTTPS enforced	308	https://rnwy.com/api/mcp

MCP tools — 10 exposed · ~817 tokens

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.

Tool Tokens

address_age ~57

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

Input Output Examples

Name	Type	Req	Description
address	string	yes	Wallet address (0x...)
chain	string	—	Chain slug (optional, defaults to base)

No output schema declared.

No examples provided.

commerce_stats ~119

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

Input Output Examples

Name	Type	Req	Description
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)

No output schema declared.

No examples provided.

compare_agents ~70

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

Input Output Examples

Name	Type	Req	Description
agents	string	yes	Comma-separated chain:id pairs. Example: base:1380,base:16907
threshold	number	—	Pass/fail threshold (default 50)

No output schema declared.

No examples provided.

entity ~49

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

Input Output Examples

Name	Type	Req	Description
wallet	string	yes	Wallet address (0x...)

No output schema declared.

No examples provided.

mcp_attestation ~73

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 Output Examples

Name	Type	Req	Description
canonical_id	string	yes	MCP server canonical ID (e.g. vujasinovic/keycloak-source-mcp)

No output schema declared.

No examples provided.

network_stats ~38

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

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

reviewer_analysis ~51

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

Input Output Examples

Name	Type	Req	Description
chain	string	yes	Chain slug
id	string	yes	Agent ID

No output schema declared.

No examples provided.

reviewer_wallet ~93

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 Output Examples

Name	Type	Req	Description
address	string	yes	Wallet address (0x...)
chain	string	yes	Chain slug: base, ethereum, bnb, etc.
summary	boolean	—	If true, omits individual review list (default true)

No output schema declared.

No examples provided.

risk_terms ~137

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 Output Examples

Name	Type	Req	Description
agent_id	number	yes	Agent ID (integer)
chain	string	yes	Chain slug: base, ethereum, bnb, gnosis, avalanche, celo, arbitrum, polygon, monad, megaeth, optimism
registry	string	—	Registry: erc8004 (default), olas

No output schema declared.

No examples provided.

trust_check ~130

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

Input Output Examples

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

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	60
27 Jul	60
28 Jul	61
29 Jul	62
30 Jul	62
31 Jul	63
1 Aug	63
2 Aug	64
3 Aug	64