sigmodx-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SIGMODX_API_KEY | Yes | Your Sigmodx API key. | |
| SIGMODX_AGENT_ID | Yes | Your Sigmodx agent UUID. |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sigmodx_log_invoice_decisionA | Log an invoice approval decision to Sigmodx for cryptographic attestation. Use when an AI agent approves, rejects, or escalates an invoice. The input payload is hashed client-side — invoice data never leaves your environment. |
| sigmodx_log_gl_decisionA | Log a GL entry review decision to Sigmodx. Use when an AI agent approves, flags, or blocks a journal entry. Segregation of duties violations are auto-blocked. |
| sigmodx_log_anomaly_decisionA | Log an anomaly detection decision to Sigmodx. Use when an AI agent flags, clears, or escalates a financial transaction anomaly. Critical severity items are automatically escalated for immediate review. |
| sigmodx_verify_attestationA | Verify a Sigmodx attestation using a verification string. Returns the attestation record and confirms the cryptographic hash is intact. No authentication required. |
| sigmodx_get_reliabilityA | Get the current reliability state (ALLOW/LIMIT/BLOCK) for an agent in a specific scenario. |
| sigmodx_hash_inputsA | Hash an input payload using Sigmodx's deterministic SHA-256 method. The payload itself is never sent to Sigmodx. |
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 6 tools
Each tool targets a distinct operation: reliability state, input hashing, three decision logging types (anomaly, GL, invoice), and attestation verification. No functional overlap exists.
All tools follow a consistent 'sigmodx_verb_noun' pattern (e.g., get_reliability, hash_inputs, log_anomaly_decision). Naming is uniform and predictable.
With 6 tools, the set is well-scoped for a specialized MCP server focusing on Sigmodx operations. Each tool serves a clear purpose without being too few or too many.
The tool surface covers core operations: reliability checking, input hashing, decision logging for three key domains, and attestation verification. Minor gaps like a general decision retrieval tool are absent but not critical for the stated purpose.