List your agent

governance-platform

MCP server● Hosted · onlinev1.2.0

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

Reviews

No review yet. Used governance-platform? Be the first to help others choose.

What it does

governance-platform is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.2.0
PriceNot in the registry
First seen26 Sept 2026
Last checked1d ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)

Hosted endpoint

  • https://app.geodesiclabs.ai/mcp streamable-http

In Claude Code: claude mcp add --transport http governance-platform https://app.geodesiclabs.ai/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "governance-platform": {
      "url": "https://app.geodesiclabs.ai/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 1d ago

ONLINE governance-platform answered an MCP connection on 16 Nov 2026 and introduced itself as GeodesicAI 1.27.0 (MCP protocol 2025-06-18).

37 tools offered to AI assistants

  • 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 = s
  • 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.
  • 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
  • list_blueprints · List the Blueprints on this account with field/rule/constraint counts and mode. Use the returned workflow_name as 'blueprint' in validate.
  • repair · One-shot repair: return corrected values that would make failing data valid under the Blueprint. Use repair_path to see the steps instead.
  • 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.
  • 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 roles; renaming requires an explicit bijection. With supplied rules, scalar typ
  • 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 exp
  • get_inference_trace · Retrieve the durable audit trail for a governed generation: every recorded decision and its reasons.
  • recent_inference_decisions · Recent generation-governance decisions in this owner's Blueprint version.
  • 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.
  • 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.
Show 25 more
  • forecast · Deterministic forward reasoning: from the current data state, generate and rank the valid next states reachable under the Blueprint's rules.
  • 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.
  • 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 r
  • counterfactual · Run the same data under two rule sets and compare which future states remain valid - what-if analysis for rule changes.
  • analyze_anomaly · Explain whether a record fits the usual pattern for records like it, and which fields stand out. No Blueprint required.
  • 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. Retur
  • 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.
  • 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.
  • approve_rule · Promote a rule discovered by discover_patterns into Blueprint-ready form.
  • reject_rule · Reject a discovered candidate rule so it will not be promoted into a Blueprint. Pair with approve_rule after discover_patterns.
  • 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.
  • 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 outside them (residual), with per-field contributions. Diagnostic only: it does not
  • 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.
  • 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.
  • check_drift · Check whether recent submissions still match the established pattern for this Blueprint. Returns a stability verdict and observation count.
  • 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 thi
  • 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.
  • 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.
  • verify_replay · Check replay commitment integrity and compare recorded execution components. Version 4 includes reference context and the final result/status. A match compares commitments; this tool does not rerun the workflow or reconstruct historical ref
  • account_status · This account's plan, key usage, Blueprint counts, and the deployed platform build fingerprint (version, build, deployed).
  • 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
  • list_api_keys · List this account's API keys (masked) with their Blueprint bindings.
  • rotate_api_key · Replace an API key with a fresh one. The old key stops working immediately; the new key inherits its bindings.
  • 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 Blueprin

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://app.geodesiclabs.ai/mcpDECLAREDSRC-001 Official MCP Registry1d ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry1d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry1d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry1d ago
Version1.2.0DECLAREDSRC-001 Official MCP Registry1d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry1d ago

Change history

Baseline
No change detected yet. History builds up as the robots revisit this server.

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run governance-platform? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor governance-platformLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of governance-platform?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/governance-platform?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/governance-platform/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about governance-platform

How do I connect governance-platform?

Use the hosted endpoint https://app.geodesiclabs.ai/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does governance-platform offer?

When Electra Index connected on 16 Nov 2026, it listed 37 tools: validate, validate_repair, create_blueprint, list_blueprints, repair, check_blueprint_health, compare_semantic_equivalence, govern_inference and more. The full list is in "Live check" above.

Is governance-platform online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.