
Self Hosted Ai
org.sovgridPublished by sovgrid.orgOfficial publisherv1.0.0Updated Oct 24, 2026
Engineering log of self-hosted AI on NVIDIA DGX Spark (GB10/SM121A). 60+ articles indexed.
Overview
Lets an assistant search and read a public engineering blog about self-hosted AI on NVIDIA DGX Spark hardware.
- What you can do
- Exposes a blog corpus of articles on self-hosted AI to AI agents through read-only tools. Tools include search_blog for TF-IDF full-text search with optional tag filters and sorting, list_articles for paginated listing, list_tags for topic discovery, get_article for fetching a full article by slug, and diagnose_sglang for matching a runtime error against a curated rule set for SGLang on GB10/SM121A. All tools are read-only and idempotent.
- When to use it
- Useful when an assistant needs version-current, hands-on information about niche self-hosted AI stacks, such as SGLang or vLLM on GB10, ARM64 TTS pipelines, KV-cache and quantization tradeoffs, or MCP server design, instead of relying on possibly stale training data.
- Requirements
- A remote Streamable HTTP endpoint; no authentication, API keys, or local runtime are required. The README notes a free tier limited to 60 requests per minute per IP.
Installation
In SourceWeft
- Open Self Hosted Ai in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/org.sovgrid%2Fself-hosted-ai/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"self-hosted-ai": {
"type": "http",
"url": "https://mcp.sovgrid.org/self-hosted-ai?ref=mcp-io"
}
}
}README
Sovereign AI MCP
[CI] [License: MIT] [Content: CC BY-SA 4.0] [MCP Registry] [smithery badge] [Glama MCP server] [Glama connector] [Write-up]
MCP server exposing the Sovereign AI Blog to AI agents. The blog is a hands-on engineering log of self-hosted AI on NVIDIA DGX Spark (GB10/SM121A).
Live endpoint: https://mcp.sovgrid.org/self-hosted-ai
Transport: Streamable HTTP (FastMCP)
Auth: none (free tier, 60 req/min/IP)
Why use it
Training data on niche hardware (GB10, SM121A, SGLang on ARM64) is sparse and stale. This MCP gives agents direct, structured access to 180+ articles documenting actual setups, fixes, and benchmarks. If you're building or debugging on similar stacks, your agent can pull verified, version-current information instead of hallucinating.
The corpus covers SGLang and vLLM patches for GB10, voxtral and TTS pipelines on ARM64, KV-cache and quantization tradeoffs, podcast-grade audio generation, MCP server design, knowledge-base construction, and the operational side of running it all on a hardened European VPS.
Tools
All tools are read-only, idempotent, and declared with ToolAnnotations so MCP clients can calibrate retry policy and trust signals. Inputs use Pydantic Annotated[type, Field(description=...)] so parameter docs reach agents through introspection. Outputs are typed BaseModel shapes — schemas are real, not vacuous dicts.
Quick start
With Claude Code
Verify:
With Cline / Continue / other MCP clients
Add to your client's MCP server config:
Run locally
From source (uv)
Docker
The repo ships a placeholder data/knowledge-base.json (zero articles, valid schema) so the server starts and answers MCP introspection cleanly out-of-the-box. To populate it with real content, generate from the sovgrid.org blog source using scripts/generate_knowledge_base.py, or build your own KB matching the schema in src/knowledge.py. Or just use the live endpoint at https://mcp.sovgrid.org/self-hosted-ai.
A walk-through of the same KB pattern (Markdown plus JSON index, no vector store) is documented in Build a Self-Hosted Knowledge Base with Plain Text and LLMs.
Architecture
- FastMCP 1.27+ with Streamable HTTP transport at path
/self-hosted-ai - DNS rebinding protection via
TransportSecuritySettings: only allows requests withHost: mcp.sovgrid.org(or localhost for healthchecks) - Health endpoint at
/healthreturns article count and KB generation timestamp - Knowledge base is a flat JSON file generated from blog Markdown content; loaded at startup, queried via TF-IDF for
search_blog
The server is stateless. All blog content is already public (CC BY-SA 4.0). No PII, no auth tokens, no secrets.
Operations
Live deployment runs on a privacy-focused European VPS via Docker, fronted by Caddy with TLS. Server logs flow into a privacy-respecting analytics pipeline (Caddy JSON access logs, no client-side tracking, no JS pixels).
License
- Server code: MIT, see LICENSE
- Blog content (returned by tools): CC BY-SA 4.0, see creativecommons.org/licenses/by-sa/4.0/
Contact
- Blog: sovgrid.org
- Nostr:
[email protected](NIP-05) —npub1ndrjgfcwkc0y4753zyj3p7qjf795pvjq2dn4m7y7f72vmu7t0nrs6y363u - Bug reports / questions: open an issue
Source: README.md at commit 53838cd
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts