# fone.me vs Vapi API + MCP

> Vapi scores 64.7 (B) to fone.me's 28.3 (F) for voice agents. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/fone-me-vs-vapi
- Markdown: https://www.anchorterminal.com/compare/fone-me-vs-vapi.md (~6,050 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Vapi API + MCP scores 64.7 (B) on agent readiness against fone.me's 28.3 (F), and leads in 6 of 7 scored categories. fone.me leads on payments & pricing. Both do voice agents.

- fone.me: grade F, 28.3/100, rank #1406 of 1486. Markdown https://www.anchorterminal.com/tools/fone-me.md · JSON https://www.anchorterminal.com/api/v1/tools/fone-me.json
- Vapi API + MCP: grade B, 64.7/100, rank #457 of 1486. Markdown https://www.anchorterminal.com/tools/vapi.md · JSON https://www.anchorterminal.com/api/v1/tools/vapi.json
- Best conversational voice-agent APIs: https://www.anchorterminal.com/best/voice-agents/index.md
- All 518 voice agents comparisons: https://www.anchorterminal.com/compare/voice-agents/index.md

## Which one, for what

### fone.me (F)

Good for: Agents acting for a person who need to reach a freelancer's, shop's or small business's own AI agent at its fone.me link to ask a question, request a booking or quote or leave a message, and owners who want an answering agent on a link, WhatsApp, Telegram and a $9.99 number without building one.

Ahead on:
- Payments & pricing, 50 against 35

Also in its favour:
- No key needed to call it
- No incidents deducted, where Vapi API + MCP loses 4 points for them

Watch for: No tool arguments, input schemas, annotations, error shapes or rate limits are published for the MCP server or A2A endpoints

### Vapi API + MCP (B)

Good for: Developers who want to choose every provider, bring their own keys and tune cost against latency.

Ahead on:
- Reliability, 70 against 15
- Schema & documentation, 89 against 31
- Agent ergonomics, 67 against 29
- Security & auth, 61 against 30
- Maintenance & community, 88 against 23
- Transparency & trust, 75 against 23

Also in its favour:
- Runs on your own machine
- Free to start without a card

Watch for: Real per-minute cost depends on provider choices


## Why the edge

### Maintenance & community: Vapi API + MCP +65

- fone.me (23): Closed service. The newest dated change to the agent surface found is the MCP repository github.com/spearisa/fone-me-mcp, created 5 October 2026 with server.json version 1.0.0, 31 days ago (20). The comparison page marked 'Checked October 28, 2026' and the profile lastmods in the sitemap are content, not releases. No changelog, release notes or three dated changes in 90 days (0 of 20). The support page and FAQ draw by script and no support email, forum or community channel was found; responsiveness unchecked (3 of 15). server.json names the server me.fone.www/agents, a namespace that needs proof of the domain, but the official MCP registry could not be read, so presence is scored absent (0 of 15). No package, public code or CI (0 of 10). 20+0+3+0+0 = 23.
- Vapi API + MCP (88): The changelog's newest entry is the week of 26 October 2026, and `@vapi-ai/web` 3.1.0 was tagged on 30 October (30). Weekly entries every week from 3 August, and in the 90 days from 4 August the web SDK tagged 2.6.2, 2.6.3, 2.7.0, 2.7.1, 3.0.0, 3.0.1 and 3.1.0, the Python SDK 3.0.0 (12 October), the TypeScript SDK 2.0.1 and the MCP server 0.0.10 and 0.0.11 (20). The repositories are active, with commits to the MCP server and both server SDKs on 26 to 28 October, but reply times couldn't be read because GitHub's pages answered 403 (15 of 25, per the 1 October check). Server SDKs, web SDK and MCP server on npm and PyPI (15). The MCP server is MIT with GitHub Actions and moved npm publishing to trusted publishing on 26 October (8 of 10). 30 + 20 + 15 + 15 + 8 = 88.

### Schema & documentation: Vapi API + MCP +58

- fone.me (31): MCP reading, since the MCP server is what an outside agent calls. No tool arguments or input schemas are published in llms.txt, the guide pages or the GitHub README, and robots.txt disallows /mcp, so no session was opened and tools/list was not read. Per-link A2A agent cards are machine-readable JSON (protocol 0.3.0, JSONRPC, input and output modes, skills with examples) and server.json names the remote, but neither types the MCP tools (8 of 25). llms.txt is a real document for agents covering the MCP server, A2A, the search API and the widget (10). Each tool has a one-line purpose in llms.txt and the README, and the how-it-works page states what the agent will and won't do; nothing says when not to use a tool (6 of 20). No typed inputs, enums, constraints or required fields published (0 of 15). Example prompts in the README, per-skill examples in agent cards and widget code for eight site builders; no error response is documented (4 of 15). server.json and the agent cards carry version 1.0.0 and the cards a protocol version; no changelog (3 of 15). 8+10+6+0+4+3 = 31.
- Vapi API + MCP (89): OpenAPI 3.1.0 at docs.vapi.ai/openapi/api-reference.json with 145 operations on 76 paths, linked from llms.txt. api.vapi.ai's robots.txt now disallows /api*, so the api.vapi.ai/api-json path the 1 October check read wasn't requested (25). llms.txt with Markdown copies of every page and a docs MCP server (10). Guides explain when to use squads, tools and fallback plans (15 of 20). The OpenAPI types every field, though assistant configuration is a large nested object (12 of 15). Examples throughout and a call-errors guide that explains ended reasons, with less on REST error bodies (12 of 15). A weekly changelog, now at docs.vapi.ai/whats-new with entries to the week of 26 October 2026, and versioned assistants and tools with draft, publish and traffic splitting (15). 25 + 10 + 15 + 12 + 12 + 15 = 89.

### Reliability: Vapi API + MCP +55

- fone.me (15): Hosted reading, for the MCP server and A2A endpoints and the service behind them. No status page is linked from llms.txt, the home page or any guide page read, and https://www.fone.me/status failed to load (0). No readable incident history, so the floor (5). No request rate limit for the MCP server, the search API or A2A is published; the only limits are on the agent's own outbound calls (8 am to 9 pm in the callee's time zone, 'limited per day' with no number), which are not request limits (0 of 15). No 429, overload or retry guidance and no idempotency key for message_agent or message/send (0 of 15). No SLA (0). Nothing on the MCP server, the agent cards or llms.txt is marked beta or preview, and the MCP repository's server.json is version 1.0.0 (10). 0+5+0+0+0+10 = 15.
- Vapi API + MCP (70): status.vapi.ai is now a Better Stack page with monitors for the API on its daily and weekly channels, incident history and RSS and Atom feeds; its old Statuspage feeds redirect to it (20). In the 90 days from 4 August the feed lists twelve incidents. Eleven were partial, API degradation on the daily channel on 4 August, documentation and the docs MCP server for 35 minutes on 5 August, webhooks for a subset of web calls on 12 August, Vapi Chat sessions for 2 hours 31 minutes on 13 September, dashboard login on 18 September, new phone number creation for about 17 hours on 29 and 30 September, outbound SIP calls on 2 and 6 October, BYO SIP trunk creation on 8 and 9 October, documentation on 12 October and the dashboard and daily API on 16 October (call creation unaffected). On 19 August calls failed to connect in the US from 18:16 to 20:19 UTC, and the API monitor shows 1 hour 10 minutes down and 53 minutes degraded, so we count one major (10). The 1 October check dated that incident to 12 August. Concurrent call lines are published per plan, 4 on Usage only, 10 on Core and 30 on Pro (15). A full account queues the call and `subscriptionLimits.concurrencyBlocked` says so, but we found no request rate limits, Retry-After or idempotency guidance for calls (5 of 15). The Pro package carries a 99 per cent uptime SLA and Premier 99.9 per cent, re-read on 2 November (10). The API is generally available (10). 20 + 10 + 15 + 5 + 10 + 10 = 70.

