RNWY
REMOTE · RNWY.COM
Free trust records for AI agents and MCP servers: trust checks, sybil signals, signed attestations.
Available components
Last scanned (12 hours ago)
Scores higher than 72% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Security
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- 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 Usability75
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +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.
- 18 Nov 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.
- 16 Nov 26 +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.
- 15 Nov 26 0
- Tool “network_stats” rewrote its description, which is the text the model reads security
- 13 Nov 26 +1
- 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 security
- Schema quality: pass → fail ▼ functional
- New tool “leave_note” functional
- “address_age” reworded the description of “chain” cosmetic
- 12 Nov 26 0
- 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 security
- Stability: unverified → 0.03 ▲ functional
- 11 Nov 26 74
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 21 Nov 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 | 8 Oct 2026 | 6 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | e0c1375d19c47ab0132f84477489ce41 |
| 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. | DS published | 19718 | 13 | Verified |
| rnwy.com. | No DS | 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 ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address (0x...) |
| chain | string | – | base or ethereum (optional, defaults to base) |
No output schema declared.
No examples provided.
commerce_stats ~129
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.
| 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.
leave_note ~189
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.
| Name | Type | Req | Description |
|---|---|---|---|
| about_chain | string | – | Optional: chain slug of an agent the note is about |
| about_id | string | – | Optional: id of that agent |
| body | string | yes | 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 |
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 ~50
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
reviewer_analysis ~58
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.
| 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 ~156
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.
| 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.
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.
remote · rnwy.com
claude mcp add --transport http com-rnwy-rnwy 'https://rnwy.com/api/mcp'
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.