Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/muyen/vibe-to-prodWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/muyen/vibe-to-prod/notion)<a href="https://agentmods.dev/mcp/muyen/vibe-to-prod/notion"><img src="https://agentmods.dev/badge/mcp/muyen/vibe-to-prod/notion/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/muyen/vibe-to-prod/notion"><img src="https://agentmods.dev/badge/mcp/muyen/vibe-to-prod/notion.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
notion scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"notion": {
"command": "npx",
"args": [
"-y",
"@notionhq/notion-mcp-server"
],
"env": {
"NOTION_API_KEY": "${NOTION_API_KEY}"
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 5. Installing the file brings all of them; each is measured and scanned on its own page.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 12 lines scan A b24b9a51bbd4
notion is an MCP server published in the GitHub repository muyen/vibe-to-prod (33 stars, last pushed 6mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-04.
Other mcp servers, from other repositories
tierward
Read a Tierward project's governance state (doctor, team-settings, arch-audit, skills) over MCP. Runs locally from the tierward npm package.
ainecto
Ainecto MCP connector for workspace, document, ERD, diagram, task, and attachment workflows. Runs locally from the @ainecto/mcp npm package.
notion
Notion's hosted MCP server: lets the agent search, read and edit pages and databases. Remote server at mcp.notion.com.
atlassian-mcp
A focused, read-only MCP server for Jira and Confluence Cloud. Runs locally from the @andreimaxim/atlassian-mcp npm package.
notion-mpm
MCP server for Notion workspace integration. Runs locally from the notion-mpm Python package.
notion-mcp
MCP server "notion-mcp" as configured in michaelwaves/notion-mcp. Runs locally from the @yc-hackathon/notion-mcp npm package.