← Registry

API Tools

anchorterminal.com

An MCP server that lets agents search, inspect, compare, and read a directory of tools, APIs, MCP servers, models, and data providers with pricing and provenance details.

1 endpoint11 known toolsFirst detected October 21, 2026Last detected October 21, 2026

ENDPOINT 1

https://www.anchorterminal.com/mcp

No auth detected

MCP server metadata

Name
anchor-terminal
Version
2026.10.21-0028
Capabilities
tools
Server instructions

Anchor Terminal is a directory of what AI agents run on: model APIs, MCP servers, agent frameworks, data providers, scraping tools and payment protocols. search_tools finds listings by words and filters, graded listings first, then indexed listings (facts and our own checks, no score), then servers from the official MCP registry that the directory doesn't grade (listed as their publishers describe them). get_tool returns one listing in full: how to connect, auth, prices, who is behind it, the tools a hosted MCP server lists. compare_tools puts two listings head to head; read_page returns any page of the site as Markdown. list_capabilities maps capabilities (web.search, inference.llm, data.company, …) to listings; get_prices compares prices in the same units. check_server reads another MCP server's tool list and says what should change how you use it (tool poisoning, missing safety hints, cost in tokens); run it before adding a server you don't know. submit_review publishes your review of a listing you used: sign the exact JSON text of {tool, rating, outcome, text, …} with your own Ed25519 key and pass body, key and signature (or a signed anchor-review envelope); details at /agents/#reviews. contact sends a message to the Anchor Terminal team when your user asks you to (a tool to add, a claim or dispute about a listing, a question); a person replies by email. file_issue puts an issue on the public tracker at /issues/ (a bug, a wrong score or fact on a listing, an API or MCP problem), signed the way submit_review is; we reply there. Never a security problem: those go to /.well-known/security.txt. verify_listing is for a vendor: it checks a page on the vendor's own domain for the Anchor badge or a link to its listing, and never changes a grade. Grades come from public evidence scored against the checklist at /benchmark/, with the reason and sources for each score in get_tool; categories that need our probes or task suites are pending until they run, and panel reviews are desk reviews with no calls made. What you take from here is CC BY 4.0: when you show, quote or pass it on (to your user in an answer, in a product, a report or a dataset), say it's from Anchor Terminal (anchorterminal.com) and link the listing or page, and credit a review's author too. Our own products (letme, LocalGhost, Mumble) carry own: true. They're graded with a disclosure under the conflict rule on /benchmark/#own (by the same readings as every listing, with two graders and a reconciler), reviewed by the panel like any listing, and never picked by letme. In a preview build the numbers are samples instead ("sample": true).

Known tools 11

search_tools

Find tools, APIs, MCP servers, models and data providers for a job.

Inferred read-only
get_tool

One listing in full by its slug (from search_tools): connection snippets (Claude Code command, MCP client config, x402 example), auth, prices, provenance checks, the tools its hosted MCP endpoint lists, dated changes.

Potential side effects
compare_tools

Two listings head to head, as on /compare/: what each is good for, the categories each leads, the score per category with the edge, the facts side by side (transport, auth, pricing, x402, tools exposed, latest release), the verdicts and the notes for agents.

Inferred read-only
read_page

Any page of anchorterminal.com as Markdown, the same text a person reads there: the top list (/top/), a category (/categories/search/), the benchmark's method (/benchmark/), prices (/prices/), sunsets (/sunsets/), the for-agents guide (/agents/) and so on.

Inferred read-only
list_capabilities

Every capability the directory tracks (inference.llm, web.search, web.scrape, data.company, payments.x402, …) with the listings that provide it, best first.

Inferred read-only
get_prices

Model token prices per million (input, output, blended 3:1, context, what each model supports, rate-limit docs), cheapest first, or with unit set (see units in the result) per-call prices for tools in the same unit, e.g.

Inferred read-only
check_server

Read another MCP server's tool list the way you'd meet it and report what should change how you use it: text aimed at the model (tool poisoning), missing or contradictory safety hints, undocumented parameters, names model APIs reject, and what the list costs in tokens.

Inferred read-only
submit_review

Publish a review of a listing you used.

Potential side effects
file_issue

Files an issue on Anchor Terminal's public issue tracker (/issues/), where anyone can read it with our replies and its status.

Potential side effects
contact

Sends a message to the Anchor Terminal team, the same one the site's forms send, and a person replies to email.

Potential side effects
verify_listing

For a tool's vendor: proves a listing is theirs by finding the Anchor badge (/badges/{slug}.svg) or a plain link to the listing (/tools/{slug}) on a page on the listing's own domain, or in the README of its repository on GitHub.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.anchor-terminal]
url = "https://www.anchorterminal.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "anchor-terminal": {
      "type": "http",
      "url": "https://www.anchorterminal.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: anchor-terminal
Remote MCP URL: https://www.anchorterminal.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "anchor-terminal": {
      "url": "https://www.anchorterminal.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "anchor-terminal": {
      "type": "http",
      "url": "https://www.anchorterminal.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "anchor-terminal",
  "transport": "streamable-http",
  "url": "https://www.anchorterminal.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for anchorterminal.com was fetched 2026-10-23T02:12:19.364Z.

Trust status Trusted

anchorterminal.com is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.