Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@@presencis/regulatory-mcp Search compliance Q&A for GDPR data retention requirements"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Read-only Model Context Protocol server for the public Presencis regulatory corpus. It answers from a bundled JSON snapshot. It does not open network connections and it does not write files.
Tools:
list_frameworks — optional exact jurisdiction or sector
get_framework — exact id
find_crosswalk — source_id, optional target_id
search_compliance_qa — query, optional regulation and limit
map_sector_obligations — exact sector
Question hits cite https://presencis.com/questions/<slug>/.
Node.js 22 or newer.
npm install
export PRESENCIS_CORPUS_ROOT=/path/to/corpus
export CROSSWALKS_DATA=/path/to/regulatory-crosswalks/data
npm run sync
npm run build
node dist/index.jsnpm test builds and runs the stdio JSON-RPC checks.
Related MCP server: @nomos/medxpert/reg-connector
The same command works for Claude Desktop, Cursor, and Antigravity. After this package is published:
{
"mcpServers": {
"presencis-regulatory": {
"command": "npx",
"args": ["-y", "@presencis/regulatory-mcp"]
}
}
}Until publish, point command at node and args at the absolute path of dist/index.js.
Apache-2.0.
Find comparison summaries and sector overlaps for an active source id, optionally one target id.
Inputs: source_id (required), target_id.
Fetch one active framework by exact id, including related comparisons and sector overlaps.
Inputs: id (required).
List active regulatory frameworks. Optional exact filters: jurisdiction, sector id.
Inputs: sector, jurisdiction.
List active frameworks mapped to a sector and the published sector description. Does not invent article-level duties.
Inputs: sector (required).
Rank public compliance questions. Returns canonical https://presencis.com/questions// links.
Inputs: query (required), limit, regulation.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Offline Protocol packages, workflows and integration guides over HTTPS. Read-only.
Read-only access to Distributed Risk's desk notes and the official US record: consolidated screening lists, OFAC recent actions, CISA KEV, Federal Register, travel advisories, reference rates and Treasury yields.
Read-only U.S. healthcare dataset metadata, schemas, immutable downloads, and checksums.
Keyless, read-only US public records for agents: SEC, FDA, enforcement, sanctions, market data.
