Skip to main content
mcpSource-backedReview first Safety Privacy

Agentic Terminal Directory MCP Server for Claude

AT Directory hosted MCP server for discovering Observer Protocol–verified merchants accepting Lightning, BOLT12, L402, and USDT agentic payments with live rail verification.

HarnessClaude CodeCursorClaude Desktop
Review first review before installing

Open the source and read safety notes before installing.

Safety notes

  • The directory indexes merchant claims and attestations; verify rails before sending funds.
  • `verify_payment_endpoint` probes live endpoints but agents still pay merchants directly.
  • Tier 1 merchants are self-attested; prefer Tier 2+ records for high-value purchases.
  • Never share private keys or wallet seeds through MCP chat sessions.

Privacy notes

  • Search queries and merchant IDs may appear in Agentic Terminal logs.
  • Payment transactions occur directly with merchants, not through the directory.
  • Optional credentials link your agent identity for rate-limit and review features.

Prerequisites

  • MCP client with streamable HTTP connector support.
  • Understanding that the directory is discovery-only—not in the payment path.
  • Optional Observer Protocol DirectoryAccessCredential for higher rate limits and write access.
  • Wallet or payment rail tooling separate from the directory for actual checkout.

Schema details

Install type
cli
Reading time
4 min
Difficulty score
35
Troubleshooting
Yes
Breaking changes
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
5 minutes
Difficulty
intermediate
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "at-directory": {
      "url": "https://mcp.agenticterminal.ai/mcp",
      "type": "http"
    }
  }
}

About this resource

Overview

The Agentic Terminal Directory (AT Directory) is a verified merchant index for agentic commerce on the payment rails Bitcoin and Tether actually use—Lightning, BOLT12, L402, and USDT across supported chains. Agents discover merchants, inspect trust tiers from Observer Protocol, and verify payment endpoints before transacting. The directory is never in the payment path.

Hosted MCP is at https://mcp.agenticterminal.ai/mcp. Source data and server code live in observer-protocol/at-directory.

Features

  • Six tools: search_merchants, get_merchant, verify_payment_endpoint, list_categories, list_rails, whoami.
  • Anonymous read access for discovery and rail verification.
  • Observer Protocol trust tiers separate from agent-callable integration tiers.
  • Hosted streamable HTTP plus optional local @agenticterminal/mcp-server stdio package.
  • Web directory at agenticterminal.ai with matching data.

Use Cases

  • Search gift-card merchants accepting Lightning in a target category.
  • Inspect Bitrefill's attestation and agent endpoints before purchase.
  • Verify a merchant's Lightning endpoint is live before sending sats.
  • List supported USDT chains and filter merchants by rail.
  • Check your agent identity with whoami when using directory credentials.

Installation

Claude (Connectors)

  1. Add https://mcp.agenticterminal.ai/mcp as a custom connector—no install required.
  2. Optionally install @agenticterminal/mcp-server globally for local stdio use.
  3. Run search_merchants with rail and category filters.
  4. Call verify_payment_endpoint before initiating payment with your wallet.

Claude Code

claude mcp add --transport http at-directory https://mcp.agenticterminal.ai/mcp
claude mcp list

Other MCP clients

Add the connector using the JSON configuration below in your MCP client settings.

Configuration

{
  "mcpServers": {
    "at-directory": {
      "url": "https://mcp.agenticterminal.ai/mcp",
      "type": "http"
    }
  }
}

For authenticated setups:

{
  "mcpServers": {
    "at-directory": {
      "url": "https://mcp.agenticterminal.ai/mcp",
      "type": "http",
      "headers": {
        "Authorization": "Bearer YOUR_DIRECTORY_ACCESS_CREDENTIAL"
      }
    }
  }
}

Optional DirectoryAccessCredential raises rate limits and unlocks review writes; discovery reads need no auth.

Examples

Merchant search

Search for merchants accepting Lightning in the gift-cards category.

Rail verification

Verify the Lightning payment endpoint for merchant bitrefill before checkout.

Merchant detail

Get full rails, agent endpoints, and attestation URL for merchant bitrefill.

Security

  • Read OP trust tier and agent-callable tier before trusting a merchant.
  • Use live verification results; do not skip verify_payment_endpoint for large payments.
  • Agents bring their own wallet—never paste seeds or macaroons into chat.

Troubleshooting

Rate limited

Obtain a DirectoryAccessCredential or reduce query frequency.

Verification inconclusive

Some rails are attestation-only; read the tool response carefully.

Empty search

Broaden category or rail filters; confirm merchant data passed CI validation.

Local stdio errors

For dev, start the mock verifier per the repository README before stdio mode.

Duplicate Check

No existing Agentic Terminal Directory or agenticterminal.ai entry was found in content/mcp/. This differs from generic payment MCP servers because it is a read-only verified merchant directory, not a wallet or checkout processor.

Source citations

Add this badge to your README

