MCP compliance catalog

Every MCP tool in the SCOPE compliance index, grouped by server — risk posture, regulatory exposure, and the tools that warrant tighter governance.
387MCP servers
5470tools
Reset 387 of 387 servers
Microsoft Outlook Mail
22 tools · footprint 29
5 high 8 med 9 low
Stripe API
12 tools · footprint 29
1 critical 3 high 1 med 7 low COSOGLBA+3 more
Ticket Tailor
20 tools · footprint 29
2 high 14 med 4 low PCI
Vibe Prospecting
12 tools · footprint 29
1 critical 4 high 1 med 6 low
Wix
16 tools · footprint 29
1 critical 1 high 1 med 13 low COSOPCI+1 more
GoCardless
9 tools · footprint 28
2 critical 3 high 1 med 3 low COSOGLBA+2 more
GovTribe
25 tools · footprint 28
2 high 15 med 8 low
Magic Patterns
23 tools · footprint 28
2 high 8 med 13 low
Sprouts
17 tools · footprint 28
1 critical 5 high 4 med 7 low
WordPress.com
19 tools · footprint 28
3 high 6 med 10 low COSOSOX
Grain
15 tools · footprint 27
1 high 10 med 4 low
Oracle NetSuite
11 tools · footprint 27
3 high 3 med 5 low COSOSOX
Quo
5 tools · footprint 27
2 critical 2 med 1 low HIPAA
Addepar
15 tools · footprint 26
1 critical 1 high 7 med 6 low GLBA
Databricks
5 tools · footprint 26
1 critical 2 high 2 med COSOSOX
Lusha
22 tools · footprint 26
1 critical 6 high 15 low
‹ PrevPage 6 of 25Next ›
ClickHouse
1 critical 1 med 2 low · 4 tools · 1 SoD-flagged
regimes APPICCPAGDPRISO_27001LGPDPIPEDAPIPLPOPIASOC2UK_GDPR

Tools needing tighter control (1 of 4)

clickhouse.run_query critical conf highhuman approval
Executes arbitrary SQL against the ClickHouse cluster, able to bulk-read any table and — depending on the connection's grants — drop databases or mutate rows irreversibly.
All other tools (3)
clickhouse.list_databases low conf highallow
Enumerates every database name on the ClickHouse cluster, exposing the schema layout to the caller.
clickhouse.list_tables low conf highallow
Lists the tables within a specified database, revealing that database's schema structure to the caller.
clickhouse.run_chdb_select_query medium conf highaudit
Runs ad-hoc SQL through chDB's embedded engine, which can pull data from local files, S3, and remote endpoints reachable by the MCP host.