Agent MCP Server

Agent MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. Discover and call x402 paid services — search by intent, filter by price/chain.

What you get

search accepts natural-language intent and ranks by FTS5 + popularity + health. Each result carries a match_reason and a confidence score. ask_services uses the same retrieval-first / LLM-rerank flow as /api/v1/ask.

Configuration and credentials

You will need 8 environment variables: UPSTREAM_BASE_URL, UPSTREAM_API_KEY, AGENT_TOOLS_ASK_BASE_URL, AGENT_TOOLS_ASK_API_KEY, AGENT_TOOLS_SAFETY_BASE_URL, AGENT_TOOLS_SAFETY_API_KEY, AGENT_TOOLS_DB_PATH, METRICS_BEARER_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by AgentTools-Cloud; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Agent's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the agent mcp server does with a few real requests.