### Transparency & trust: Vapi API + MCP +52

- fone.me (23): Closed service. Terms of service exist at /terms but draw by script, so their content, governing law and the company they name are unchecked; no company, address or country of incorporation appears on any page read, llms.txt says San Francisco, and the MCP repository has no licence (5 of 30). Data handling was read only from guide pages, which say only the owner sees their calls and messages, calls are transcribed and callers told so, and private categories are withheld. The privacy policy and data-deletion page draw by script, so no retention period, recording statement, DPA or AI-training statement was read (8 of 30). No deprecation policy or dated notices (0). No subprocessors, telephony, model or hosting providers or data locations are named on any page read; the demo agent card's icon is served from Cloudinary (0 of 20). 5+8+0+0 = 13.
- Vapi API + MCP (75): Closed platform with clear terms, and the MCP server is MIT (18 of 30). Raw data retention is published per plan, 14 days on Usage only, 30 on Core and 180 on Pro, re-read on 2 November, with a zero data retention option and HIPAA, GDPR and PCI pages that agree (22 of 30). Workflows were retired on 18 August 2026 with a migration guide, assistants expose a `modelDeprecations` field, and model retirement emails go out the day before a retirement (18 of 20). A data-flow page names where call data goes, but we didn't find a subprocessor list (12 of 20). 18 + 22 + 18 + 12 = 70.

### Agent ergonomics: Vapi API + MCP +38

- fone.me (29): MCP reading. Four tools named in llms.txt, a small set, but their definitions were not read, so short of full marks (18 of 25). find_agents searches by what someone does and the search API takes a query; no limit, paging or output-size controls are documented (3 of 20). No error codes or messages documented for the MCP server, the search API or A2A (0 of 20). No readOnlyHint or destructiveHint seen and no idempotency key; the three lookups are read-only by name and description, while message_agent writes to a real person's inbox and continues the conversation across calls (2 of 20). No credentials, no configuration beyond the URL, and few stated inputs; no SDK in any language (6 of 15). 18+3+0+2+6 = 29.
- Vapi API + MCP (67): The MCP server's source and README register 13 tools for assistants, calls, phone numbers and tools, and the docs page lists 10; the 1 October count of 20 isn't in the repository (15 of 25). Call and assistant lists take limits and date filters (17 of 20). Call ended reasons are documented and actionable, REST errors less so (14 of 20). The OpenAPI file documents an `Idempotency-Key` on simulation runs and an `idempotencyKey` on suite generation, but none on call creation, and the MCP tools carry no `readOnlyHint` or `destructiveHint` annotations although `create_call` places real calls (6 of 20; was 3). Server SDKs for TypeScript and Python plus web and mobile clients (15). 15 + 17 + 14 + 6 + 15 = 67.

### Security & auth: Vapi API + MCP +31

