Agentic Terminal Directory MCP Server

Agentic Terminal Directory MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. Verified merchants accepting agentic payments on Lightning/L402/BOLT12/USDT — search, verify, pay.

What you get

AT Directory indexes merchants that sell products, services, APIs, or content and accept Lightning, BOLT12, L402, or USDT (any chain), with trust attestations issued through Observer Protocol. It is the verified, agent-callable layer on top of the fragmented agent-payment landscape. It is not in the payment path — agents discover here and pay merchants directly.

What the assistant can call

Once Agentic Terminal Directory is connected, these are the calls the assistant has available:

• SKILL.md — teaches an agent how to query and complete payment handoff
• Agent — callable tier** (the integration): full-api · structured-handoff · human-checkout

Configuration and credentials

You will need one environment variable: AT_VERIFIER_URL. 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 payments and commerce group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Agentic Terminal Directory's toolset — SKILL.md, Agent — is a fair guide to whether it matches your workflow. It is maintained by ai.agenticterminal; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Agentic Terminal Directory'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 agentic terminal directory mcp server does with a few real requests.