MCP server exposing the **Sovereign AI Blog** ([sovgrid.org](https://sovgrid.org)) — a hands-on engineering log of self-hosted AI on NVIDIA DGX Spark hardware (GB10/SM121A). 44+ and growing articles covering SGLang, Mistral, Voxtral, OpenClaw setups, fixes, and benchmarks. **Tools:** - `search_blog` — full-text TF-IDF search across all articles - `get_article` — fetch full article content by slug - `diagnose_sglang` — validate SGLang configs against GB10/SM121A constraints **Use case:** Training data on niche AI hardware is sparse and stale. This MCP gives agents direct, structured access to verified, version-current setups instead of hallucinating. **License:** MIT (server) / CC BY-SA 4.0 (content) **Auth:** none, free tier, 60 req/min/IP **Privacy:** server-log analytics only, no client-side tracking
Sovereign AI Blog is a remote MCP server published at mcp.sovgrid.org. It has been probed 7 times since 9/10/2026. It answered in 7 of them (100.0%), a near-uninterrupted record. Median response time is 403 ms, placing it among the faster endpoints. It offers a narrow, focused set of 4 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
diagnose_sglang — Description cut off mid-sentence, losing critical implementation detailssearch_blog — Parameter schema (e.g., 'query' type) not explicitly definedlist_tags — No parameter documentation for a simple endpointRisk: medium
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/cipherfoxie-sovereign-mcp)<a href="https://mcpmetrics.io/servers/cipherfoxie-sovereign-mcp"><img src="https://mcpmetrics.io/badge/cipherfoxie/sovereign-mcp/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-12 00:29:02 | Legacy | 400 | 403 | 200 | 532 | 2025-11-25 |
| 2026-09-11 22:37:38 | Legacy | 400 | 515 | 200 | 783 | 2025-11-25 |
| 2026-09-11 20:45:13 | Legacy | 400 | 413 | 200 | 431 | 2025-11-25 |
| 2026-09-11 18:52:42 | Legacy | 400 | 344 | 200 | 333 | 2025-11-25 |
| 2026-09-11 16:59:56 | Legacy | 400 | 337 | 200 | 330 | 2025-11-25 |
| 2026-09-11 15:07:20 | Legacy | 400 | 397 | 200 | 410 | 2025-11-25 |
| 2026-09-10 21:16:35 | Auth-gated | 401 | 331 | 401 | 331 | — |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.