sentrul-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SENTRUL_API_KEY | No | Your Sentrul API key. Leave unset to use the free tier. | auto-provisioned |
| SENTRUL_API_BASE | No | Override the Sentrul gateway base URL (staging / local dev). | https://app.sentrul.com/api |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sentrul_researchA | Fetch a URL and run Sentrul's research-agent on the content. Returns summary, entities, claims, and a public Langfuse trace URL. |
| sentrul_compliance_scanC | Scan text for common compliance patterns (PII, PCI, HIPAA, GDPR data). Returns findings + severity. Not legal advice. |
| sentrul_trace_lookupC | Retrieve a public Langfuse trace by ID. Returns the structured trace payload for inspection in the client. |
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 3 tools
Each tool has a clearly distinct purpose with no overlap. sentrul_compliance_scan analyzes text for compliance patterns, sentrul_research processes web content for research insights, and sentrul_trace_lookup retrieves specific trace data. An agent can easily differentiate between scanning, researching, and trace lookup functions.
All tool names follow a consistent 'sentrul_' prefix with descriptive suffixes (compliance_scan, research, trace_lookup). The naming pattern is uniform and predictable, using snake_case throughout without any deviations or mixed conventions.
With only 3 tools, the set feels thin for a server named 'sentrul-mcp-server', which suggests a broader scope for compliance and research operations. While each tool is distinct, the count is borderline low, potentially limiting functionality for agents working in this domain.
The tools cover scanning, research, and trace lookup, but there are notable gaps for a compliance/research domain. Missing operations include updating or managing scans, configuring research parameters, or handling trace modifications, which could lead to dead ends in agent workflows.