amCharts 5 MCP Server vs Microsoft Learn MCP Server

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.

Microsoft Learn MCP Server 13

The release notes, re-read on 4 November, still end at the plugin release on 23 March 2026, more than 180 days ago (0). The repository set @microsoft/learn-cli to 1.0.0 on 4 September 2026 (commit 90e1837), with no tag, release or changelog entry, so it isn't counted as a release. The plugin manifest is still 0.3.1 from 19 March 2026. No server entries in the last 90 days (0). Open issues per the 1 October check (eight, the oldest from June 2025; #100 got a documentation fix on 2 September 2026). Questions go to the GitHub repository (8). Registry line 15 to 0. The registry entry was read from the MCP registry's JSON API, a source Anchor Terminal no longer uses, and the repository carries no server.json, so no readable registry page shows the listing. The CLI has a vitest suite that the validation workflow runs on Node 22 and 24, Dependabot updates (the latest on 10 September 2026) and actions pinned to commit SHAs on 30 October. The server's own health isn't visible (5). 0 + 0 + 8 + 0 + 5 = 13.

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.

Microsoft Learn MCP Server 20

Scored as a hosted MCP server. No status page for Microsoft Learn or this endpoint was found (0), so there's no readable incident history (5). The FAQ (dated 5 May 2026, re-read on 4 November) says the free endpoint has rate limits for fair use but gives no numbers, and the release notes and best-practices page give none either (0). Throttling and 429 behaviour aren't documented. The best-practices page says to refresh tools/list and retry after a 400 or 404, which is safe-retry guidance for tool changes, and every tool is a read (5, a partial kept). No SLA (0). Generally available since 7 November 2025 per the release notes (10). 0 + 5 + 0 + 5 + 0 + 10 = 20.

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.

Microsoft Learn MCP Server 42

Contract line 20 to 0. The server is closed source, Microsoft publishes no tool definitions because it treats them as dynamic, and the only typed parameters are in the README's tool table. A parameter table isn't a published JSON Schema (read-ai, zapier-mcp), and calling the server's tools/list would be a request to the product's own endpoint, which this check doesn't make. No llms.txt found, but learn.microsoft.com returns the docs pages as Markdown when asked with Accept: text/markdown (the release notes, read that way on 4 November), as for copilot-studio-mcp, azure-devops-mcp and dynamics-365-sales, and the README is Markdown (10, was 5). The README table gives one line of purpose per tool, and the repository's three agent skills and a suggested system prompt say when to use each (12). Inputs are query and url strings plus an optional language string with no listed values (6). Configuration examples for about twenty clients and a troubleshooting table. No documented error responses beyond 405 (6). A release-notes page with seven dated entries, the last on 23 March 2026. Microsoft says the tool surface is dynamic and not versioned (8). 0 + 10 + 12 + 6 + 6 + 8 = 42.

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.

Microsoft Learn MCP Server 58

Three tools, which the README describes in one line each. We couldn't measure the live definitions (25). maxTokenBudget on the endpoint URL truncates search results to a token budget. microsoft_docs_fetch always returns the whole page and nothing pages (10). Errors aren't documented beyond the 400 or 404 refresh rule and a 405 for browsers (5). Every tool is a read and safe to repeat. We couldn't check whether readOnlyHint is set (8). One required parameter per tool and no auth. A CLI on npm, no SDKs (10).

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.

Microsoft Learn MCP Server 60

No credentials at all, so nothing to leak or scope (20). All three tools are reads (15). Results come from Microsoft's own documentation and code samples, which the README says is the only source (10). No per-call visibility for the caller, since there's no account (0). MSRC reporting with a 24-hour response target in SECURITY.md and Microsoft's bug bounty programme. microsoft.com's security.txt was past its Expires date per the 30 September check (15).