Verified merchants accepting agentic payments on Lightning/L402/BOLT12/USDT — search, verify, pay.
Where agents discover OP-verified merchants on the rails Bitcoin and Tether actually use. 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…
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://mcp.agenticterminal.ai/mcp6 tools · 52mssearch_merchantsSearch OP-verified merchants by rail, chain, category, agent-callable tier, trust tier, and free text. Ranked by trust tier then verification recency.Search OP-verified merchants by rail, chain, category, agent-callable tier, trust tier, and free text. Ranked by trust tier then verification recency.
| Parameter | Type | Description |
|---|---|---|
| query | string | — |
| rail | string | — |
| chain | string | — |
| category | string | — |
| agent_callable_tier | string | — |
| trust_tier_min | number | — |
| accepts_usdc | boolean | — |
| limit | integer | — |
get_merchantGet the full record for one merchant including all rails, payment endpoints, and OP attestation. Tier 2+ requires an AT credential.Get the full record for one merchant including all rails, payment endpoints, and OP attestation. Tier 2+ requires an AT credential.
| Parameter | Type | Description |
|---|---|---|
| id* | string | — |
verify_payment_endpointRun a live check against a merchant's declared payment endpoint for a rail. Returns health, detail, and rail-specific evidence.Run a live check against a merchant's declared payment endpoint for a rail. Returns health, detail, and rail-specific evidence.
| Parameter | Type | Description |
|---|---|---|
| merchant_id* | string | — |
| rail* | string | — |
list_categoriesList the category taxonomy with merchant counts.List the category taxonomy with merchant counts.
No input schema was published for this tool.
list_railsList supported payment rails and their current merchant counts.List supported payment rails and their current merchant counts.
No input schema was published for this tool.
whoamiReport the resolved credential state and rate limits for the calling agent.Report the resolved credential state and rate limits for the calling agent.
No input schema was published for this tool.
6 of 6 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Where agents discover OP-verified merchants on the rails Bitcoin and Tether actually use. 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. MCP server (primary product) — , hosted at .…
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.