RNWY Trust Intelligence
REMOTE · RNWY.COM · SCANNED SEP 20
Check if an AI agent is trustworthy. Sybil detection, signed attestations, 150,000+ agents. Free.
Available components
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 → Why this is hard to 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 Usability78
- AI-judged instruction clarity (excellent).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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the RNWY Trust Intelligence MCP server?
RNWY Trust Intelligence 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.
remote · rnwy.com
claude mcp add --transport http rnwy-mcp 'https://rnwy.com/api/mcp'
{
"mcpServers": {
"rnwy-mcp": {
"url": "https://rnwy.com/api/mcp"
}
}
} {
"servers": {
"rnwy-mcp": {
"type": "http",
"url": "https://rnwy.com/api/mcp"
}
}
} [mcp_servers.rnwy-mcp] url = "https://rnwy.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rnwy-mcp": {
"type": "remote",
"url": "https://rnwy.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add rnwy-mcp --url 'https://rnwy.com/api/mcp' --transport streamable-http
mcp_servers:
rnwy-mcp:
url: "https://rnwy.com/api/mcp" {
"McpServers": {
"rnwy-mcp": {
"Transport": "http",
"Url": "https://rnwy.com/api/mcp"
}
}
} assistant mcp add rnwy-mcp -t streamable-http -u 'https://rnwy.com/api/mcp'
{
"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.
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.
- 26 Aug 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
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 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
- 31 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
- 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
- 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 0
First indexed and scored.
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 20 Sept 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 | 10 Aug 2026 | 8 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 5f230290ef3a76d50e943f4915ec9be3 |
| 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
address_age ~57
Look up wallet age in days for any address. The uncheatable signal; time cannot be faked.
| 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.
| 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.
| 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.
| 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.
| 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 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.
| 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.
| 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
| 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.
| 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.
What is the RNWY Trust Intelligence MCP server?
RNWY Trust Intelligence is an MCP server listed in the public MCP registry as io.github.rnwy/mcp. Check if an AI agent is trustworthy. Sybil detection, signed attestations, 150,000+ agents. Free. This page covers its hosted endpoint (https://rnwy.com/api/mcp).
Is the RNWY Trust Intelligence MCP server safe to use?
RNWY Trust Intelligence 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 Trust Intelligence MCP server expose?
RNWY Trust Intelligence exposes 10 tools: trust_check, reviewer_analysis, compare_agents, address_age, network_stats, and 5 more. Their descriptions and schemas cost roughly 817 tokens of context every time the server is loaded.
Does the RNWY Trust Intelligence MCP server require authentication?
No. We connected to RNWY Trust Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RNWY Trust Intelligence MCP server still maintained?
RNWY Trust Intelligence is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.