RNWY — AI Agent Trust Intelligence
Server Details
MCP server exposing 8 tools for trust scoring, sybil detection, reviewer wallet analysis, and counterparty risk across 150,000+ AI agents on ERC-8004, Olas, and Virtuals. Streamable HTTP, JSON-RPC 2.0, no API key required.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.3/5 across 10 of 10 tools scored. Lowest: 2.6/5.
Some tools have overlapping purposes (e.g., entity and trust_check both provide agent trust info; risk_terms and mcp_attestation both provide risk scores). Address_age and reviewer_analysis focus on wallet age but in different contexts, which helps. However, tools like entity and reviewer_wallet both provide sybil signals, causing potential confusion.
Tool names use a mix of noun and verb phrases (e.g., address_age, compare_agents, trust_check). Some are descriptive but inconsistent in style (e.g., reviewer_wallet vs. reviewer_analysis). No clear verb_noun pattern, but readable overall.
10 tools is reasonable for a trust intelligence server covering wallet analysis, agent trust, network stats, and risk assessment. Each tool addresses a distinct aspect, though a few could be merged without loss.
Covers core trust and risk dimensions: age, activity, sybil detection, risk scoring, attestations. Missing are tools for updating or submitting data (e.g., no tool to report a reviewer or submit an attestation), which might be needed for full lifecycle. Gaps are notable but not critical for read-heavy use.
Available Tools
10 toolsaddress_ageInspect
Look up wallet age in days for any address. The uncheatable signal; time cannot be faked.
| Name | Required | Description | Default |
|---|---|---|---|
| chain | No | Chain slug (optional, defaults to base) | |
| address | Yes | Wallet address (0x...) |
commerce_statsInspect
Commerce activity for an agent or address; job count, unique counterparties, repeat client rate, total earnings. Covers Olas Mechs and Virtuals ACP protocols.
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Agent ID. Use with chain and registry for linked agent commerce data. | |
| chain | No | Chain slug (required with id) | |
| address | No | Wallet or contract address (0x...). Use this for Virtuals ACP lookups. | |
| registry | No | Registry: erc8004, olas (default erc8004) |
compare_agentsInspect
Side-by-side trust comparison of 2-10 agents, ranked by score with reviewer quality summary for each.
| Name | Required | Description | Default |
|---|---|---|---|
| agents | Yes | Comma-separated chain:id pairs. Example: base:1380,base:16907 | |
| threshold | No | Pass/fail threshold (default 50) |
entityInspect
Full operator footprint for any wallet address — all agents owned, trust scores, sybil signals, wallet intelligence, and MCP servers associated with that operator.
| Name | Required | Description | Default |
|---|---|---|---|
| wallet | Yes | Wallet address (0x...) |
mcp_attestationInspect
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 | Required | Description | Default |
|---|---|---|---|
| canonical_id | Yes | MCP server canonical ID (e.g. vujasinovic/keycloak-source-mcp) |
network_statsInspect
Network-wide statistics; total agents by registry, chain distribution, commerce job counts, and trust score tier distribution across 180,000+ indexed agents.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
reviewer_analysisInspect
Analyze wallet ages of every reviewer who left feedback on an agent. Detects sybil patterns like same-day wallet creation clusters.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Agent ID | |
| chain | Yes | Chain slug |
reviewer_walletInspect
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 | Required | Description | Default |
|---|---|---|---|
| chain | Yes | Chain slug: base, ethereum, bnb, etc. | |
| address | Yes | Wallet address (0x...) | |
| summary | No | If true, omits individual review list (default true) |
risk_termsInspect
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 | Required | Description | Default |
|---|---|---|---|
| chain | Yes | Chain slug: base, ethereum, bnb, gnosis, avalanche, celo, arbitrum, polygon, monad, megaeth, optimism | |
| agent_id | Yes | Agent ID (integer) | |
| registry | No | Registry: erc8004 (default), olas |
trust_checkInspect
Pass/fail trust verdict for any AI agent across ERC-8004, Olas, or Virtuals registries. Returns score, tier, badges, and reasoning.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Agent ID (token ID or Mech ID) | |
| chain | Yes | Chain slug: ethereum, base, bnb, gnosis, avalanche, celo, arbitrum, polygon, monad, megaeth, optimism | |
| registry | No | Registry: erc8004 (default), olas, virtuals | |
| threshold | No | Pass/fail threshold (default 50) |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!