Show that Agentic Terminal Directory MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/agentic-terminal-directory-mcp-server.svg)](https://heyclau.de/entry/mcp/agentic-terminal-directory-mcp-server)

How it compares

Agentic Terminal Directory MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

FieldAgentic Terminal Directory MCP Server for Claude

AT Directory hosted MCP server for discovering Observer Protocol–verified merchants accepting Lightning, BOLT12, L402, and USDT agentic payments with live rail verification.

Open dossier
AdAdvisor MCP Server for Claude

Hosted AdAdvisor MCP server with curated Meta Ads workflows for browsing creatives, launching campaigns, building audiences, and optimizing performance from Claude via streamable HTTP.

Open dossier
Alpic MCP Server for Claude

Alpic hosted MCP server to manage cloud-hosted MCP projects—deployments, debugging, and analytics—for apps built and shipped on the Alpic platform.

Open dossier
AppDeploy MCP Server for Claude

AppDeploy hosted MCP server for chat-native full-stack web app deployment with templates, QA snapshots, version rollback, and live public URLs from Claude or ChatGPT.

Open dossier
Trust
Install riskReview firstReview firstReview firstReview first
Notes Safety Privacy Safety Privacy Safety Privacy Safety Privacy
Categorymcpmcpmcpmcp
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorObserver ProtocolAdAdvisorAlpicAppDeploy
Added2026-06-142026-06-142026-06-142026-06-14
Platforms
Claude CodeCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo
Safety notesThe directory indexes merchant claims and attestations; verify rails before sending funds. `verify_payment_endpoint` probes live endpoints but agents still pay merchants directly. Tier 1 merchants are self-attested; prefer Tier 2+ records for high-value purchases. Never share private keys or wallet seeds through MCP chat sessions.Workflow tools can create or modify Meta Ads campaigns, ad sets, creatives, and audiences when your token has write scope. Bearer tokens grant persistent account access until revoked in AdAdvisor or Meta Business settings. Treat returned spend, conversion, and audience data as business-sensitive before sharing in chat exports. Verify AI-proposed budget or targeting changes before approving tool calls on live ad accounts.Management tools may trigger redeployments or configuration changes on hosted MCP servers. Analytics and logs may contain end-user queries from your deployed MCP apps. Do not share Alpic credentials across untrusted chat sessions. Verify target project/environment before approving destructive deploy actions.deploy_app publishes publicly reachable URLs; review app content before deploying. delete_app permanently removes apps—use only on explicit user request. Deployed apps may access AppDeploy-provided database, storage, and auth services. OAuth sessions grant persistent deploy access until disconnected.
Privacy notesSearch queries and merchant IDs may appear in Agentic Terminal logs. Payment transactions occur directly with merchants, not through the directory. Optional credentials link your agent identity for rate-limit and review features.Account IDs, campaign names, creative assets, and performance metrics are sent to AdAdvisor and Meta APIs. Store adv_sk_ API keys in connector headers or secrets managers, not in chat logs or source control. AdAdvisor may retain usage telemetry under its platform terms; review privacy policy before connecting production accounts.Project metadata, deployment logs, and analytics are processed by Alpic. End-user traffic to your deployed MCP apps is subject to Alpic platform terms. Store Alpic auth tokens in connector secrets, not in repositories.App source, deployment logs, and QA snapshots are stored on AppDeploy infrastructure. Public URLs may expose app functionality and any data users submit to the deployed app. Guest OAuth still ties deployments to an AppDeploy identity—avoid sharing accounts.
Prerequisites
  • MCP client with streamable HTTP connector support.
  • Understanding that the directory is discovery-only—not in the payment path.
  • Optional Observer Protocol DirectoryAccessCredential for higher rate limits and write access.
  • Wallet or payment rail tooling separate from the directory for actual checkout.
  • AdAdvisor account with Meta Ads connected and an API key (adv_sk_...) for MCP authentication.
  • Claude Pro, Team, or Enterprise with Connectors support, or another MCP client with streamable HTTP connectors.
  • Meta Ads account permissions sufficient for the campaigns and assets you plan to query or modify.
  • Review of AdAdvisor pricing and plan limits before enabling write workflows in production accounts.
  • Alpic account with at least one MCP project deployed on Alpic cloud.
  • Claude or another MCP client with streamable HTTP connector support.
  • Authentication to Alpic (API key or OAuth depending on connector setup).
  • Understanding that this server manages Alpic-hosted projects, not arbitrary third-party MCP URLs.
  • AppDeploy account via OAuth (Google, Apple, X, or Guest).
  • Claude Pro/Team with Connectors, ChatGPT, Cursor, Codex, or Grok MCP support.
  • Clear description of the app you want deployed before invoking write tools.
  • Awareness that deploy_app and delete_app are destructive operations.
Install
claude mcp add --transport http at-directory https://mcp.agenticterminal.ai/mcp
claude mcp add --transport http adadvisor https://api.adadvisor.ai/mcp
claude mcp add --transport http alpic https://mcp.alpic.ai
claude mcp add --transport http appdeploy https://api-v2.appdeploy.ai/mcp
Config
{
  "mcpServers": {
    "at-directory": {
      "url": "https://mcp.agenticterminal.ai/mcp",
      "type": "http",
      "headers": {
        "Authorization": "Bearer YOUR_DIRECTORY_ACCESS_CREDENTIAL"
      }
    }
  }
}
{
  "mcpServers": {
    "adadvisor": {
      "url": "https://api.adadvisor.ai/mcp",
      "type": "http",
      "headers": {
        "Authorization": "Bearer adv_sk_YOUR_KEY"
      }
    }
  }
}
{
  "mcpServers": {
    "alpic": {
      "url": "https://mcp.alpic.ai",
      "type": "http",
      "headers": {
        "Authorization": "Bearer YOUR_ALPIC_TOKEN"
      }
    }
  }
}
{
  "mcpServers": {
    "appdeploy": {
      "url": "https://api-v2.appdeploy.ai/mcp",
      "type": "http"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.