{"site":{"name":"MCP Risk","tagline":"Approve MCPs once. Know when they change.","description":"Evidence-backed trust profiles for MCP repos and configs. Approve a known-good state and monitor what changes.","url":"http://localhost:3000"},"hero":{"headline":"Know what your agents can run before they run it.","sub":"MCP Risk creates evidence-backed trust profiles for MCP repos and configs, so teams can approve a known-good state and monitor what changes.","assurances":["No execution by default","Config-aware","No email to preview"],"capabilities":["Approval records","Config fingerprints","Drift evidence","Trust card gallery"]},"primer":{"title":"New to MCP?","paragraphs":["The Model Context Protocol (MCP) lets AI agents connect to external tools and data through MCP servers — local processes or remote services that expose actions like reading files, querying databases, or calling APIs.","That power is the risk. An MCP server can ship a tool whose description quietly instructs the agent to exfiltrate secrets, or change behavior after you approve it. MCP Risk reads the repo and config, produces a trust profile you can approve, and flags when the approved state drifts."]},"method":{"title":"A trust profile is not a scan. It is an approval record.","body":"The scanner only produces evidence. The product is the lifecycle around that evidence: who approved what, under which config, and what changed afterwards.","steps":[{"number":"01","title":"Evidence","body":"Extract declared tools, install commands, dependencies, env keys, permission surfaces, and risky code patterns."},{"number":"02","title":"Config","body":"Evaluate the actual launch context: command, args, tokens, filesystem scope, network exposure, and client."},{"number":"03","title":"Approval","body":"Bind decisions to repo version, config hash, policy version, analyzer version, reviewer, and environment."},{"number":"04","title":"Drift","body":"Trigger re-review when tools, descriptions, dependencies, env vars, or install commands change materially."}]},"reviewFlow":{"title":"Every MCP approval should leave evidence behind.","body":"A calm chain from tool request, to trust profile, to approval, to drift.","exampleSession":[{"kind":"cmd","text":"$ mcp-risk profile github.com/example/mcp-server"},{"kind":"out","text":"subject: github.com/example/mcp-server"},{"kind":"out","text":"config: 9f1c…42ab"},{"kind":"out","text":"verdict: approve_with_conditions"},{"kind":"cmd","text":"$ mcp-risk diff approved latest"},{"kind":"warn","text":"change: env_key_added GITHUB_TOKEN"},{"kind":"warn","text":"change: tool_added run_shell"},{"kind":"bad","text":"result: re-review required"}],"driftDiff":{"caption":"Approved profile vs. the live server, three weeks later.","verdict":"Approval lapsed — re-review required before this server runs again.","lines":[{"sign":" ","text":"subject: github.com/example/mcp-server"},{"sign":" ","text":"config: 9f1c…42ab"},{"sign":"+","text":"env_key_added: GITHUB_TOKEN"},{"sign":"+","text":"tool_added: run_shell"},{"sign":"-","text":"verdict: approve"},{"sign":"+","text":"verdict: re-review required"}]}},"library":[{"type":"Guide","title":"MCP server security checklist","summary":"Practical review criteria for MCP repos and configs.","url":"/library#mcp-server-security-checklist"},{"type":"Playbook","title":"Approval workflow for teams","summary":"How to record, review, and re-approve MCP usage.","url":"/library#approval-workflow-for-teams"},{"type":"Notes","title":"Tool poisoning and drift","summary":"Why descriptions and schemas need ongoing monitoring.","url":"/library#tool-poisoning-and-drift"},{"type":"Example","title":"Claude Desktop config review","summary":"Common risks in local MCP configuration files.","url":"/library#claude-desktop-config-review"},{"type":"Reference","title":"Reading a trust profile","summary":"What each verdict, card, and drift signal means.","url":"/library#reading-a-trust-profile"},{"type":"Template","title":"Policy pack starter","summary":"Baseline rules for local dev and company laptops.","url":"/library#policy-pack-starter"}],"callToAction":{"title":"Generate your first MCP trust profile.","body":"Submit a repo or config. See the verdict and summary instantly — add your email to unlock the full evidence and downloadable card."},"api":{"submit":{"method":"POST","path":"/api/submit","body":{"repoOrConfig":"<github url or mcp.json contents>"},"returns":"Trust profile preview: verdict, riskLevel, summary, publicSlug, status."},"profileStatus":{"method":"GET","path":"/api/profile/{publicSlug}/status","returns":"Current scan status and profile for a submitted subject."}},"machineSurfaces":["/llms.txt","/api/site","/ai"]}