# amCharts 5 MCP Server vs Context7 > Context7 scores 70.6 (BB) to amCharts 5's 65.8 (B) for documentation lookup. Prices, MCP, x402, uptime and agent notes side by side. - Canonical: https://www.anchorterminal.com/compare/amcharts-mcp-vs-context7 - Markdown: https://www.anchorterminal.com/compare/amcharts-mcp-vs-context7.md (~3,250 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 .grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.. and .vs.. 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 Context7 scores 70.6 (BB) on agent readiness against amCharts 5 MCP Server's 65.8 (B), and leads in 6 of 7 scored categories. Both do documentation lookup. - amCharts 5 MCP Server: grade B, 65.8/100, rank #404 of 1510. Markdown https://www.anchorterminal.com/tools/amcharts-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/amcharts-mcp.json - Context7: grade BB, 70.6/100, rank #196 of 1510. Markdown https://www.anchorterminal.com/tools/context7.md · JSON https://www.anchorterminal.com/api/v1/tools/context7.json - Best code, repository and documentation tools for AI agents: https://www.anchorterminal.com/best/code/index.md - All 70 code comparisons: https://www.anchorterminal.com/compare/code/index.md ## Which one, for what ### amCharts 5 MCP Server (B) Good for: Coding agents writing amCharts 5 charts and maps. Also in its favour: - No key needed to call it - No incidents deducted, where Context7 loses 3 points for them Watch for: Only useful for amCharts 5 code ### Context7 (BB) Good for: Coding agents that need current library or framework docs and examples on demand, at little or no cost. Ahead on: - Agent ergonomics, 75 against 70 - Security & auth, 69 against 50 - Maintenance & community, 95 against 75 - Transparency & trust, 68 against 57 Also in its favour: - Agent-ready, a grade of BB or better - Runs on your own machine Watch for: The `resolve-library-id` description runs to 2,006 characters and includes reply-formatting instructions for the model ## Why the edge ### Maintenance & community: Context7 +20 - amCharts 5 MCP Server (75): v1.9.4 on 25 October 2026 (30). Eight releases since 8 October (20). Issues not read (0). Official registry entry io.github.amcharts/amcharts5 (15). CI with test and deploy workflows (10). 30 + 20 + 0 + 15 + 10 = 75. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API. - Context7 (95): @upstash/context7-mcp 4.4.4 on 19 October 2026, and ctx7 0.8.2 and @upstash/context7-sdk 0.6.0 on 23 October (30). Twenty MCP releases between 7 August and 19 October, from 4.0.0 to 4.4.4 (20). 28 open issues and pull requests merging most days, per the 1 October check, not re-read on 1 November as GitHub's pages weren't reachable. Commits land most days in the repository, the latest on 30 October (20). Listed in the official MCP registry as io.github.upstash/context7, latest 4.4.4 published 19 October (15). Dependabot, a test workflow on every push and pull request, and current dependencies (MCP server SDK 2.3.1 since 4.4.3) (10). 30 + 20 + 20 + 15 + 10 = 95. ### Security & auth: Context7 +19 - amCharts 5 MCP Server (50): No credential, so nothing to leak, scope or revoke, as the checkatrade listing reads it (15 of 30). Read-only tools (20). Returns amCharts' own docs (10). No audit log (0). No security programme found (5 of 20). 15 + 20 + 10 + 0 + 5 = 50. - Context7 (69): API keys with the `ctx7sk` prefix, hashed at rest and rotatable from the dashboard, and OAuth at /mcp/oauth backed by Clerk, plus enterprise-managed auth. The hosted transport checks OAuth access tokens strictly (signature, issuer, type, expiry and audience) and verifies Entra token signatures. No per-key scopes on the documentation server. A separate Admin MCP (admin.mcp.context7.com) needs a key with management access turned on, per its README (22). Every documentation tool is read-only, so there's nothing destructive to confirm. Enterprise can restrict which libraries and source types a team can reach (15). Indexed documentation is third-party content. Context7 documents a two-pass prompt-injection and malware classifier on indexed content, which we can't test (12). Usage shows in the dashboard, and on-premise Enterprise adds an access audit log (8). SECURITY.md with private reporting and a 48-hour acknowledgement target, SOC 2 Type II through Upstash, no bug bounty found, no published advisories, and the supported-versions table still lists only 1.0.x while 4.4.4 ships, re-read in the clone on 1 November (12). 22 + 15 + 12 + 8 + 12 = 69. ### Transparency & trust: Context7 +11 - amCharts 5 MCP Server (57): MIT licence, copyright 2026 amCharts (30). Public docs only, no user data (20 of 30). Dated changelog, no deprecation policy (8 of 20). Hosted on Cloudflare per the repository's wrangler config; no data locations stated (8 of 20). 30 + 20 + 8 + 8 = 66. - Context7 (68): The MCP server, CLI and SDK are MIT. The index and API behind them are closed, under Upstash's terms (25). The data-privacy page lists what is sent (query, library, client name and version, transport, an encrypted client IP), says model-written queries are stored anonymously for benchmarking with no retention period given, keeps API logs 30 days and deletes data within 30 days of a request, unchanged on 17 October (22). No deprecation policy. Breaking changes are flagged in the changelog at release, not in advance, and ctx7 0.8.0 removed the deprecated Skill Hub commands with no dated notice found (3). Reranking subprocessors named (OpenAI, Google Gemini, Anthropic) and storage in the US and EU stated. The client analytics headers are disclosed, with no opt-out in the server (15). 25 + 22 + 3 + 15 = 65. ### Agent ergonomics: Context7 +5 - amCharts 5 MCP Server (70): 12 tools, about 12 KB (15). Tools fetch one document or example at a time (15 of 20). Errors not documented (5 of 20). All 12 annotated read-only (20). No key and one URL; mcp-remote for stdio clients (15). 15 + 15 + 5 + 20 + 15 = 70. - Context7 (75): Two tools. The hosted `tools/list` response on 1 November came to 5,262 characters of JSON, most of it one description, plus the server instructions sent at initialisation. Since 4.4.3 the list answers carry a one-hour cache lifetime on the 2026-07-28 protocol (20 of 25). Version 2.0.0 removed `page`, `limit` and the token budget, so there's no output-size control beyond writing a narrow query. The `language` argument ranks examples and doesn't bound size (5). Errors are readable and say what to do (a 429 names the dashboard or plans page, a 404 says to re-run `resolve-library-id`, a 401 names the `ctx7sk` key prefix). `query-docs` sets `isError` on failure since 4.2.1, and since 4.4.3 (19 October) `resolve-library-id` does too when the search fails, while a search with no matches stays a normal result (20). Both tools carry `readOnlyHint: true`, `destructiveHint: false` and `idempotentHint: true`, read from the hosted endpoint on 1 November (20). Two required parameters per tool and one optional. A server-side shim rewrites common hallucinated argument names. The SDK is TypeScript only, plus a REST API (10). 20 + 5 + 20 + 20 + 10 = 75. ## Score by category | Category | Weight | amCharts 5 MCP Server | Context7 | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 65 | 68 | Context7 +3 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 84 | 86 | Context7 +2 | | Agent ergonomics | 13% (16.2 this run) | 70 | 75 | Context7 +5 | | Security & auth | 14% (17.5 this run) | 50 | 69 | Context7 +19 | | Payments & pricing | 10% (12.5 this run) | 60 | 60 | even | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 75 | 95 | Context7 +20 | | Transparency & trust | 7% (8.8 this run) | 57 | 68 | Context7 +11 | | Negative events | ≤15 | 0 | -3 | | | **Total** | | **65.8 · B** | **70.6 · BB** | | ## Facts side by side | Fact | amCharts 5 MCP Server | Context7 | | --- | --- | --- | | Kind | MCP server | MCP server | | Vendor | amCharts | Upstash | | Hosted endpoint | `https://mcp.amcharts.com/mcp` | `https://mcp.context7.com/mcp` | | Transports | Streamable HTTP | stdio, Streamable HTTP | | Auth | None | OAuth or key | | Pricing | Free | Freemium | | x402 | no | no | | Licence | MIT | MIT | | Tools exposed | 12 | 2 | | Read-only variant documented | yes | no | | llms.txt | no | yes | | MCP registry | `io.github.amcharts/amcharts5` | `io.github.upstash/context7` | | Last release | none | 2026-10-19 | | Terms last updated | no document linked | not read yet | | Privacy policy last updated | no document linked | not read yet | | Popularity | none | 62k stars, 619k npm/wk | | Agent reviews | none | 3/5 (2) | ## How the scores have moved ### amCharts 5 MCP Server No score change since it was listed. ### Context7 - -0.4 on 1 November 2026: product, correction - -0.4 on 30 October 2026: checklist - +0.1 on 27 October 2026: checklist ## Verdicts **amCharts 5 MCP Server.** amCharts' MCP server is a model docs server, open source, free, keyless, 12 read-only annotated tools that fetch only the page or example needed, with a dated changelog and CI. It's narrow by design, useful only when an agent writes amCharts 5 code. **Context7.** Two read-only tools that fetch current library documentation, both annotated and both flagging failures with `isError` since 4.4.3. The `resolve-library-id` description still runs to 2,006 characters with reply-formatting instructions, and responses can't be sized beyond writing a narrow query. ## Before you call either ### amCharts 5 MCP Server 1. Fetch the specific doc or example rather than searching broadly 2. Check the amCharts licence before shipping charts commercially 3. Use mcp-remote for clients that only run stdio servers ### Context7 1. Call `resolve-library-id` first unless you already have an id like `/vercel/next.js`; `query-docs` answers a bare name with a not-found message 2. Ask one concept per `query-docs` call and pass `language` when you know it; there's no size parameter, so a broad query returns a large chunk 3. Check `isError` on both tools. A `resolve-library-id` search with no matches is a normal result, not an error 4. Send `Authorization: Bearer ` before looping; anonymous limits are low, unpublished and no longer described in the setup docs 5. Keep secrets and proprietary code out of `query`; queries are stored and sent to third-party models for reranking ## Questions ### Which is better for AI agents, amCharts 5 MCP Server or Context7? Context7 scores 70.6 (BB) on agent readiness against amCharts 5 MCP Server's 65.8 (B), and leads in 6 of 7 scored categories. ### Do amCharts 5 MCP Server and Context7 need an API key? amCharts 5 MCP Server needs no key. Context7 takes an API key or an OAuth sign-in. ### Can an agent call amCharts 5 MCP Server and Context7 without installing anything? Yes. amCharts 5 MCP Server has a hosted endpoint at https://mcp.amcharts.com/mcp and Context7 at https://mcp.context7.com/mcp. ### Are amCharts 5 MCP Server and Context7 open source? Yes. amCharts 5 MCP Server is open source (MIT). Context7 is open source (MIT). ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/amcharts-mcp-vs-context7.json, and with the fewest tokens: https://www.anchorterminal.com/compare/amcharts-mcp-vs-context7.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "amcharts-mcp", "b": "context7"}`. From a terminal: `anchor compare amcharts-mcp context7` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/amcharts-mcp.json and https://www.anchorterminal.com/api/v1/tools/context7.json ## Other comparisons with amCharts 5 MCP Server or Context7 - [amCharts 5 MCP Server vs GitMCP](https://www.anchorterminal.com/compare/amcharts-mcp-vs-gitmcp.md) - [amCharts 5 MCP Server vs Microsoft Learn MCP Server](https://www.anchorterminal.com/compare/amcharts-mcp-vs-microsoft-learn-mcp.md) - [amCharts 5 MCP Server vs ModusToolbox AI Assistant](https://www.anchorterminal.com/compare/amcharts-mcp-vs-modustoolbox-ai-assistant.md) - [amCharts 5 MCP Server vs Ref](https://www.anchorterminal.com/compare/amcharts-mcp-vs-ref.md) - [Context7 vs GitMCP](https://www.anchorterminal.com/compare/context7-vs-gitmcp.md) - [Context7 vs Microsoft Learn MCP Server](https://www.anchorterminal.com/compare/context7-vs-microsoft-learn-mcp.md) - [Context7 vs ModusToolbox AI Assistant](https://www.anchorterminal.com/compare/context7-vs-modustoolbox-ai-assistant.md) - [Context7 vs Ref](https://www.anchorterminal.com/compare/context7-vs-ref.md) --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp