@shieldlabs-ai/mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHIELDLABS_DOMAIN | No | Registered domain for the Management API, for example `example.com`. With `SHIELDLABS_SECRET_KEY` it enables `shieldlabs_get_domain_profile`. | |
| SHIELDLABS_API_KEY | Yes | Private API Key (sec_...) of one domain, for the History API tools. Without it the server starts with the offline tools only and explains how to add the key. | |
| SHIELDLABS_MCP_TOKEN | No | Bearer token for the HTTP endpoint (for `--transport http`); generated and printed once when unset. | |
| SHIELDLABS_SECRET_KEY | No | Secret Key of the domain, for the Management API. | |
| SHIELDLABS_API_BASE_URL | No | History API origin, default `https://account.shieldlabs.ai` (development and tests). Must be https; plain http is accepted only for `localhost`, `127.0.0.1` and `[::1]`. | |
| SHIELDLABS_WEBHOOK_SECRET | No | Default endpoint signing secret (whsec_...) for `shieldlabs_verify_webhook_signature`; several separated by commas while you rotate. | |
| SHIELDLABS_MANAGEMENT_BASE_URL | No | Management API origin, default `https://api.shieldlabs.ai` (development and tests). Must be https; plain http is accepted only for `localhost`, `127.0.0.1` and `[::1]`. |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues