@presencis/regulatory-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CROSSWALKS_DATA | Yes | Path to the regulatory-crosswalks data directory, set via `export CROSSWALKS_DATA=/path/to/regulatory-crosswalks/data`. | |
| PRESENCIS_CORPUS_ROOT | Yes | Path to the corpus directory, set via `export PRESENCIS_CORPUS_ROOT=/path/to/corpus`. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_frameworksA | List active regulatory frameworks. Optional exact filters: jurisdiction, sector id. |
| get_frameworkA | Fetch one active framework by exact id, including related comparisons and sector overlaps. |
| find_crosswalkB | Find comparison summaries and sector overlaps for an active source id, optionally one target id. |
| search_compliance_qaC | Rank public compliance questions. Returns canonical https://presencis.com/questions// links. |
| map_sector_obligationsB | List active frameworks mapped to a sector and the published sector description. Does not invent article-level duties. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.