# amCharts 5 MCP Server vs GitMCP (slim)

> amCharts 5 scores 65.8 (B) to GitMCP's 40.2 (E) for documentation lookup. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/amcharts-mcp-vs-gitmcp.md (~3,400 tokens) · this version ~1,930 tokens · JSON https://www.anchorterminal.com/compare/amcharts-mcp-vs-gitmcp.json · canonical https://www.anchorterminal.com/compare/amcharts-mcp-vs-gitmcp
- 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)

amCharts 5 MCP Server scores 65.8 (B) on agent readiness against GitMCP's 40.2 (E), 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
- GitMCP: E 40.2, rank #1326 of 1510 · https://www.anchorterminal.com/tools/gitmcp.min.md
- amCharts 5 MCP Server, good for Coding agents writing amCharts 5 charts and maps. Ahead on Reliability, 65 against 15; Schema & documentation, 84 against 56; Agent ergonomics, 70 against 58; Security & auth, 50 against 42; Maintenance & community, 75 against 8; Transparency & trust, 57 against 36.
- GitMCP, good for Quick, keyless library docs for public GitHub projects in a coding agent.

| Category | amCharts 5 MCP Server | GitMCP |
| --- | --- | --- |
| Reliability (16%) | 65 | 15 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 84 | 56 |
| Agent ergonomics (13%) | 70 | 58 |
| Security & auth (14%) | 50 | 42 |
| Payments & pricing (10%) | 60 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 75 | 8 |
| Transparency & trust (7%) | 57 | 36 |

| Fact (where they differ) | amCharts 5 MCP Server | GitMCP |
| --- | --- | --- |
| Vendor | amCharts | Ido Salomon (GitMCP open-source project) |
| Hosted endpoint | `https://mcp.amcharts.com/mcp` | `https://gitmcp.io/{owner}/{repo}` |
| Licence | MIT | Apache-2.0 |
| Tools exposed | 12 | 4 |
| MCP registry | `io.github.amcharts/amcharts5` | not listed |
| Last release | none | 2026-05-08 |
| Popularity | none | 8.5k stars |

Why the edge:
- Maintenance & community, amCharts 5 MCP Server +67: 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.); GitMCP 8 (The last commit on main is 8 May 2026, 182 days before this check, and there are no tags or releases (0). Nothing in the last 90 days (0). Since May, outside issues and pull requests (#244 to #271, among them the security report #249 and fixes #256, #267 and #250) have gone without a maintainer reply or merge (3). Not found in the official MCP registry under any namespace (0). A run-tests workflow with vitest and a Playwright end-to-end workflow exist on push and pull request (5). 0 + 0 + 3 + 0 + 5 = 8.)
- Reliability, amCharts 5 MCP Server +50: amCharts 5 MCP Server 65 (Local-software reading for an open-source server that amCharts also hosts. Installs as @amcharts/amcharts5-mcp, and the hosted URL needs nothing installed (20). test.yml runs on the repository; pass state not read (15 of 25). Repository issues not read (0). A dated CHANGELOG.md with semver releases (15). Version 1.9.4 (15). 20 + 15 + 0 + 15 + 15 = 65.); GitMCP 15 (Scored as a hosted MCP server. No status page found (0) and so no readable incident history (5). The maintainer confirmed on issue #245 that gitmcp.io was throttled by Cloudflare for a few hours in May 2026, outside the 90-day window. No rate limits are documented (0) and nothing on 429 or retries (0). No SLA (0). The service is live with no beta or preview label (10). 0 + 5 + 0 + 0 + 0 + 10 = 15.)
- Schema & documentation, amCharts 5 MCP Server +28: amCharts 5 MCP Server 84 (12 tools read from tools/list with JSON Schema inputs (25). Docs served as Markdown to the agent (10). Descriptions say what each returns, and the docs explain the on-demand approach (16 of 20). Typed inputs with two enums (10 of 15). Worked examples in the README (8 of 15). Dated changelog (15). 25 + 10 + 16 + 10 + 8 + 15 = 84.); GitMCP 56 (Every tool registers a zod input schema, so inputs are typed JSON Schema (25). There is no llms.txt for GitMCP itself; the README on GitHub is the only Markdown documentation (5). Descriptions are generated per repository and say what each tool reads and when it helps ("Useful for general questions. Always call this tool first if asked about owner/repo"), but not when to avoid one (12). Inputs are a query string and an optional page number, with no enums or constraints beyond types (9). The README has three worked examples and no documented error responses (5). No versioning, tags, releases or changelog (0). 25 + 5 + 12 + 9 + 5 + 0 = 56.)
- Transparency & trust, amCharts 5 MCP Server +21: 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.); GitMCP 36 (Apache-2.0, with the whole service in the public repository (30). The README says the service stores no personal data or queries and keeps no repository content permanently, but there is no privacy policy or terms page (8). No deprecation policy or dated notices; SSE was removed on 8 May 2026 while the README still shows an SSE config for VS Code (0). The hosting stack (Cloudflare Workers, Workers AI, Vectorize, an Analytics Engine dataset) is visible in wrangler.jsonc but no processor is named for users, and invocation logs were turned off on 8 May (5). 30 + 8 + 0 + 5 = 43.)
- Agent ergonomics, amCharts 5 MCP Server +12: 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.); GitMCP 58 (Four tools per repository endpoint and five on gitmcp.io/docs, each short (25). Code search pages 30 results with a page number, and documentation search returns matched chunks instead of the whole file, but there is no size control on the fetch tool (10). Errors come back as tool text with no documented codes (5). Every tool is a read and the source sets readOnlyHint, but issue #266 reports the annotations are passed in a position the MCP SDK ignores, and the fix #267 is unmerged (8). No parameters to set up and nothing to configure; there are no SDKs, which a keyless MCP endpoint doesn't need (10). 25 + 10 + 5 + 8 + 10 = 58.)
- Security & auth, amCharts 5 MCP Server +8: 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.); GitMCP 42 (No credentials at all, so nothing to leak or scope (20). Every tool is a read of public content (15). Repository docs, code and fetched URLs reach the model unmarked, and fetch_generic_url_content fetches any absolute URL a document mentions, with no prompt-injection guidance in the README (2). No per-call visibility for the caller (0). SECURITY.md routes reports to a Google Form, but the server-side request forgery report in issue #249 (12 June 2026) and its proposed fix #256 have had no maintainer reply in almost five months. No certifications or bounty (5). 20 + 15 + 2 + 0 + 5 = 42.)