# amCharts 5 MCP Server vs Context7 (slim)

> 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.

- Full: https://www.anchorterminal.com/compare/amcharts-mcp-vs-context7.md (~3,250 tokens) · this version ~1,930 tokens · JSON https://www.anchorterminal.com/compare/amcharts-mcp-vs-context7.json · canonical https://www.anchorterminal.com/compare/amcharts-mcp-vs-context7
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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: B 65.8, rank #404 of 1510 · https://www.anchorterminal.com/tools/amcharts-mcp.min.md
- Context7: BB 70.6, rank #196 of 1510 · https://www.anchorterminal.com/tools/context7.min.md
- amCharts 5 MCP Server, good for Coding agents writing amCharts 5 charts and maps. Also No key needed to call it; No incidents deducted, where Context7 loses 3 points for them.
- Context7, 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 Agent-ready, a grade of BB or better; Runs on your own machine.

| Category | amCharts 5 MCP Server | Context7 |
| --- | --- | --- |
| Reliability (16%) | 65 | 68 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 84 | 86 |
| Agent ergonomics (13%) | 70 | 75 |
| Security & auth (14%) | 50 | 69 |
| Payments & pricing (10%) | 60 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 75 | 95 |
| Transparency & trust (7%) | 57 | 68 |

| Fact (where they differ) | amCharts 5 MCP Server | Context7 |
| --- | --- | --- |
| 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 |
| 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) |

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.)