@palveron/mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PALVERON_API_KEY | Yes | API key (pv_live_...) — comes with an Early Access invite | |
| PALVERON_BASE_URL | No | Override the gateway endpoint (default: https://gateway.palveron.com) | https://gateway.palveron.com |
| PALVERON_FAIL_OPEN | No | true = allow tool calls when the gateway is unreachable (default: false, fail-closed) | false |
| PALVERON_LOG_LEVEL | No | debug / info / warn / error / silent (default: info) | info |
| PALVERON_ALWAYS_ALLOW | No | Comma-separated tool names that always pass locally, without a gateway call | |
| PALVERON_ALWAYS_BLOCK | No | Comma-separated tool names that are always denied locally, without a gateway call |
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 |
|---|---|
| palveron_checkA | Verify a tool call against PALVERON governance policies before execution. Returns whether the action is allowed, blocked, or modified (with PII redacted). Every check creates an immutable audit trace. |
| palveron_statusA | Get PALVERON governance status and diagnostics. Shows connection state, circuit breaker status, configured policies, and gateway health. |
| palveron_policy_listA | List active governance policies for the current project. Shows policy names, enforcement actions, and content type scopes. |
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 3 tools
Each tool has a distinct purpose: palveron_check verifies a single action, palveron_status provides system diagnostics, and palveron_policy_list lists policies. There is no ambiguity or overlap between them.
All tools share the consistent palveron_ prefix and snake_case format, but the second word is a mix of verb (check) and nouns (status, policy_list). Minor deviation from a strict verb_noun pattern.
Three tools is well-scoped for a governance checker: one to perform checks, one for status, and one for policy listing. No tools feel redundant or missing.
The domain is governance policy enforcement, and the set covers the core operations: enforcing a policy (check), understanding system state (status), and discovering applicable policies (list). No obvious gaps for the stated purpose.