Schema | route-verdict-mcp

route-verdict-mcp

Overview Schema Source Related Servers Discussions Admin

Server Configuration

Describes the environment variables required to run the server.

Name	Required	Description	Default
`AGENT_KEY_FILE`	No	Path to a file containing the EVM private key used to sign x402 payment authorizations. Alternative to AGENT_PRIVATE_KEY.
`AGENT_PRIVATE_KEY`	No	EVM private key (0x...) of a wallet holding USDC on Base, used locally to sign the x402 EIP-3009 authorization for paid calls. Alternative to AGENT_KEY_FILE. Without a signer configured the tool never pays.
`ROUTE_VERDICT_URL`	No	Service base URL override (default: production).
`ROUTE_VERDICT_MAX_AMOUNT_UNITS`	No	Spend guard per call in USDC micro-units (default 50000 = $0.05, the known price). The client refuses to sign anything priced above it.	50000

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": false }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`experimental`	{}

Tools

Functions exposed to the LLM to take actions

Name Description

Name	Description
route_checkA	Audit an x402 endpoint's trust and liveness before paying or relying on it. `Calls RouteVerdict (POST /v1/check, $0.05 USDC on Base via x402). Returns a verdict (TRUSTED / CAUTION / AVOID) with a 0-100 trust score, an itemized deduction list, a live 402 probe of the target (the target is never paid), its published terms, discovery-schema quality, catalog presence in the CDP Bazaar and PayAI indexes, and a diff against the last check of the same URL. Args: resource_url: Full URL of the x402 resource to audit.`

route_checkA

Audit an x402 endpoint's trust and liveness before paying or relying on it.

Calls RouteVerdict (POST /v1/check, $0.05 USDC on Base via x402).
Returns a verdict (TRUSTED / CAUTION / AVOID) with a 0-100 trust
score, an itemized deduction list, a live 402 probe of the target
(the target is never paid), its published terms, discovery-schema
quality, catalog presence in the CDP Bazaar and PayAI indexes, and
a diff against the last check of the same URL.

Args:
    resource_url: Full URL of the x402 resource to audit.

Prompts

Interactive templates invoked by user choice

Name	Description
No prompts

Resources

Contextual data attached and managed by the client

Name	Description
No resources

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.5/5.0

Scored 2026-10-25 19:40 across 1 tool

Disambiguation5/5

With a single tool there is no possibility of confusion or misselection. The purpose (audit an x402 endpoint before paying) is clearly articulated and distinct from anything else in the surface.

Naming Consistency5/5

The lone tool, route_check, follows a clean verb_noun (domain_verb) pattern that is readable and predictable. There are no competing conventions to clash with.

Tool Count3/5

One tool is thin for a server, even a narrowly scoped one; it maps to a single paid endpoint, so a minimal surface is defensible, but agents have no complementary operations (e.g. batch check, fetch cached verdict without paying) to work with.

Completeness4/5

The tool returns a rich, self-contained result (verdict, score, deductions, live probe, terms, catalog presence, diff vs. last check), which covers the core audit workflow well. Minor gaps exist: no way to retrieve a prior verdict without a new paid call, and no batch or list operations.

Maintenance

ActivityMaintained

ResponsivenessNo issues