amCharts 5 MCP Server vs Ref

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.

Ref 15

Scored as a hosted MCP server. ref.tools and docs.ref.tools are paused for this run pending a ruling on Ref's terms, so their readings are per the 8 October check, not re-read on 4 November. ref.tools/status is a single-page application. Its eight components, 30-day bars and four incidents were read on 8 October only from the script file the page loads, which this run doesn't count (script bundles are barred), so the page's contents are unread (0 of 20) and no incident history is readable (5). No rate limit is documented. The 8 October reading of a ratelimit-policy header came from a request to Ref's API, which this run doesn't count as evidence, and credit allowances aren't rate limits (0). No 429 or retry guidance was found in the reviewed documentation (0). No SLA found (0). The hosted endpoint is generally available (10). 0+5+0+0+0+10 = 15.

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.

Ref 35

No dated release or API change of Ref Context is readable within 180 days. The ref-tools-mcp package was last published on 4 November 2025 (3.0.3, the version-bump commit is dated the same day in the repository), 365 days before this check. The 31 July and 30 September 2026 updates were read on 8 October from mailchi.mp, whose robots.txt now disallows every crawler, so they're struck; the docs changelog index gives months only, and both covered Ref Plans. The repository's last commits, on 28 September 2026, are dependency updates, which can't set recency (0 of 30). No releases or dated entries in the 90 days from 6 August (0). Per the 8 October reading of GitHub's API, closed issues show two to five comments each and September's open pull requests one comment each, and the docs promise a reply within one business day (15). The official MCP registry lists tools.ref/ref-tools-mcp under Ref's own domain, at 3.0.1 from 28 October 2025, still on 4 November (15). Dependabot alerts were cleared on 28 September 2026. The only workflow builds a bundle on release, with no tests (5). 0+0+15+15+5 = 35.

amCharts 5 MCP Server 60

Free, with nothing to buy for the server and no payment protocol. 0 + 20 + 20 + 20 = 60.

Ref 35

Per the 8 October check, not re-read on 4 November (ref.tools and docs.ref.tools are paused for this run pending a ruling on Ref's terms). No x402, MPP or L402 (0). One credit per tool call and $10 per 1,000 extra credits are published without a login (20). The free plan is 200 one-time credits that never expire, not a recurring allowance, and the docs don't say whether sign-up needs a card (15). A person has to sign up in a browser to get a key (0).

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.

Ref 68

Both tools have typed JSON Schema inputs in the open-source server (25). docs.ref.tools/llms.txt, llms-full.txt and a Markdown copy of every docs page exist (10). The descriptions say what each tool does and that a read takes the exact URL from a search, with nothing on when not to use them (12). Each tool takes one required string with no enums or bounds, and private search is switched on by writing ref_src=private inside the query text (7). The README shows two worked search-and-read sequences with token counts. No error responses are documented (6). The npm package follows semver, but the repository has no changelog file and no GitHub releases, and product changes appear only in monthly newsletters listed on the docs changelog page (per the 8 October check), whose copies on mailchi.mp now disallow every crawler (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.

Ref 63

Per the 8 October check, not re-read on 4 November. OAuth through Scalekit with two scopes, public_docs:read and private_docs:read, or an API key. Key rotation and revocation aren't described in the docs (26). Less 10 because the install docs give ?apiKey=YOUR_API_KEY in the URL as a documented option (16). Both tools are read-only, the scopes separate public from private search, and team roles limit who can add to the index (16). ref_read_url returns third-party web content. Ref's comparison page says Centure.ai detects and blocks prompt injection in scraped and uploaded content, which we can't test (11). ref.tools/activity logs user identity, tool calls and arguments (13). A valid security.txt (expires 1 July 2027) and a security@ref.tools contact, with no acknowledgement time. SOC 2 is in progress, not complete. No bug bounty or published advisories found, OSV holds none for ref-tools-mcp, and the repository has no SECURITY.md. This run reads security.txt plus a reporting route with no stated time as 7 (mails-ai, tokenrip), in place of the 8 given on 8 October (7). 26-10+16+11+13+7 = 63.

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.

Ref 69

Per the 8 October check, not re-read on 4 November (ref.tools and docs.ref.tools are paused for this run pending a ruling on Ref's terms). The stdio server is MIT, and it is a thin client. The search service is closed. Its terms and privacy policy are drawn by script and were read on 8 October only from the script files the pages load, which this run doesn't count, so both are unread here. The line is held, as Prefactor's licence and data-handling lines were when its script-drawn terms were struck (18). The security page describes encryption, tenant isolation, zero-data-retention terms at model providers and a seven-day limit on agent transcripts. No DPA was found, and Centure.ai is named on the comparison page but not in the subprocessor table (18). No deprecation policy found. The pricing page says legacy $9 and $19 subscriptions continue unchanged (3). 19 subprocessors are named with what each can see. Data locations aren't stated (14). 18+18+3+14 = 53.