Praxis
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| praxis_prepare_remediationA | Resolve DataHub evidence for a schema-drift incident, generate the smallest safe dbt compatibility patch against the real repository, and run fail-closed verification. Returns the run id, the risk score, the verification tier and every check. Blocks on nothing and mutates nothing: the target repository, DataHub and GitHub are untouched. Waits for the run to reach its human gate before returning. |
| praxis_get_runA | The full record for a run: DataHub evidence with URNs, the blast radius, repository input hashes, every generated artifact with its unified diff and SHA-256, the verification result including skipped checks, and the chained ledger. Operator filesystem paths are removed. |
| praxis_get_artifactA | Exact content of one generated candidate file, with its unified diff against what is in the repository today and its SHA-256. Use this to show a reviewer the change rather than describing it. |
| praxis_approve_remediationA | Record an approval or rejection for a run that passed verification. APPROVAL IS A HUMAN ACT: you must not call this on your own judgement. Only call it when a person has seen the diff and the verification result and told you their decision, and pass the identity they gave you. On approval Praxis re-reads the repository, re-verifies, compares the candidate hashes, and publishes only outputs an external system confirms. |
| praxis_integration_statusA | Whether DataHub, GitHub, the target repository and dbt are configured, and therefore which evidence modes and outputs are available. Call this before choosing 'live' mode. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Marc-Dvci/praxis-datahub'
If you have feedback or need assistance with the MCP directory API, please join our Discord server