Every result you'll see in the next ten slides is real — pulled from the
live deploy at https://fillin.glyphapi.dev/mcp/
moments before this deck rendered. No mockups. No staging. No happy-path stubs.
Web search returns things the model already knows. Signal-to-noise inside an agent loop dies. Fillin is the substrate that returns only the delta.
receives a question from its operator:
This is a post-cutoff question by definition. The agent must either guess from training, hallucinate, or call an external tool.
I don't have information about MCP server developments or agent infrastructure released after my training cutoff of January 1, 2026. I can tell you about the MCP ecosystem as it existed in late 2025 — the Model Context Protocol specification, the early server examples, and Anthropic's reference implementations — but anything shipped in 2026 is outside my knowledge.
To answer this accurately, you'd need to consult recent sources like Hacker News, GitHub Releases for MCP-related repositories, or Anthropic's blog. I can synthesize what I find if you can share recent posts.
honest hedge. Best-case behavior — the agent acknowledges its limit. Worst-case is hallucinated specifics that sound plausible. Neither delivers value to the operator.
Five notable MCP and agent-infrastructure releases since your cutoff:
The pattern: hosted agent infra is going commercial (Microsoft), Anthropic is publishing production guidance, and the community is sharing operational lessons rather than just demos.
five citations · all real · all post-cutoff · all clickable. Click any link — they go to actual URLs that exist.
{
"name": "fillin_query",
"arguments": {
"query": "new MCP servers and agent infrastructure released",
"cutoff": "2026-01-01",
"k": 5
}
}
POST https://fillin.glyphapi.dev/mcp/ tools/call → fillin_query bearer auth · 60 rpm/IP cap
scoring: similarity × source_authority × recency_decay
— pulls 3×k candidates, reweights, slices to k. arXiv and GitHub Releases beat HN noise; newer beats older with a 90-day half-life.
Documents are filtered by published_at > cutoff at the
database layer — not the application layer. A doc from 2024 doesn't
enter the candidate pool, so it can't bleed into context. Smaller
context cost, cleaner signal, no redundant retrieval.
Similarity alone over-rewards HN noise that uses the right keywords. Authority weighting (arXiv 0.95 > GH 0.95 > RSS 0.75 > HN 0.70) and a 90-day recency half-life pull canonical sources to the top. Tunable per-corpus via env override.
Every result carries source, URL, publish timestamp, and similarity score. Agents synthesize grounded answers; humans verify by clicking. No black box. No hallucinated citations possible — if it's not in the corpus, it's not in the response.
Continuous ingestion from 4 sources: Hacker News, arXiv, RSS, GitHub Releases. Cron tick every 30 minutes. 6,109+ docs and growing.
why this matters for ZHCs: a Zero-Human Company's treasury wallet can fund and use Fillin in 4 API calls — no human in any step. That's not a side feature. That's the core architecture for autonomous customers.
verified by /security-scan today. The product you just experienced is the deployed product. Click into smithery.ai/servers/mandalazenwave/fillin to see the listing or open the URL above directly.
Add this to your ~/.claude/mcp.json
or your agent framework's equivalent:
{
"mcpServers": {
"fillin": {
"url": "https://fillin.glyphapi.dev/mcp/",
"transport": "streamable-http"
}
}
}
Three tools appear in your agent's toolset:
fillin_query,
fillin_stats,
fillin_health.
The agent decides when to call them. You decide what to do with what they return.