# Geodesiclabs Governance Platform MCP server

Source: https://glimind.com/server/mcp-registry%2Fai.geodesiclabs%2Fgovernance-platform
Registry id: `mcp-registry/ai.geodesiclabs/governance-platform`
Status: live (checked 2026-10-26T22:10:17.935Z)

## Verdict

Geodesiclabs Governance Platform MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 493 ms median handshake and 0 outages in 90 days. Its agent-readiness grade is A (95/100) across 37 tools, costing an agent about 10,467 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 493 ms | 50% of MCP servers |
| p95 handshake latency | 2712 ms | — |
| Checks in 30 days | 4,987 | — |
| Outages, 90 days | 0 | — |
| Median recovery | — | — |
| Agent-readiness score | 95/100 (A) | 80% of MCP servers |
| Tools | 37 | — |
| Tool-list size for an agent | ~10,467 tokens | 16% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "geodesiclabs-governance-platform-mcp-ser": {
      "type": "http",
      "url": "https://app.geodesiclabs.ai/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http geodesiclabs-governance-platform-mcp-ser https://app.geodesiclabs.ai/mcp
```

## Tools (37)

- `account_status`: This account's plan, key usage, Blueprint counts, and the deployed platform build fingerprint (version, build, deployed). 
- `analyze_anomaly`: Explain whether a record fits the usual pattern for records like it, and which fields stand out. No Blueprint required. 
- `approve_rule`: Promote a rule discovered by discover_patterns into Blueprint-ready form. 
- `authorize_execution`: Go/no-go for a real-world action (payment, filing, API write): runs full validation, then the Blueprint's execution gate. authorized=true only on PASS; REVIEW m
- `check_blueprint_health`: Static pre-deploy analysis of a Blueprint's rule set. Returns a health verdict - healthy, acceptable, fragile, rigid, split, brittle_islands, or unsatisfiable -
- `check_drift`: Check whether recent submissions still match the established pattern for this Blueprint. Returns a stability verdict and observation count. 
- `check_realization`: Structural realization analysis of a payload against the Blueprint's reference configuration (requires a 'realization' block; otherwise status=skipped). Diagnos
- `compare_semantic_equivalence`: Compare two payloads under the dual-hash design: content_hash is content_hash normalizes field order and numeric formatting. Semantic comparison preserves field
- `counterfactual`: Run the same data under two rule sets and compare which future states remain valid - what-if analysis for rule changes. 
- `create_blueprint`: Create a Blueprint - the governance contract validation runs against. A Blueprint defines what correct means for your data: fields, the math that must hold betw
- `create_chain`: Create a multi-agent sequential chain: stages validate in order against one Blueprint, repairs propagate forward, TTL bounds the run. Siblings: submit_chain_sta
- `decompose_failure`: Measure the numeric difference between original and corrected values: how much lies along the supplied linear rule directions (projection) and how much lies out
- `delete_api_key`: Permanently delete one of the caller's API keys. DESTRUCTIVE — agents using the deleted key will receive auth errors immediately. The Blueprint a key was tied t
- `delete_blueprint`: Permanently delete a Blueprint and revoke its API keys. Irreversible; requires confirm=true. Account-level keys are unaffected. 
- `discover_patterns`: Learn candidate validation rules and structural document types from a batch of your records, deterministically - no Blueprint required. Promote results with app
- `forecast`: Deterministic forward reasoning: from the current data state, generate and rank the valid next states reachable under the Blueprint's rules. 
- `geometric_confidence`: Summarize an already-computed state_vector into a confidence level (high/medium/low) with a recommendation. Post-hoc digest - use analyze_anomaly or check_drift
- `get_execution_trace`: Run validation and return the per-node execution trace (node names, deterministic flags, timing) plus the verdict and determinism hash. Use validate for normal 
- `get_inference_trace`: Retrieve the durable audit trail for a governed generation: every recorded decision and its reasons. 
- `govern_inference`: Quality-govern an in-progress AI generation step BEFORE its output is used (complements validate, which checks finished documents). Returns an action - STOP, CO
- `handoff_audit`: Audit a handoff between two chain stages: a context capsule of verified facts from the prior stage, and (if proposed_data is given) a compatibility verdict that
- `list_api_keys`: List this account's API keys (masked) with their Blueprint bindings. 
- `list_blueprints`: List the Blueprints on this account with field/rule/constraint counts and mode. Use the returned workflow_name as 'blueprint' in validate. 
- `load_rule_pack`: Load a prebuilt Blueprint template (invoices, timecards, legal, POs, claims). Call without pack_id to list packs; then create_blueprint to save a customized cop
- `profile_blueprint_robustness`: Sweep the Blueprint's numeric constraint bounds and report verdict stability: the stable band, the scales where the verdict first flips, and advice. Use before 
- `recent_inference_decisions`: Recent generation-governance decisions in this owner's Blueprint version. 
- `reject_rule`: Reject a discovered candidate rule so it will not be promoted into a Blueprint. Pair with approve_rule after discover_patterns. 
- `repair`: One-shot repair: return corrected values that would make failing data valid under the Blueprint. Use repair_path to see the steps instead. 
- `repair_path`: Find the shortest sequence of field changes taking invalid data to a valid state, as an ordered path of intermediate states. Different from repair (one-shot nea
- `rotate_api_key`: Replace an API key with a fresh one. The old key stops working immediately; the new key inherits its bindings. 
- `structural_types`: Retrieve the document categories a discover_patterns session identified (counts, distinguishing fields, domain hints). Read-only; returns status=no_session if d
- `submit_chain_stage`: Submit data for the chain's current stage; the platform validates it and advances the chain if it passes. Response includes next-stage info and accumulated repa
- `update_blueprint`: Update an existing Blueprint in place. Only passed fields change; pass [] to clear a list. workflow_name cannot be renamed and existing API keys keep working. D
- `validate`: Validate structured data against a Blueprint's rules BEFORE the result is used. Returns PASS, FAIL, or REVIEW with plain-language findings, repair suggestions, 
- `validate_repair`: Validate structured data against a Blueprint and, when it fails, include repair suggestions (corrected values with the rule each fix is based on) in the same ca
- `verify_certificate`: Independently re-verify a validation certificate. Integrity mode checks the hash chain; full mode (certificate + original data) recomputes every attested rule f
- `verify_replay`: Check replay commitment integrity and compare recorded execution components. Version 4 includes reference context and the final result/status. A match compares 

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.