@presencis/regulatory-mcp
OfficialRelated Servers
Alternatives to @presencis/regulatory-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables querying enterprise records and retention policies from any MCP client over stdio, with read-only tools for searching records, fetching retention verdicts, identifying archival candidates, summarizing departments, forecasting retentions, and viewing audit history.-
- AlicenseNot gradedqualityBmaintenanceEnables local read-only retrieval and search across 27 global medical device regulatory knowledge hubs (NMPA/FDA/MDR/PMDA etc.) using four MCP tools, with zero credentials and no external network calls.1Apache 2.0
- AlicenseNot gradedqualityNot gradedmaintenanceExposes policy, control, risk and system lookup tools plus an agent-as-a-tool query endpoint over stdio or streamable HTTP, so clients can run hybrid and graph retrieval, traverse knowledge-graph neighbors, and assess control-coverage gaps. Answers come back cited and guardrailed, and it runs fully offline without API keys.MIT
- AlicenseNot gradedqualityBmaintenanceEnables read-only local retrieval of medical-device and orthopedic standards via MCP tools, supporting searches by standard number, name, region, committee, topic, official links, and related regulations without network access or credentials.1Apache 2.0
- AlicenseAqualityBmaintenanceEnables users to access six offline, read-only guidance tools that generate team configuration and early-exit drafts, validate supplied layout paths, explain methods, and draft workflows and owner batches from bounded inputs without reading arbitrary files or calling networks.6MIT
- AlicenseAqualityBmaintenanceGives AI assistants a read-only, offline interface to the FinOps Foundation's published guidance — its principles, phases, domains, 22 capabilities with Crawl/Walk/Run maturity assessments, personas, and an 88-entry KPI library — so FinOps questions are answered with the Foundation's own text and formulas rather than improvised ones. It exposes 11 tools, document resources, and four guided prompts over stdio, with every response carrying its source URL and license.1146 npmMIT
TDQS
Scored across 5 tools
Two pairs overlap significantly: map_sector_obligations largely duplicates list_frameworks with a sector filter (plus a sector description), and find_crosswalk returns the same comparison/sector-overlap data that get_framework already bundles. The descriptions do help steer selection, but an agent could plausibly choose the wrong tool for a sector-scoped framework listing.
All names are snake_case verb_noun constructions (list_frameworks, get_framework, find_crosswalk, search_compliance_qa, map_sector_obligations), which is predictable and readable. Only minor deviation is the mix of verbs (find vs search vs map) for what could be treated as retrieval operations.
Five tools is a lean but defensible surface for a read-only regulatory lookup service, with each tool nominally owning a resource type. Slightly thin given the overlap, but nothing feels gratuitous.
There is no tool to enumerate sectors or jurisdictions even though both are required as exact filter inputs to list_frameworks and map_sector_obligations, creating a discovery dead end. The surface is also entirely read-only with no way to fetch a single Q&A record or framework version history, and article-level duties are explicitly out of scope.