Skip to content

Audit your MCP setup

Paste your MCP config: everything your agent can do across every server, one permissions block, and a lockfile for CI.

Paste a config with "mcpServers" (Claude, Cursor) or "servers" (VS Code).

.mcp.json · claude_desktop_config.json · .cursor/mcp.json · .vscode/mcp.json

Read in your browser first. Only server names, URLs without query strings, package names and the names of env variables are sent. Values, keys and headers never leave this page.

ExampleA config with GitHub, Fetch and Slack. Audit yours to replace it.

3 servers found, 9 tools

Every server in the config, counted together.

9 tools: 1 can delete or cancel things, 2 do something that can't be undone, 1 change things and 5 only read.

Tools: 1 delete, 2 irreversible, 1 write, 5 read.

Exfil paths

A tool that reads private data, one that reads text someone else wrote, and one that can send data out make a path. In your report, click a tool to deny it and watch the count.

27 paths from private data to a way out

Recommended: deny 3 outbound tools (fetch, create_issue, slack_post_message).

Reads private data3

Reads files, mail, messages, databases, secrets, calendars or repositories.

Reads text others write3

Brings in text someone else can write: web pages, inbound email, messages, issues and comments.

Can send data out3

Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Show the 25 first paths
  1. github/get_file_contents → fetch/fetch → fetch/fetch
  2. github/get_file_contents → fetch/fetch → github/create_issue
  3. github/get_file_contents → fetch/fetch → slack/slack_post_message
  4. github/get_file_contents → github/list_issues → fetch/fetch
  5. github/get_file_contents → github/list_issues → github/create_issue
  6. github/get_file_contents → github/list_issues → slack/slack_post_message
  7. github/get_file_contents → slack/slack_get_channel_history → fetch/fetch
  8. github/get_file_contents → slack/slack_get_channel_history → github/create_issue
  9. github/get_file_contents → slack/slack_get_channel_history → slack/slack_post_message
  10. github/list_issues → fetch/fetch → fetch/fetch
  11. github/list_issues → fetch/fetch → github/create_issue
  12. github/list_issues → fetch/fetch → slack/slack_post_message
  13. github/list_issues → github/list_issues → fetch/fetch
  14. github/list_issues → github/list_issues → github/create_issue
  15. github/list_issues → github/list_issues → slack/slack_post_message
  16. github/list_issues → slack/slack_get_channel_history → fetch/fetch
  17. github/list_issues → slack/slack_get_channel_history → github/create_issue
  18. github/list_issues → slack/slack_get_channel_history → slack/slack_post_message
  19. slack/slack_get_channel_history → fetch/fetch → fetch/fetch
  20. slack/slack_get_channel_history → fetch/fetch → github/create_issue
  21. slack/slack_get_channel_history → fetch/fetch → slack/slack_post_message
  22. slack/slack_get_channel_history → github/list_issues → fetch/fetch
  23. slack/slack_get_channel_history → github/list_issues → github/create_issue
  24. slack/slack_get_channel_history → github/list_issues → slack/slack_post_message
  25. slack/slack_get_channel_history → slack/slack_get_channel_history → fetch/fetch

Claude Code permissions

One block for every scanned server, keyed by the names in your config: allow the reads, ask before a change or a way out, deny the deletes, and deny what you picked above.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__github__get_file_contents",
      "mcp__github__list_issues",
      "mcp__slack__slack_list_channels",
      "mcp__slack__slack_get_channel_history"
    ],
    "ask": [
      "mcp__github__create_issue",
      "mcp__github__merge_pull_request",
      "mcp__fetch__fetch",
      "mcp__slack__slack_post_message"
    ],
    "deny": [
      "mcp__github__delete_file"
    ]
  }
}
Capability tags behind 6 rules
  • mcp__github__get_file_contents private-data
  • mcp__github__list_issues private-data, untrusted-input
  • mcp__github__create_issue outbound
  • mcp__fetch__fetch untrusted-input, outbound
  • mcp__slack__slack_get_channel_history private-data, untrusted-input
  • mcp__slack__slack_post_message outbound

Lockfile for CI

Commit it next to your config. The check fails when any server serves different tools from the ones you reviewed.

mcp-lock.json
{
  "lockfileVersion": 1,
  "generatedBy": "anlyon.dev",
  "generatedAt": "2026-10-22T00:00:00.000Z",
  "servers": {}
}

CI check

curl -s -X POST "https://radar.anlyon.com/api/v1/audit/verify" --data-binary @mcp-lock.json | jq -e '.ok'

By server (3)

Each server in your config, as the index sees it.

  • githubremoteGitHubTools: 1 delete, 1 irreversible, 1 write, 2 read.5 tools
  • fetchremoteFetchTools: 0 delete, 0 irreversible, 0 write, 1 read.1 tool
  • slackremoteSlackTools: 0 delete, 1 irreversible, 0 write, 2 read.3 tools