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.
303MCP servers
4476tools
Reset 303 of 303 servers
Ashby
17 tools · footprint 16
6 med 11 low
CData Connect AI
8 tools · footprint 16
1 critical 1 high 6 low
DataHub
24 tools · footprint 16
8 med 16 low
Google Compute Engine
25 tools · footprint 16
1 critical 6 med 18 low
Google Drive
7 tools · footprint 16
2 high 2 med 3 low
Guru
5 tools · footprint 16
3 med 2 low
HealthEx
15 tools · footprint 16
1 high 11 med 3 low HIPAA
Lumin PDF
7 tools · footprint 16
2 high 2 med 3 low
Microsoft OneDrive (Work IQ)
17 tools · footprint 16
1 high 4 med 12 low
Mintlify
17 tools · footprint 16
2 high 7 med 8 low
Sumble
25 tools · footprint 16
2 high 2 med 21 low
ThoughtSpot Spotter
12 tools · footprint 16
6 med 6 low
Coupler.io
4 tools · footprint 15
1 high 3 low
Digits
10 tools · footprint 15
5 med 5 low
Dovetail
9 tools · footprint 15
5 med 4 low
Gmail
10 tools · footprint 15
2 high 1 med 7 low
‹ PrevPage 9 of 19Next ›
NPI RegistryDocs ↗
3 low · 3 tools · 0 SoD-flagged
regimes none

Tools needing tighter control (0 of 3)

None — every tool is low-risk, high-confidence, and outside PCI/HIPAA payload scope.
All other tools (3)
npi-registry.npi_lookup low conf highallow
Returns one provider's full NPPES record — legal name, practice address, taxonomy, and enumeration status — from CMS's publicly disclosable provider registry.
npi-registry.npi_search low conf highallow
Enumerates healthcare providers by name, location, specialty, or organization, returning batches of public NPPES directory records for provider-network research.
npi-registry.npi_validate low conf highallow
Checks an NPI's format and Luhn check digit locally, catching typos before a registry call; no data leaves the client and nothing is modified.