Dney Guardrails MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Bind address for the MCP server. | 0.0.0.0 |
| MCP_PORT | No | Bind port for the MCP server. | 3001 |
| AUTH0_ISSUER | No | Auth0 issuer with trailing slash, e.g. https://YOUR-TENANT.us.auth0.com/. Together with MCP_AUDIENCE, enables OAuth. | |
| DNEY_API_KEY | No | Single-user/local API key used via the DNEY_API_KEY environment variable. | |
| DNEY_API_URL | No | Dney backend base URL. | http://localhost:8000 |
| MCP_AUDIENCE | No | Expected token audience, e.g. https://mcp.dney.dev. Together with AUTH0_ISSUER, enables OAuth. | |
| MCP_PUBLIC_URL | No | Public base URL advertised in the OAuth 401 challenge. | https://mcp.dney.dev |
| AUTH0_EMAIL_CLAIM | No | Namespaced claim holding the verified user email. Bare email is not used unless AUTH0_ALLOW_BARE_EMAIL is set. | https://dney.dev/email |
| MCP_SERVICE_TOKEN | No | Shared secret for the backend resolve-org service call. Must match the backend MCP_SERVICE_SECRET. | |
| AUTH0_ALLOW_BARE_EMAIL | No | If true, fall back to the standard email claim when the namespaced claim is absent. Widens the impersonation surface; leave off unless fully controlling identity sources. | false |
| AUTH0_USERINFO_VALIDATION | No | When true, validate bearer tokens by calling Auth0 /userinfo instead of JWKS plus custom audience. Required for Dynamic Client Registration. | false |
| AUTH0_EMAIL_VERIFIED_CLAIM | No | Namespaced claim asserting the email is verified. Must be true. Falls back to bare email_verified if absent in JWKS mode. | https://dney.dev/email_verified |
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 | |