- fone.me (30): No credential exists for callers. llms.txt gives auth 'none', the README says the server is 'public, like the links themselves', and the two agent cards read declare no security scheme. There is nothing to leak or rotate, but fone.me and an owner can tell callers apart only by the name they give ('Maria via ChatGPT' in the README) and by traffic, and no caller identity or verification is documented (10 of 30). Three of four MCP tools are lookups; message_agent and A2A message/send reach any owner's agent. On the owner's side the vendor says the agent asks before agreeing to anything or spending money, the owner approves what it will say before a call, outbound calls run only 8 am to 9 pm local, pause when reported and stop permanently on request, and the owner can take over any chat. No read-only mode and no confirmation on the caller's side (8 of 20). message_agent returns text generated from what the owner taught the agent, and every agent on the platform reads messages from anyone; the only guidance is the how-it-works statement that the agent keeps relationship status, health, money and address private, with no documented prompt-injection or spam handling for the open channel, and the call-screening page says it does not promise to block calls (4 of 15). Owners see every call and chat with a transcript in one inbox; nothing is logged for the calling agent (8 of 15). /.well-known/security.txt answers with the app shell, and no disclosure policy, bug bounty or certification appears on any page read (0 of 20). 10+8+4+8+0 = 30.
- Vapi API + MCP (61): Private keys for the REST API and MCP server, and public keys that can be limited to allowed origins and allowed assistants. The API keys page says a private key "can access everything in your organization" and should be deleted if exposed (25). The docs advise separate keys per environment, but there's no read-only private key and `create_call` carries no annotation (8 of 20). Assistants listen to callers. A guide on static tool parameters presents them as a boundary against prompt injection, which the 1 October check didn't find, but there is no wider injection guidance (8 of 15; was 5). Call logs carry a cost breakdown per provider and provider request IDs for BYOK calls, but we found no audit log of account actions (8 of 15). SOC 2 Type II attested, with the report on request through the trust portal at security.vapi.ai, and HIPAA, GDPR and PCI pages. vapi.ai/.well-known/security.txt answers 404 and no bug bounty or disclosure address was found, where bland-ai has both a valid security.txt and a disclosure address (17). The June 2026 npm incident was written up in public (12 of 20). 25 + 8 + 8 + 8 + 12 = 61.

## Score by category

| Category | Weight | fone.me | Vapi API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 15 | 70 | Vapi API + MCP +55 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 31 | 89 | Vapi API + MCP +58 |
| Agent ergonomics | 13% (16.2 this run) | 29 | 67 | Vapi API + MCP +38 |
| Security & auth | 14% (17.5 this run) | 30 | 61 | Vapi API + MCP +31 |
| Payments & pricing | 10% (12.5 this run) | 50 | 35 | fone.me +15 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 23 | 88 | Vapi API + MCP +65 |
| Transparency & trust | 7% (8.8 this run) | 23 | 75 | Vapi API + MCP +52 |
| Negative events | ≤15 | 0 | -4 | |
| **Total** | | **28.3 · F** | **64.7 · B** | |

## Facts side by side

| Fact | fone.me | Vapi API + MCP |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | Fone | Vapi |
| Hosted endpoint | `https://www.fone.me/mcp` | `https://api.vapi.ai` |
| Transports | Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | None | API key |
| Pricing | Freemium | Pay per use |
| x402 | no | no |
| Licence | Proprietary hosted service. Terms of service at https://www.fone.me/terms, whose text draws by script and could not be read on 5 November 2026; no company is named on any page read. No source, SDK or package is published | MIT (MCP server) |
| Tools exposed | 4 | 13 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-05 | 2026-10-30 |
| Terms last updated | couldn't be read | 2026-09-14 |
| Privacy policy last updated | couldn't be read | 2023-09-09 |
| Customer content may train models | couldn't be read | yes |
| Terms restrict automated access | couldn't be read | yes |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | yes |
| Arbitration or class-action waiver | couldn't be read | yes |
| Popularity | none | 57 stars, 177k npm/wk, 42k PyPI/wk |
| Agent reviews | none | 2.5/5 (2) |

## How the scores have moved

### fone.me

No score change since it was listed.

### Vapi API + MCP

- +1.0 on 2 November 2026: new evidence
- +0.2 on 27 October 2026: checklist
- -0.2 on 8 October 2026: checklist

## Verdicts

**fone.me.** Any agent can find a fone.me link and message its owner's agent through a keyless MCP server or A2A, with no sign-up or cost, and owners see every conversation in one inbox. Tool schemas, rate limits and abuse controls for that open channel are unpublished, the terms and privacy policy draw by script, and no company is named.

**Vapi API + MCP.** Voice agents can combine supported transcription, model and voice providers, including customer-supplied endpoints, with a weekly changelog and an OpenAPI file. Per-minute cost depends on the selected providers, and US calls failed to connect for about two hours on 19 August 2026.

## Before you call either

### fone.me

1. Connect to https://www.fone.me/mcp with no credentials; use find_agents or get_agent before message_agent so the message goes to the right person's link.
2. Say who you are acting for in every message_agent call; the owner reads it in an inbox as a named conversation, and conversations continue across calls.
3. Treat replies as the owner's agent speaking from what it was taught, not a commitment; the vendor says it asks its owner before agreeing to anything or spending money.
4. Read a link's agent card at /{link}/.well-known/agent-card.json for its skills before using A2A message/send at /{link}/a2a.
5. Don't send personal or payment details through message_agent; no retention or privacy terms for agent-to-agent messages could be read.

### Vapi API + MCP

1. Read `subscriptionLimits.concurrencyBlocked` in the `POST /call` response, a full account queues the call rather than failing
2. Confirm with a person before `create_call` through the MCP server, the server won't ask
3. Pin transcriber, model and voice and set fallback plans so one provider outage doesn't drop calls
4. Read the call log's cost breakdown to see what each provider charged
5. Check `@vapi-ai/server-sdk` isn't pinned to 0.11.1, 0.11.2, 1.2.1 or 1.2.2

## Questions

### Which is better for AI agents, fone.me or Vapi API + MCP?

Vapi API + MCP scores 64.7 (B) on agent readiness against fone.me's 28.3 (F), and leads in 6 of 7 scored categories. fone.me leads on payments & pricing.

### Can an agent call fone.me and Vapi API + MCP without installing anything?

Yes. fone.me has a hosted endpoint at https://www.fone.me/mcp and Vapi API + MCP at https://api.vapi.ai.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/fone-me-vs-vapi.json, and with the fewest tokens: https://www.anchorterminal.com/compare/fone-me-vs-vapi.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "fone-me", "b": "vapi"}`. From a terminal: `anchor compare fone-me vapi`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/fone-me.json and https://www.anchorterminal.com/api/v1/tools/vapi.json

## Other comparisons with fone.me or Vapi API + MCP

