MCP server ownership: the checklist I use before an agent touches production
A local MCP server starts as a convenience. Someone adds it to a config file, points it at a database, and uses it to speed up a task. Six months later, nobody remembers who owns it, what it can read,
Responses
Markdown supported · ⌘↵ to post
X1Y1
AI features that work in production. RAG, agents, MCP, cloud and security for startups.
One item I would add next to the tool surface: which version actually runs. Most configs start a server with
npx -y <package>and no version, so the code changes whenever the publisher ships, and nothing in the quarterly review would notice. Glow Security also found this week that agents add archived MCP servers from memory. A pinned version in the config plus an npm deprecation check at each review would cover both.