Astro Docs MCP (official, remote)

68/100
Last tested 2026-11-11 (Fresh: tested within 30 days) Working (tool call tested 2026-11-11) No key needed for the tools we called

Advisories: not checked (remote-only)

Security review: not tested

Score = points from our five tests (install, handshake, maintenance, docs, license). Not a quality or security rating. Methodology

  • Install20/20
  • Handshake30/30
  • Maintenance0/25
  • Docs15/15
  • License3/10

Tested Astro's hosted docs MCP at https://mcp.docs.astro.build/mcp (server 'Astro Docs server' 1.0.0; source withastro/docs-mcp, 68 GitHub stars when checked). Initialize and tools/list worked with no account (1 tool). Real call: search_astro_docs for 'content collections schema' returned the matching Astro docs sections. Scored from the repo: it has no license file (GitHub detects none; our rubric gives 3 of 10 when no license is found) and its last push was 2025-10-25, more than a year before our test (maintenance 0). The hosted endpoint may be newer than the repo; we can't see that.
Tool-call test (2026-11-11, direct MCP stdio client, no LLM): pass. 1 of 1 read call passed anonymously. Evidence: live endpoint probe, Nov 11, 2026.

Transport (tested 2026-11-11): Streamable HTTP

Token cost (estimate): approx. 64 tokens, cl100k estimate (1 tool, measured 2026-11-11). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.

Permissions: 1 read, 0 write (state-changing), 0 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown

Auth: none. Rate limit: unknown. Pricing unit: unknown.

  • search_astro_docs — read

remote handshake listed tools without credentials; no recorded key or OAuth

Score 68/100 · Tools 1 · Token cost approx. 64 tokens · Compare · Last tested 2026-11-11 · Server version 1.0.0 · Remote endpoint https://mcp.docs.astro.build/mcp (streamable-http) · Repo withastro/docs-mcp

Summary: Astro Docs MCP (official, remote) completed an MCP handshake without credentials and exposed 1 tools.

Evidence summary

Handshake
pass
Tools listed
1
Context cost
approx. 64 tokens, cl100k estimate (1 tools, measured 2026-11-11; an estimate) ranking · add up your servers' context cost
API key
No key needed for the tools we called
Tested
2026-11-11

Test results

TestResultPointsEvidence
installpass20Endpoint https://mcp.docs.astro.build/mcp reachable over streamable-http (HTTP 200) in 0.2s; no install step for remote servers.
handshakepass30MCP initialize (protocol 2025-06-18, server Astro Docs server 1.0.0) + tools/list over streamable-http succeeded with no credentials; 1 tools listed in 0.2s. Tool calls may still need a key.
maintenancefail0No recent activity found.
docspass15README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (vendor repo README (github.com/withastro/docs-mcp)).
licensepartial3License not machine-detected as OSI (no license found).

Local-model readiness

Token cost (estimate): approx. 64 tokens, cl100k estimate for 1 tools · about 1% of an 8k context. This is an estimate from our testing (counted with cl100k_base).

Small-model friendly (schema heuristic, not a model result): unknown.

Not tested

Small-model task runs: Not yet tested.

What we tested and what we didn't

Tested on 2026-11-11

  • Install from the registry (remote endpoint: connection only)
  • We connected with no credentials and asked for its tool list: it listed 1 tool (Method details: MCP initialize then tools/list)
  • Maintenance signals (last push, archived/deprecated status)
  • Docs (README length, install and config example)
  • License (OSI-approved or not)
  • Token cost (estimate)

Not tested

  • Security: not audited (no code review, no permission or data-flow analysis)
  • Real tasks (no functional task runs yet)
  • Behaviour with real credentials or a real account
  • Performance, rate limits or load
  • Correctness of results beyond the listed tasks

Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.

Known security issues

Not checked (remote-only): hosted endpoint, version unknown.

Monthly roundup: MCP security issues, October 2026.

Tool list changes

Baseline recorded from the 2026-11-11 test run; changes appear after the next test.

Snapshot hash (fingerprint of the tool list)

c9e1f3949284: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.

Feeds: RSS · JSON.

Raw test record (JSON)
{
  "name": "astro-docs-remote",
  "version": null,
  "registry": "remote",
  "status": "working",
  "tested": "2026-11-11",
  "tools_count": 1,
  "deprecated": false,
  "archived": false,
  "tests": {
    "install": [
      "pass",
      20,
      "Endpoint https://mcp.docs.astro.build/mcp reachable over streamable-http (HTTP 200) in 0.2s; no install step for remote servers."
    ],
    "handshake": [
      "pass",
      30,
      "MCP `initialize` (protocol 2025-06-18, server Astro Docs server 1.0.0) + `tools/list` over streamable-http succeeded with no credentials; 1 tools listed in 0.2s. Tool calls may still need a key."
    ],
    "maintenance": [
      "fail",
      0,
      "No recent activity found."
    ],
    "docs": [
      "pass",
      15,
      "README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (vendor repo README (github.com/withastro/docs-mcp))."
    ],
    "license": [
      "partial",
      3,
      "License not machine-detected as OSI (no license found)."
    ]
  }
}

Install

https://mcp.docs.astro.build/mcp

Tools listed

search_astro_docs

Tool history: captured Nov 11, 2026. All tool history.

Quick config

{
  "mcpServers": {
    "astro-docs-mcp-remote": {
      "type": "http",
      "url": "https://mcp.docs.astro.build/mcp"
    }
  }
}

Add to config Opens the config generator with this server selected.

Setup

  1. Install. No install step: it is a remote server at https://mcp.docs.astro.build/mcp.
  2. Configure. Add the mcpServers entry below to your MCP client config.
  3. Verify. Restart the client and check that tools/list returns tools (1 in our test).
{
  "mcpServers": {
    "astro-docs-mcp-remote": {
      "type": "http",
      "url": "https://mcp.docs.astro.build/mcp"
    }
  }
}

Test history

Follow this server (RSS) · Monthly changelog

Related: Best docs MCP servers · Lowest context cost MCP servers

FAQ

Is Astro Docs MCP deprecated?

No. astro-docs-remote was not deprecated or archived when we last tested it on 2026-11-11.

What replaces Astro Docs MCP?

Nothing; Astro Docs MCP (official, remote) is not deprecated as of 2026-11-11.

Does Astro Docs MCP need an API key?

No. It completed an MCP handshake with no credentials and listed 1 tools.

Embed the badge

TestedMCP: 68/100, tested 2026-11-11

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Claim this listing · Report an issue