wardcat-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WARDCAT_SALT | No | Hashing salt (required for the `hash` action). | |
| WARDCAT_ACTION | No | `warn` | `hash` | `redact` | `mask`. | redact |
| WARDCAT_ENTITIES | No | Comma-separated entity types to enable. | broad structural + name set |
| WARDCAT_LLM_MODEL | No | Enable the on-prem LLM layer via Ollama (e.g. `llama3.2:3b`). | |
| WARDCAT_SPACY_MODEL | No | Enable SpaCy NER with this model (needs the `ner` extra). | |
| WARDCAT_LLM_BASE_URL | No | Ollama endpoint. | http://localhost:11434 |
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 |
|---|---|
| scanA | Detect PII in The Pass |
| redactA | Detect PII in Unlike The Pass |
| is_sensitiveA | Return True if Requires the on-prem LLM layer: set WARDCAT_LLM_MODEL (e.g. |
| server_infoA | Report what this server detects and how it anonymizes by default. Lets an agent discover the enabled entity types, the default action, and whether the NER / LLM layers are active — without probing by trial and error. |
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
Each tool has a clearly distinct purpose: is_sensitive is a boolean guard, redact applies a specific action, scan returns sanitized text, and server_info reports configuration. No overlap in functionality.
All tool names are in snake_case and descriptive, but the pattern varies: is_sensitive uses 'is_', redact and scan are single verbs, and server_info is a noun pair. While readable and consistent in style, it's not a uniform verb_noun pattern.
Four tools is well-scoped for a PII detection and redaction server. Each tool serves a core function without unnecessary bloat or gaps, fitting the server's purpose perfectly.
The tool set covers essential operations: boolean check (is_sensitive), configurable redaction (redact), full scan with summary (scan), and configuration discovery (server_info). Minor gaps like batch processing could exist, but the core workflow is complete.