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
Guidepoint
5 tools · footprint 10
2 med 3 low
isolved People Cloud
6 tools · footprint 10
2 med 4 low
Lightfield
5 tools · footprint 10
2 med 3 low
Shopify
6 tools · footprint 10
1 med 5 low
Swagger (SmartBear)
25 tools · footprint 10
10 med 15 low
Benchling
4 tools · footprint 9
2 high 2 med
Boltz
11 tools · footprint 9
7 med 4 low
CargoAi
6 tools · footprint 9
1 med 5 low
ClinicalTrials.gov Connector
6 tools · footprint 9
1 med 5 low
Exa
7 tools · footprint 9
1 med 6 low
Exa
4 tools · footprint 9
1 med 3 low
FactSet AI-Ready Data
18 tools · footprint 9
1 med 17 low
HubSpot Developer MCP Server (App & CMS Development)
21 tools · footprint 9
4 med 17 low
Indeed
4 tools · footprint 9
1 med 3 low
Canary Data
14 tools · footprint 8
14 low
Google Contacts (People API MCP Server)
3 tools · footprint 8
3 low
‹ PrevPage 13 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.