Learn
Short, evidence-first notes on MCP trust, health, and install hygiene. Built for humans and agents. Numbers always come from the live census — never invented.
What changed in MCP 2026-07-28
The stateless revision removed the initialize handshake and made server/discover mandatory. What it means if you run an MCP server.
Agent checklist: install an MCP server safely
For coding agents and humans driving them — a short runbook.
How to evaluate an MCP server before you install it
A practical pre-install gate that pairs census checks with human review.
How to tell if an MCP server is official
Brand match is an evidence problem, not a naming contest.
Look-alike MCP namespaces and brand risk
Why a verified domain is not the same as vendor affiliation.
MCP registry vs The MCP Census
The registry lists servers. The census checks health and ownership with evidence.
MCP server health signals that actually matter
Archived repos, deprecated packages, dead remotes — fact-based signals.
MCP supply-chain checklist for platform teams
Inventory and gate MCP servers like any other plugin supply chain.
MCP trust score explained
A published point sum with factors — not a vibes rating.
Official vs Verified vs trust score
Three different claims on an MCP Census card — plain English.
Remote vs local MCP servers
Hosted endpoints and installable packages are different risk shapes.
What is an MCP server?
Plain-language definition of Model Context Protocol servers and why install choices matter.
Why MCP servers need a census
Directories scale discovery. Trust needs continuous evidence.
Want the live table? Open lookup. Agents: llms.txt · API.