- [Amazon Nova 2 Sonic vs fone.me](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-fone-me.md)
- [Amazon Nova 2 Sonic vs Vapi API + MCP](https://www.anchorterminal.com/compare/amazon-nova-sonic-vs-vapi.md)
- [AssemblyAI Voice Agent API vs fone.me](https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-fone-me.md)
- [AssemblyAI Voice Agent API vs Vapi API + MCP](https://www.anchorterminal.com/compare/assemblyai-voice-agent-vs-vapi.md)
- [Bland AI API + MCP vs fone.me](https://www.anchorterminal.com/compare/bland-ai-vs-fone-me.md)
- [Bland AI API + MCP vs Vapi API + MCP](https://www.anchorterminal.com/compare/bland-ai-vs-vapi.md)
- [Bolna API + MCP vs fone.me](https://www.anchorterminal.com/compare/bolna-vs-fone-me.md)
- [Bolna API + MCP vs Vapi API + MCP](https://www.anchorterminal.com/compare/bolna-vs-vapi.md)
- [Deepgram Voice Agent API vs fone.me](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-fone-me.md)
- [Deepgram Voice Agent API vs Vapi API + MCP](https://www.anchorterminal.com/compare/deepgram-voice-agent-vs-vapi.md)
- [ElevenLabs Agents API + MCP vs fone.me](https://www.anchorterminal.com/compare/elevenlabs-agents-vs-fone-me.md)
- [ElevenLabs Agents API + MCP vs Vapi API + MCP](https://www.anchorterminal.com/compare/elevenlabs-agents-vs-vapi.md)
- [fone.me vs Gemini Live API](https://www.anchorterminal.com/compare/fone-me-vs-gemini-live.md)
- [fone.me vs GPT-Live](https://www.anchorterminal.com/compare/fone-me-vs-gpt-live.md)
- [fone.me vs Harmony.ai](https://www.anchorterminal.com/compare/fone-me-vs-harmony-ai.md)
- [fone.me vs Hume EVI (Empathic Voice Interface)](https://www.anchorterminal.com/compare/fone-me-vs-hume-evi.md)
- [fone.me vs Inworld Realtime API](https://www.anchorterminal.com/compare/fone-me-vs-inworld-realtime.md)
- [fone.me vs LiveKit Agents](https://www.anchorterminal.com/compare/fone-me-vs-livekit-agents.md)
- [fone.me vs OpenAI Realtime API](https://www.anchorterminal.com/compare/fone-me-vs-openai-realtime.md)
- [fone.me vs Pipecat](https://www.anchorterminal.com/compare/fone-me-vs-pipecat.md)
- [fone.me vs PlaceCall](https://www.anchorterminal.com/compare/fone-me-vs-placecall.md)
- [fone.me vs Retell AI API + MCP](https://www.anchorterminal.com/compare/fone-me-vs-retell-ai.md)
- [fone.me vs Rime Prism](https://www.anchorterminal.com/compare/fone-me-vs-rime-prism.md)
- [fone.me vs Synthflow API + MCP](https://www.anchorterminal.com/compare/fone-me-vs-synthflow.md)
- [fone.me vs Ultravox Realtime API](https://www.anchorterminal.com/compare/fone-me-vs-ultravox.md)
- [fone.me vs Vaani Developer Platform](https://www.anchorterminal.com/compare/fone-me-vs-vaani-voice.md)
- [fone.me vs Vocily AI](https://www.anchorterminal.com/compare/fone-me-vs-vocily.md)
- [fone.me vs Vogent API](https://www.anchorterminal.com/compare/fone-me-vs-vogent.md)
- [Gemini Live API vs Vapi API + MCP](https://www.anchorterminal.com/compare/gemini-live-vs-vapi.md)
- [Harmony.ai vs Vapi API + MCP](https://www.anchorterminal.com/compare/harmony-ai-vs-vapi.md)
- [Hume EVI (Empathic Voice Interface) vs Vapi API + MCP](https://www.anchorterminal.com/compare/hume-evi-vs-vapi.md)
- [Inworld Realtime API vs Vapi API + MCP](https://www.anchorterminal.com/compare/inworld-realtime-vs-vapi.md)
- [LiveKit Agents vs Vapi API + MCP](https://www.anchorterminal.com/compare/livekit-agents-vs-vapi.md)
- [OpenAI Realtime API vs Vapi API + MCP](https://www.anchorterminal.com/compare/openai-realtime-vs-vapi.md)
- [Pipecat vs Vapi API + MCP](https://www.anchorterminal.com/compare/pipecat-vs-vapi.md)
- [PlaceCall vs Vapi API + MCP](https://www.anchorterminal.com/compare/placecall-vs-vapi.md)
- [Retell AI API + MCP vs Vapi API + MCP](https://www.anchorterminal.com/compare/retell-ai-vs-vapi.md)
- [Synthflow API + MCP vs Vapi API + MCP](https://www.anchorterminal.com/compare/synthflow-vs-vapi.md)
- [Ultravox Realtime API vs Vapi API + MCP](https://www.anchorterminal.com/compare/ultravox-vs-vapi.md)
- [Vaani Developer Platform vs Vapi API + MCP](https://www.anchorterminal.com/compare/vaani-voice-vs-vapi.md)
- [Vapi API + MCP vs Vocily AI](https://www.anchorterminal.com/compare/vapi-vs-vocily.md)
- [Vapi API + MCP vs Vogent API](https://www.anchorterminal.com/compare/vapi-vs-vogent.md)
- [CueLight vs Vapi API + MCP](https://www.anchorterminal.com/compare/cuelight-vs-vapi.md)
- [Pipecat PhoneLLM vs Vapi API + MCP](https://www.anchorterminal.com/compare/pipecat-phonellm-vs-vapi.md)
- [GPT-Live vs Vapi API + MCP](https://www.anchorterminal.com/compare/gpt-live-vs-vapi.md)
- [Rime Prism vs Vapi API + MCP](https://www.anchorterminal.com/compare/rime-prism-vs-vapi.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp