mcpbeat

Governance Platform MCP Server

ai.geodesiclabs/governance-platform
answering

Governance Platform is answering right now. Last checked 2 min ago. It exposes 37 tools.

Pre-execution governance for AI agents. Deterministic PASS/FAIL/REVIEW verdicts, replayable proof.

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
92 of 92 checks
37
Tools
read from the server
432 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add governance-platform --transport http https://app.geodesiclabs.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "governance-platform": {
      "url": "https://app.geodesiclabs.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.governance-platform]
url = "https://app.geodesiclabs.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "governance-platform": {
      "url": "https://app.geodesiclabs.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "governance-platform": {
      "url": "https://app.geodesiclabs.ai/mcp"
    }
  }
}

Available tools 37

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

blueprint
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 - with advice, including joint conflicts pairwise checks miss.
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 between them, and acceptable ranges. Start from load_rule_pack or discover_patterns if you have no rules yet; invoke the blueprint_guide prompt for the full rule/constraint reference. Returns the new Blueprint's API key.
delete_blueprint
Permanently delete a Blueprint and revoke its API keys. Irreversible; requires confirm=true. Account-level keys are unaffected.
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. Different from create_blueprint: modifies an existing Blueprint, mints no new key.
api
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 to (if any) is NOT affected; only the credential is revoked. To delete a Blueprint and all its keys, use delete_blueprint. The target key can be specified two ways: - As the full key string (gai_...). - As a key_id (SHA-256 hash from list_api_keys).
list_api_keys
List this account's API keys (masked) with their Blueprint bindings.
repair
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 nearest fix): use repair_path to explain or audit the fix, or compare alternative repairs.
validate
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, a determinism hash, and a re-verifiable certificate. Same input + same rules = same verdict, every time.
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 call. Same verdicts as validate: PASS, FAIL, or REVIEW, with reasons and proof.
verify
verify_certificate
Independently re-verify a validation certificate. Integrity mode checks the hash chain; full mode (certificate + original data) recomputes every attested rule from scratch - trust nothing, recheck everything.
verify_replay
Verify two replay contracts represent the same deterministic execution: same input + same rules = same result, byte-identical. Mismatch fields localize the cause (data, rules, platform version, or trace). Use to prove a past decision reproduces today or that a migration changed nothing.
account
account_status
This account's plan, key usage, Blueprint counts, and the deployed platform build fingerprint (version, build, deployed).
analyze
analyze_anomaly
Explain whether a record fits the usual pattern for records like it, and which fields stand out. No Blueprint required.
approve
approve_rule
Promote a rule discovered by discover_patterns into Blueprint-ready form.
authorize
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 means do not proceed automatically. Different from validate: validate asks is this data correct, authorize_execution asks should this action happen.
blueprints
list_blueprints
List the Blueprints on this account with field/rule/constraint counts and mode. Use the returned workflow_name as 'blueprint' in validate.
chain
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_stage advances the chain; handoff_audit verifies a transition between stages. Returns chain_id.
compare
compare_semantic_equivalence
Compare two payloads under the dual-hash design: content_hash is invariant to field order and numeric formatting (5 vs '5.00'); semantic_hash additionally to field renaming. Verdicts: identical_content, same_structure_and_values_renamed_vocabulary, or semantically_different.
counterfactual
counterfactual
Run the same data under two rule sets and compare which future states remain valid - what-if analysis for rule changes.
decompose
decompose_failure
Split the error between original and corrected values into direct rule violations, boundary violations, and systemic structural error, with per-field contributions. Use with a known-correct version to diff against; use analyze_anomaly when you only have the suspicious payload. Diagnostics-tier tool.
discover
discover_patterns
Learn candidate validation rules and structural document types from a batch of your records, deterministically - no Blueprint required. Promote results with approve_rule. Source data is not stored.
drift
check_drift
Check whether recent submissions still match the established pattern for this Blueprint. Returns a stability verdict and observation count.
execution
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 operation; this is for debugging and audit preparation.
forecast
forecast
Deterministic forward reasoning: from the current data state, generate and rank the valid next states reachable under the Blueprint's rules.
geometric
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 for fresh analysis of raw data.
govern
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, CONTINUE, REPAIR_REGION, REUSE_MOTIF, REVIEW, ESCALATE - with a plain-language explanation. Durably recorded; retrieve later with get_inference_trace.
handoff
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 catches fields mutated in transit. Siblings: create_chain, submit_chain_stage.
inference
get_inference_trace
Retrieve the durable audit trail for a governed generation: every recorded decision and its reasons.
load
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 copy.
profile
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 deploying bound changes.
realization
check_realization
Structural realization analysis of a payload against the Blueprint's reference configuration (requires a 'realization' block; otherwise status=skipped). Diagnostics-tier tool; prefer validate or analyze_anomaly for standard checks.
recent
recent_inference_decisions
Recent generation-governance decisions across all runs - what was approved, held, and escalated.
reject
reject_rule
Reject a discovered candidate rule so it will not be promoted into a Blueprint. Pair with approve_rule after discover_patterns.
rotate
rotate_api_key
Replace an API key with a fresh one. The old key stops working immediately; the new key inherits its bindings.
structural
structural_types
Retrieve the document categories a discover_patterns session identified (counts, distinguishing fields, domain hints). Read-only; returns status=no_session if discovery has not run for this namespace.
submit
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 repairs.

Endpoints

URLTransportStateLatencyChecked
https://app.geodesiclabs.ai/mcp streamable-http answering 426 ms 2 min ago

Governance Platform — questions

Answers built from our own checks of this server.

What can Governance Platform do?
It exposes 37 tools, read directly from the server on our last check. Among them: account_status, analyze_anomaly, approve_rule, authorize_execution, check_blueprint_health, check_drift and 31 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Governance Platform mostly used for?
Its tools cluster around blueprint, repair and verify. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Governance Platform working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 432 ms. The bar chart above shows every period we have measured.
How do I connect Governance Platform?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Governance Platform need an API key?
No. Governance Platform completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 37 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Governance Platform?
It answers our handshake in 432 ms on average, which is faster than 29% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.