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

Microsoft Outlook Mail

22 tools · footprint 29

5 high 8 med 9 low

12 tools · footprint 29

1 critical 3 high 1 med 7 low COSOGLBA+3 more

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

16 tools · footprint 29

1 critical 1 high 1 med 13 low COSOPCI+1 more

9 tools · footprint 28

2 critical 3 high 1 med 3 low COSOGLBA+2 more

25 tools · footprint 28

2 high 15 med 8 low

23 tools · footprint 28

2 high 8 med 13 low

17 tools · footprint 28

1 critical 5 high 4 med 7 low

19 tools · footprint 28

3 high 6 med 10 low COSOSOX

15 tools · footprint 27

1 high 10 med 4 low

Oracle NetSuite

11 tools · footprint 27

3 high 3 med 5 low COSOSOX

5 tools · footprint 27

2 critical 2 med 1 low HIPAA

15 tools · footprint 26

1 critical 1 high 7 med 6 low GLBA

5 tools · footprint 26

1 critical 2 high 2 med COSOSOX

22 tools · footprint 26

1 critical 6 high 15 low

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.