# Hugging Face Inference Providers vs LiteLLM

> LiteLLM scores 62.4 (B) to Hugging Face Inference Providers's 54 (C) for model routing. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-litellm
- Markdown: https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-litellm.md (~6,300 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

LiteLLM scores 62.4 (B) on agent readiness against Hugging Face Inference Providers's 54 (C), and leads in 5 of 7 scored categories. Hugging Face Inference Providers leads on security & auth and transparency & trust. Both do model routing.

- Hugging Face Inference Providers: grade C, 54/100, rank #926 of 1510. Markdown https://www.anchorterminal.com/tools/hugging-face-inference-providers.md · JSON https://www.anchorterminal.com/api/v1/tools/hugging-face-inference-providers.json
- LiteLLM: grade B, 62.4/100, rank #559 of 1510. Markdown https://www.anchorterminal.com/tools/litellm.md · JSON https://www.anchorterminal.com/api/v1/tools/litellm.json
- Best model APIs and inference for AI agents: https://www.anchorterminal.com/best/inference/index.md
- All 830 models comparisons: https://www.anchorterminal.com/compare/inference/index.md

## Which one, for what

### Hugging Face Inference Providers (C)

Good for: Agents and developers who want open-weight models from several hosts on one token and one bill, with a public price and capability list per provider.

Ahead on:
- Security & auth, 79 against 72
- Transparency & trust, 71 against 63

Also in its favour:
- A hosted endpoint, with nothing to install
- No incidents deducted, where LiteLLM loses 12 points for them

Watch for: No rate limits, 429 behaviour or error responses documented for the router

### LiteLLM (B)

Good for: Teams that want one OpenAI-compatible endpoint over many providers on their own infrastructure, with per-key budgets, model allowlists and an MCP gateway.

Ahead on:
- Reliability, 70 against 25
- Schema & documentation, 91 against 62
- Agent ergonomics, 79 against 58
- Payments & pricing, 60 against 20

Also in its favour:
- Open source

Watch for: litellm 1.82.7 and 1.82.8 on PyPI carried a credential stealer for about 40 minutes on 24 March 2026


## Why the edge

### Reliability: LiteLLM +45

- Hugging Face Inference Providers (25): Hosted lines. status.huggingface.co is a Better Stack page with 90-day component history for the Hub, Inference Endpoints, Spaces, the CDNs and Jobs, but no component for Inference Providers or the router (10 of 20). With no component, there is no readable incident history for the surface agents call, and the feed's 23 items from 10 June to 7 October 2026 don't name it (5). No rate limits for the router were found; the Hub rate-limits page gives numbers for Hub APIs, resolvers and pages only (0). No 429 or overload guidance for the router was found (0). No SLA found (0). Chat completions on the router is generally available; the Responses API is labelled beta (10). Routing between providers with `:fastest` or `:cheapest` softens a single provider's outage, which this checklist doesn't score.
- LiteLLM (70): Read with the local-software lines, since the gateway runs on the operator's hardware and BerriAI hosts nothing an agent calls. litellm on PyPI states Python 3.10 to 3.14, and the gateway ships as a Docker image, a Helm chart and Terraform modules, with GHCR images signed by cosign (20). 51 GitHub Actions workflows plus a CircleCI config cover unit, proxy-database, end-to-end, chaos, mutation and UI tests. The GitHub API was rate-limited for our reader on 6 November and Actions pages refused it on 6 October, so we couldn't confirm main is passing (15 of 25). The issue tracker showed 1,674 open issues on 6 November, with eight bug reports among the 15 newest, seven of them with a reply, against a project that tags several releases a day (10 of 25, down from an unchecked 12). Release notes carry breaking-change bullets, but breaking changes land in weekly minor releases on the 1.x line, so version numbers don't signal them (10 of 15). 1.108.1, past 1.0 (15).

### Payments & pricing: LiteLLM +40

- Hugging Face Inference Providers (20): No x402, MPP or L402 (0). Per-token prices for every model and provider published without a login in the router's /v1/models and on model pages (20). No free tier since 7 October 2026, when free users lost their included monthly credits; PRO's $2.00 of credits needs a subscription (0). Sign-up, token creation and credit purchase are browser steps (0).
- LiteLLM (60): Read with the self-hosted rule, since an agent uses the free gateway and Enterprise is a sales-led licence for the same software. No x402, MPP or L402 (0). MIT with no account and no card, so 20, 20 and 20 on the last three lines. Model calls cost what the operator's provider keys cost.

### Schema & documentation: LiteLLM +29

- Hugging Face Inference Providers (62): No OpenAPI document for the router (openapi.json paths answer 404). The task reference pages are generated from typed JSON Schema specs in huggingface.js, and the router's /v1/models gives a machine-readable catalogue, so 12 of 25. llms.txt for the Inference Providers docs and a Markdown twin of every page via `.md` (10). Guides say what each task and policy is for, with a quick setup page for coding agents (14 of 20). Parameter tables with types for chat completion, though `response_format` and `tool_choice` show as unknown types (9 of 15). Examples in Python, JavaScript and curl on every task page, but no documented error responses for the router (9 of 15). No changelog of its own; the Hub changelog doesn't cover it and dated changes are only in the hub-docs history (8 of 15).
- LiteLLM (91): Every gateway serves Swagger at /, ReDoc at /redoc and the raw schema at /openapi.json, and the docs host a public Swagger explorer (25). llms.txt, llms-full.txt and a Markdown twin of every page via `.md` (10). Pages say what a feature is for and where its limits are, and the key-auth page explains how permissions are inherited and where they aren't, but the reference is very large for a model to navigate (16 of 20). OpenAI-shaped request schemas from Pydantic models, with `metadata`, `litellm_params` and config blocks left as free-form objects (10 of 15). A full error reference with the envelope, every status, response headers and how to tell gateway limits from provider limits, plus examples on every page (15). Release notes per version with dates, newest v1.108.0 and v1.106.7 on 4 November 2026 (15).

### Agent ergonomics: LiteLLM +21

- Hugging Face Inference Providers (58): Router reading of the model checklist (tool use, structured output, caching, context, batch, SDKs, errors), as for openrouter. Tool calling through the OpenAI-compatible API with `tool_choice`, support flagged per provider in /v1/models (15 of 20). Structured output documented, support flagged per provider and false on some (10 of 15). No prompt caching guidance found, though the Enterprise usage API counts cached input tokens (3 of 15). Routes to models with up to 1,048,576 tokens of context per the model list, a judgement call since a router has no default model (15). No batch API (0 of 10). Official clients in Python and JavaScript, plus any OpenAI SDK (10). Errors not documented (5 of 15).
- LiteLLM (79): Read with the API lines for the gateway an agent calls. Responses size through the usual `max_tokens` and streaming, and the MCP gateway can replace a large tool catalogue with four virtual tools (tool search) or filter tools by semantic relevance, which cuts context cost (20 of 25). Key, team and spend listings page and filter, though we didn't check every list call (15 of 20). Errors keep the OpenAI envelope with a string `code`, gateway 429s carry `retry-after`, `rate_limit_type` and `reset_at`, management routes answer RFC 9457 problem+json, and a table says which errors are safe to retry (20). Retries, cooldowns and fallbacks run inside the gateway and the docs say which errors to retry, but there are no idempotency keys for the management writes (12 of 20). Any OpenAI or Anthropic SDK works by changing the base URL, but the only first-party client is the Python SDK, and keys and spend need Postgres and a master key before the first call (12 of 15).

### Transparency & trust: Hugging Face Inference Providers +8

- Hugging Face Inference Providers (71): Closed service under Terms of Service that name Inference Providers, with an Apache-2.0 Python client and an MIT JavaScript client (20). The security page and the docs agree on no training, no stored bodies and 30-day logs, but the privacy policy dates from 28 March 2023 and each provider's own data policy governs the rest (18 of 30). No deprecation policy found. Provider support changes and the 7 October removal of free credits are dated only in the docs repository history (5 of 20). The privacy policy lists 11 subprocessors with countries per the Inference Endpoints check, and the docs name every provider a request can reach, though not where each runs (15 of 20).
- LiteLLM (63): MIT for everything outside enterprise/, which has its own licence (25 of 30). The data security page (updated 6 November 2026) and security.md agree that a self-hosted gateway sends no data or telemetry to BerriAI, and the gateway stores prompts and spend in the operator's own Postgres. We found no terms of service or privacy policy on litellm.ai for its site, trial or Enterprise licence (20 of 30). A version support policy since 29 June 2026 (four stable minor lines), deprecated pages labelled in the docs, and release notes with breaking-change bullets (15 of 20). Usage telemetry, new in v1.107.0, is off by default, lists every field it can send and goes only to a table or endpoint the operator sets. A main-branch commit of 23 October 2026 made the Admin UI chat post a hashed user id to chat-telemetry.litellm.ai, and it was removed on 24 October before any tagged release contained it, so it isn't deducted. The start-up fetch of the price map from GitHub is documented with an opt-out (17 of 20).

### Security & auth: Hugging Face Inference Providers +7

- Hugging Face Inference Providers (79): Model reading. Fine-grained user access tokens that can be limited to the `Make calls to Inference Providers` permission, rotated and revoked, plus a public revocation endpoint for leaked tokens, and organisation approval of fine-grained tokens on paid plans (30). Hugging Face says it doesn't store user data for training, but data handling past the router follows each provider's policy, with no per-request filter to exclude providers that train or retain (12 of 20). Request bodies and responses aren't stored when routed and debug logs are kept up to 30 days without user data or tokens, with provider retention outside that statement (10 of 15). Usage by model and provider in account settings, an Enterprise usage API, and Team and Enterprise admins can disable providers and set a spending limit (13 of 15). SOC 2 Type 2 for the Hub, of which the docs say Inference Providers is a feature, and security.txt valid to 2030 per the Inference Endpoints check; no bug bounty found (14 of 20).
- LiteLLM (72): Read with the tool checklist for self-hosted software. Virtual keys are hashed, revocable and blockable, with model, route, MCP server, budget, rate and expiry limits, and a `proxy_admin_viewer` read-only role exists. Rotation with a grace period is Enterprise only, so 25, less 10 because the docs pass a key as `?key=` on `/key/info` and on the Claude Code marketplace manifest (15 of 30). `allowed_routes`, MCP permissions by key and team, an approval queue for submitted MCP servers and stdio MCP servers off by default from 1.104.0 (15 of 20). Guardrails can run before a model call and on MCP tool results, and an OWASP LLM Top 10 page maps each risk to a control, but prompt-injection detectors such as Lakera need an Enterprise licence and all of it is off by default (12 of 15). Request and spend logs per key in the open-source build; audit logs of admin actions are Enterprise only (12 of 15). security.md with GitHub private reporting, a bug bounty from $500 to $3,000 for P0 and P1 reports, a security announcements list, SOC 2 Type II per the data security page, CodeQL, OSV and Scorecard workflows, and advisories published on GitHub. No security.txt, and reports without a video are closed unread (18 of 20).

## Score by category

| Category | Weight | Hugging Face Inference Providers | LiteLLM | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 25 | 70 | LiteLLM +45 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 62 | 91 | LiteLLM +29 |
| Agent ergonomics | 13% (16.2 this run) | 58 | 79 | LiteLLM +21 |
| Security & auth | 14% (17.5 this run) | 79 | 72 | Hugging Face Inference Providers +7 |
| Payments & pricing | 10% (12.5 this run) | 20 | 60 | LiteLLM +40 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 80 | 82 | LiteLLM +2 |
| Transparency & trust | 7% (8.8 this run) | 71 | 63 | Hugging Face Inference Providers +8 |
| Negative events | ≤15 | 0 | -12 | |
| **Total** | | **54 · C** | **62.4 · B** | |

## Facts side by side

| Fact | Hugging Face Inference Providers | LiteLLM |
| --- | --- | --- |
| Kind | Model router | Model router |
| Vendor | Hugging Face, Inc. | BerriAI |
| Hosted endpoint | `https://router.huggingface.co/v1` | no (local only) |
| Transports | HTTP | HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | Proprietary service under the Hugging Face Terms of Service, which name Inference Providers. The `huggingface_hub` Python client is Apache-2.0 and `@huggingface/inference` is MIT | MIT, except the enterprise/ directory, which is under its own licence and needs an Enterprise licence key |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-29 | 2026-11-05 |
| Terms last updated | 2022-09-15 | no document linked |
| Privacy policy last updated | 2023-03-28 | no date given |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 483k npm/wk, 71.5M PyPI/wk | 63k stars, 22.5M PyPI/wk |

## Verdicts

**Hugging Face Inference Providers.** One Hugging Face token reaches open models on 18 partner providers at the providers' own prices, with a public model list that shows each provider's price, context and tool support. Router rate limits, error responses and its own status component were not found in the reviewed documentation, and free accounts have had no included credits since 7 October 2026.

**LiteLLM.** An MIT-licensed gateway that puts 100+ model providers behind one OpenAI-compatible API, with virtual keys, budgets, fallbacks and an MCP gateway, released several times a week. Its security record is the main limitation. Two PyPI releases carried a credential stealer on 24 March 2026, and 30 GitHub advisories followed in 12 months, five of them critical.

## Before you call either

### Hugging Face Inference Providers

1. Read https://router.huggingface.co/v1/models before choosing a provider; it shows price, context and `supports_tools` per provider
2. Pin a provider with `model:<provider>` when tool calling or structured output matters, since support varies by provider
3. Use a fine-grained token with only the Inference Providers permission, and send `X-HF-Bill-To` to bill an organisation
4. Back off on 429 without assuming a Retry-After header, since none is documented for the router

### LiteLLM

1. Pin an exact litellm version or image digest, verify the cosign signature, and never install an unpinned latest in CI
2. Give each agent a virtual key limited to its models, routes and MCP servers, with a budget and an expiry
3. Treat a 429 with `retry-after` as the gateway's own limit and wait that long; a 429 without it came from the provider
4. Set `NO_DOCS`, `NO_REDOC` and `NO_OPENAPI` to True in production, and use the `-non_root` image variant
5. Set `LITELLM_LOCAL_MODEL_COST_MAP=True` where egress is blocked, since start-up otherwise fetches the price map from GitHub

## Questions

### Which is better for AI agents, Hugging Face Inference Providers or LiteLLM?

LiteLLM scores 62.4 (B) on agent readiness against Hugging Face Inference Providers's 54 (C), and leads in 5 of 7 scored categories. Hugging Face Inference Providers leads on security & auth and transparency & trust.

### Do Hugging Face Inference Providers and LiteLLM need an API key?

Both need an API key.

### Can an agent call Hugging Face Inference Providers and LiteLLM without installing anything?

Hugging Face Inference Providers has a hosted endpoint at https://router.huggingface.co/v1. No hosted endpoint is listed for LiteLLM.

### Are Hugging Face Inference Providers and LiteLLM open source?

No open-source release is listed for Hugging Face Inference Providers. LiteLLM is open source (MIT, except the enterprise/ directory, which is under its own licence and needs an Enterprise licence key).


## For agents

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

## Other comparisons with Hugging Face Inference Providers or LiteLLM

- [Amazon Bedrock vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/amazon-bedrock-vs-hugging-face-inference-providers.md)
- [Claude API vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/anthropic-api-vs-hugging-face-inference-providers.md)
- [Azure OpenAI in Foundry Models vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/azure-openai-vs-hugging-face-inference-providers.md)
- [BlockRun.AI vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/blockrun-ai-vs-hugging-face-inference-providers.md)
- [Cerebras Inference vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/cerebras-inference-vs-hugging-face-inference-providers.md)
- [Cloudflare AI Gateway vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-hugging-face-inference-providers.md)
- [Cloudflare Workers AI vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-hugging-face-inference-providers.md)
- [Cohere Chat API (Command models) vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/cohere-chat-vs-hugging-face-inference-providers.md)
- [DeepInfra vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/deepinfra-vs-hugging-face-inference-providers.md)
- [DeepSeek API vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/deepseek-api-vs-hugging-face-inference-providers.md)
- [Glimpse vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/elorian-glimpse-vs-hugging-face-inference-providers.md)
- [Fireworks AI Inference vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/fireworks-inference-vs-hugging-face-inference-providers.md)
- [Gemini Developer API vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/gemini-api-vs-hugging-face-inference-providers.md)
- [GroqCloud vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/groq-vs-hugging-face-inference-providers.md)
- [Hugging Face Inference Providers vs Inkling 2 Small](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-inkling-2-small.md)
- [Hugging Face Inference Providers vs Jais 3](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-jais-3.md)
- [Hugging Face Inference Providers vs Meta Model API](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-meta-model-api.md)
- [Hugging Face Inference Providers vs MiniMax API](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-minimax-api.md)
- [Hugging Face Inference Providers vs Mistral AI API](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-mistral-api.md)
- [Hugging Face Inference Providers vs Muse Spark Open](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-muse-spark-open.md)
- [Hugging Face Inference Providers vs Novita AI](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-novita-ai.md)
- [Hugging Face Inference Providers vs OpenAI API](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-openai-api.md)
- [Hugging Face Inference Providers vs Beam 1.0](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-reflection-beam.md)
- [Hugging Face Inference Providers vs SambaCloud](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-sambanova.md)
- [Hugging Face Inference Providers vs SiliconFlow](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-siliconflow.md)
- [Hugging Face Inference Providers vs Simplismart](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-simplismart.md)
- [Hugging Face Inference Providers vs StepFun API](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-stepfun-api.md)
- [Hugging Face Inference Providers vs SWE-2 Flash](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-swe-2-flash.md)
- [Hugging Face Inference Providers vs Together AI Inference](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-together-inference.md)
- [Hugging Face Inference Providers vs Vertex AI (Gemini Enterprise Agent Platform)](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-vertex-ai.md)
- [Hugging Face Inference Providers vs xAI API (Grok)](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-xai-api.md)
- [Antseed vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/antseed-vs-hugging-face-inference-providers.md)
- [Antseed vs LiteLLM](https://www.anchorterminal.com/compare/antseed-vs-litellm.md)
- [Cloudflare AI Gateway vs LiteLLM](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-litellm.md)
- [Eden AI vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/eden-ai-vs-hugging-face-inference-providers.md)
- [Eden AI vs LiteLLM](https://www.anchorterminal.com/compare/eden-ai-vs-litellm.md)
- [Hugging Face Inference Providers vs OpenRouter](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-openrouter.md)
- [Hugging Face Inference Providers vs Router.com (Ramp Router)](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-ramp-router.md)
- [Hugging Face Inference Providers vs RouterPlus](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-routerplus.md)
- [Hugging Face Inference Providers vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-tencent-tokenhub.md)
- [Hugging Face Inference Providers vs Vercel AI Gateway](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-vercel-ai-gateway.md)
- [LiteLLM vs OpenRouter](https://www.anchorterminal.com/compare/litellm-vs-openrouter.md)
- [LiteLLM vs Router.com (Ramp Router)](https://www.anchorterminal.com/compare/litellm-vs-ramp-router.md)
- [LiteLLM vs RouterPlus](https://www.anchorterminal.com/compare/litellm-vs-routerplus.md)
- [LiteLLM vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/litellm-vs-tencent-tokenhub.md)
- [LiteLLM vs Vercel AI Gateway](https://www.anchorterminal.com/compare/litellm-vs-vercel-ai-gateway.md)
- [Hugging Face Inference Providers vs Nemotron 3.5 Super VL](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-nemotron-3-5-super-vl.md)
- [Hugging Face Inference Providers vs Prism Inference](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-prism-inference.md)

---

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