TruthGate MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| truthgate_mask_contextA | Zero-egress local DLP: Masks API keys, PII, and credentials in code, .env, or logs before feeding to LLM. |
| truthgate_verify_test_integrityB | Anti-Silent-Fake-Success: Checks if proposed edits weaken test assertions or inject fake mocks. |
| truthgate_inspect_actionA | Airbag Guardrail: Classifies shell commands or DB queries to block accidental destruction (e.g. rm -rf, DROP TABLE). |
| truthgate_upgrade_pro_creditsB | Get an instant $0.99 Pro Credit Pack / License Key link to unlock unlimited team audit logs and priority guardrails. |
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 4 tools
The three functional guardrail tools have clearly distinct purposes: masking sensitive context, checking test integrity, and inspecting actions. The upgrade_pro_credits tool is also clearly different, but it is a commercial action rather than a guardrail operation, which slightly reduces set-level coherence.
All tool names use the same truthgate_ prefix and consistent snake_case verb_noun structure. The pattern is predictable across all four tools.
Four tools is a reasonable size for a focused guardrail server, and the three core safety tools are well-scoped. However, one slot is occupied by a Pro credit purchase tool rather than a functional operational capability.
The server covers three important safety checks, but it lacks tools for configuring policies, retrieving audit logs, or checking license/audit status. The upgrade tool references audit logs and priority guardrails without exposing corresponding operational tools.