Skip to content
plugmcp
DirectorySkillsCategoriesBlog
EN/中文
Sign inSign up
Home/Servers/Agentic Terminal Directory

Agentic Terminal Directory

by ai.agenticterminal

Verified merchants accepting agentic payments on Lightning/L402/BOLT12/USDT — search, verify, pay.

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Server URL
https://mcp.agenticterminal.ai/mcp
Provider
Add in Claude

Claude opens with the name and URL filled in. You still confirm it there.

Claude Code
claude mcp add --transport http ai.agenticterminal-directory https://mcp.agenticterminal.ai/mcp

Run in a terminal.

Claude Desktop
{
  "mcpServers": {
    "ai.agenticterminal-directory": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.agenticterminal.ai/mcp"
      ]
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Related MCP

View more
  • Firecrawl🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
  • N
    NotionToken-auth Notion MCP: pages, databases, blocks, comments, files. Runs headless in CI and agents.
  • Context7Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors

Related skills

View all
  • reaReverse engineer anything with agents, from app behavior down to native binaries.
  • rea-changelog-updatePrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.
  • rea-tool-designDesign or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.

Verified merchants accepting agentic payments on Lightning/L402/BOLT12/USDT — search, verify, pay.

Uptime
100%last 1 checks

AT Directory

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) — @agenticterminal/mcp-server, hosted at mcp.agenticterminal.ai.
  • Web directory — agenticterminal.ai, same data rendered for humans.
  • SKILL.md — teaches an agent how to query and complete payment handoff.

Status

Pre-v1, active build. Target: week of 2026-05-18 for a live Tether-meeting demo. v1 ships Tiers 1–2.

Use it from an agent

// Hosted (recommended, no install)
{ "mcpServers": { "at-directory": { "url": "https://mcp.agenticterminal.ai/mcp" } } }

npm install -g @agenticterminal/mcp-server   # local alternative

Six tools: search_merchants, get_merchant, verify_payment_endpoint, list_categories, list_rails, whoami. Reads are ungated — anonymous agents see all tiers and can transact with no setup. An Observer Protocol DirectoryAccessCredential raises rate limits and unlocks write access (reviews), but is not required to discover or transact. Full reference: agenticterminal.ai/api-docs.

Repo layout

data/merchants/         One JSON file per merchant (the source of truth).
data/schema/            JSON Schema (Draft 2020-12) for merchant records.
data/categories.json    Category taxonomy.
data/rails.json         Supported rails + USDT chains.
data/LOGO-AUDIT.md      Logo sourcing checklist.
packages/core/          Types, schema-validated load, search/filter.
packages/mcp-server/    stdio + hosted HTTP MCP server, rail verification.
packages/skill/         SKILL.md (canonical).
apps/web/               Next.js static directory + Netlify Functions.
deploy/mcp-server/      Dockerfile, systemd unit, DEPLOY runbook.
scripts/                Data validation (and one-time crawl tooling).

Development

pnpm install
pnpm -r test          # core + mcp-server unit/integration tests
pnpm -r typecheck
pnpm validate-data    # schema-validate every merchant record
pnpm -F @at-directory/web dev          # web at localhost:3000
pnpm -F @agenticterminal/mcp-server start:stdio   # MCP over stdio

Local MCP with the mock verifier (until the real AT route lands):

pnpm -F @agenticterminal/mcp-server exec tsx src/dev/mock-verifier.ts &
AT_VERIFIER_URL=http://127.0.0.1:8787 \
  pnpm -F @agenticterminal/mcp-server start:stdio

Data model

Every merchant carries two orthogonal signals — read both:

  • OP trust tier (the merchant): 1 self-attested · 2 operator-verified. v1 Tier 2 = AT operator transacted and confirmed; the bilateral counterparty-attestation model lands in v1.x.
  • Agent-callable tier (the integration): full-api · structured-handoff · human-checkout.

The trust tier gates nothing. Reads are ungated, every tier is visible to anonymous agents, and an agent can transact with a Tier 1 merchant with no setup. The tier is evidence for a caller to weigh, not a decision this directory has made on its behalf. Nothing is refused on the basis of it.

Schema is enforced in CI (pnpm validate-data) and on every load. USDT rails require a chain; Tier 2+ non-integrated records require an op_attestation_url; an op_trust_tier of 3 is rejected on ingest, which is why the model above stops at 2.

Contributing

See CONTRIBUTING.md. Merchants and researchers submit by email to [email protected]; accepted entries land at Tier 1 until verified.

The self-registration form at /submit is not operational. apps/web/app/submit/page.tsx has had TALLY_FORM_ID = 'TODO' since 883c183 (2026-06-22, which replaced the earlier GitHub-issue form) and no commit since has changed it, so the page renders an email fallback and embeds no form. apps/web/netlify/functions/submit-merchant.ts exists and is complete, but it needs TURNSTILE_SECRET_KEY, GITHUB_APP_ID, GITHUB_APP_PRIVATE_KEY and GITHUB_INSTALLATION_ID in the Netlify environment and nothing in this repo shows whether they are set. This README and CONTRIBUTING.md advertised the form as the working route anyway until 2026-09-15, when an inbound bounty submission pointed it out. Do not re-advertise it until the form ID is set and a test submission has actually opened a PR.

Documents

  • Scope — positioning, inclusion criteria, definition of done.
  • Spec — implementation contract.

License

MIT.

How do I install Agentic Terminal Directory?
Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does Agentic Terminal Directory need an API key?
No required environment variable is listed on this record.
What transport does Agentic Terminal Directory use?
Agentic Terminal Directory is reached over HTTP.
When was Agentic Terminal Directory last checked?
Last checked 2026-10-13. Verified merchants accepting agentic payments on Lightning/L402/BOLT12/USDT — search, verify, pay.

No tool list yet. Remote servers get one after the first health check.

plugmcp

Plug any tool into any agent. MCP servers for people who do not write servers. Gateway for volume, n8n for apps.

  • github.com/TODO
  • x.com/TODO
  • linkedin.com/company/TODO

PlugMCP, 2026

Product
  • Browse
  • Install
  • Host your own
  • Voice mode
  • Browser
Directory
  • All MCP servers
  • Agent skills
  • Categories
  • New
  • Voice
  • Submit a server
Developers
  • Docs
  • Blog
  • What is MCP
  • What is WebMCP
  • Status
Company
  • About
  • Contact
  • Terms
  • Privacy
  • DPA