Sentinel Signal MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SENTINEL_API_KEY | No | API key; if omitted, auto-trial minting is used unless disabled | |
| SENTINEL_BASE_URL | No | Scoring API base URL | https://api.sentinelsignal.io |
| SENTINEL_NO_TRIAL | No | Set to '1' to disable auto-trial minting | |
| SENTINEL_API_BASE_URL | No | Legacy alias for SENTINEL_BASE_URL | |
| SENTINEL_TOKEN_BASE_URL | No | Token-service base URL used for trial key minting | https://token.sentinelsignal.io |
| SENTINEL_TIMEOUT_SECONDS | No | HTTP request timeout in seconds | 30 |
| SENTINEL_CREDENTIALS_PATH | No | Path to cached credentials file | ~/.sentinel/credentials.json |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| score_workflowC | Call Sentinel Signal unified workflow scoring (POST /v1/score). |
| get_limitsA | Return plan limits for the current API key (GET /v1/limits). |
| list_workflowsA | List supported workflows and current model versions (GET /v1/workflows). |
| get_workflow_schemaB | Fetch required fields, optional fields, and example payloads for a workflow (GET /v1/workflows/{workflow}/schema). |
| validate_workflow_payloadA | Validate and normalize a workflow payload without consuming a scoring call (POST /v1/workflows/{workflow}/validate). |
| get_usageA | Return usage for the current API key (GET /v1/usage). Optional month format: YYYY-MM. |
| score_batchB | Score up to 25 workflow items sequentially in one request (POST /v1/score/batch). |
| submit_feedbackB | Submit structured feedback for a prior scoring request (POST /v1/feedback). |
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 8 tools
Tools are mostly distinct, but score_workflow and score_batch both deal with scoring and could be confused without careful reading of their descriptions. get_usage and get_limits are also related but easily differentiated.
All tool names follow a consistent lowercase verb_noun pattern (get_, score_, submit_, list_, validate_). This makes the set highly predictable.
With 8 tools, the server covers scoring (single and batch), validation, schema retrieval, workflow listing, feedback, usage, and limits. This is well-scoped for the API's purpose.
The tool surface covers the main lifecycle of workflow scoring: single/batch scoring, validation, schema, workflow list, feedback, and account info. A minor gap might be a tool to retrieve historical scoring results, but this is likely handled by the score responses themselves.