Skip to main content
Glama
entroute

EntRoute MCP

Official
by entroute
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
JavaScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
EVM_PRIVATE_KEYNoHex private key for x402 payments
ENTROUTE_API_URLNoEntRoute API base URLhttps://api.entroute.com
MAX_PAYMENT_PER_REQUESTNoSpending cap per request in USD0.05

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
discover_paid_apiA

Discover pay-per-request API endpoints for a given capability.

Returns ranked, verified endpoints with pricing and reliability metrics. Use this to find APIs before calling them. The results include:

  • Endpoint URL and method

  • Price per call and payment network

  • Success rate and latency metrics

  • Provider information

After discovering, you can use call_paid_api to execute the endpoint.

Trust & safety:

  • "Verified" means the endpoint returns a valid x402 402 response -- it does not guarantee the quality or accuracy of the data returned after payment.

  • Endpoints are probed every 10 minutes. Check last_verified and success_rate to gauge reliability.

  • Fallback endpoints (unverified) have failed recent verification checks -- use with caution.

  • Prefer endpoints with success_rate >95% and verification within the last 24 hours.

list_capabilitiesA

List available API capability types.

Use this to explore what kinds of APIs are available in the registry. You can filter by tag (e.g., "weather", "translation") or search by keyword.

Note: A capability existing does not mean verified endpoints are available for it. Use discover_paid_api to check for live endpoints.

call_paid_apiA

Call a previously discovered API endpoint.

Use this after discover_paid_api to execute the request. Payment-required endpoints (402) will return an error with payment details since no wallet is configured.

IMPORTANT: You must first use discover_paid_api to find an endpoint. Then use the endpoint_id from the discovery result.

Trust & safety:

  • No wallet is configured, so paid endpoints will return payment details without executing.

  • EntRoute verifies that endpoints return valid 402 responses every 10 minutes, but does not guarantee response quality or accuracy.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

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.3/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clear and distinct purpose: list_capabilities for discovery, discover_paid_api for endpoint search, and call_paid_api for execution. No overlap exists.

Naming Consistency4/5

Naming follows a consistent verb_noun pattern (list_capabilities, discover_paid_api, call_paid_api). Slight inconsistency: 'discover' and 'list' are different verbs but both are clear.

Tool Count5/5

Three tools cover the entire workflow of discovering and calling paid APIs without unnecessary additions. The count is well-scoped for the domain.

Completeness4/5

Covers the full lifecycle: list capabilities, discover endpoints, and call them. Minor gap: no tool for viewing payment history or managing wallets, but that may be out of scope.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources