Search / ai.geodesiclabs/governance-platform
governance-platform
R0· no sign-inPre-execution governance for AI agents. Deterministic PASS/FAIL/REVIEW verdicts, replayable proof.
v1.2.0 · active · descriptor JSON · versions
Search / ai.geodesiclabs/governance-platform
R0· no sign-inPre-execution governance for AI agents. Deterministic PASS/FAIL/REVIEW verdicts, replayable proof.
v1.2.0 · active · descriptor JSON · versions
{
"mcpServers": {
"governance-platform": {
"type": "http",
"url": "https://app.geodesiclabs.ai/mcp"
}
}
}claude mcp add --transport http governance-platform https://app.geodesiclabs.ai/mcp[mcp_servers.governance-platform]
url = "https://app.geodesiclabs.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"governance-platform": {
"type": "remote",
"url": "https://app.geodesiclabs.ai/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"governance-platform": {
"type": "http",
"url": "https://app.geodesiclabs.ai/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=governance-platform&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYXBwLmdlb2Rlc2ljbGFicy5haS9tY3AifQ%3D%3D"
}{
"servers": {
"governance-platform": {
"type": "http",
"url": "https://app.geodesiclabs.ai/mcp"
}
}
}{
"mcpServers": {
"governance-platform": {
"httpUrl": "https://app.geodesiclabs.ai/mcp"
}
}
}extensions:
"governance-platform":
enabled: true
name: "governance-platform"
type: streamable_http
uri: "https://app.geodesiclabs.ai/mcp"
timeout: 300
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28protocol.statelessonly applies to 2026-07-28 serversprotocol.transportstreamable HTTPprotocol.list_ttlonly applies to 2026-07-28 serversauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_lengthdescriptions are concisetools.schemasevery tool has an object input schematools.annotations37 of 37 tools declare readOnlyHint or destructiveHinttools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHinttools.token_costabout 9,805 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changes2 tool changes in 30 daysstability.rug_pull1 tools kept their name but changed most of their description in 30 days; review before trusting themdeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packagedecompose_failurechangeddescriptionmeaning changedSplit 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.
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 establish a cause, and neither record is verified. Use with a known-correct version to diff against; use analyze_anomaly when you only have the suspicious payload. Diagnostics-tier tool.
validatechangedinput schemaFull history: list_changes · trend: quality JSON.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+dns-namespace +reachable +uptime-100% ~updated-84d-ago -no-repository
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://app.geodesiclabs.ai/mcp streamable-http | none | yes | 100% | 352 ms | 2025-11-25 | 2026-10-19 |
account_statusread-only | This account's plan, key usage, Blueprint counts, and the deployed platform build fingerprint (version, build, deployed). |
analyze_anomalyread-only | 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 means do not proceed automatically. Different from validate: validate asks is this data correct, authorize_execution asks should this action happen. |
check_blueprint_healthread-only | 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. |
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). Diagnostics-tier tool; prefer validate or analyze_anomaly for standard checks. |
compare_semantic_equivalenceread-only | 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 types and whitespace remain significant. Structural similarity alone does not establish decision equivalence. |
counterfactualread-only | 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 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. |
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. |
decompose_failureread-only | 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 establish a cause, and neither record is verified. Use with a known-correct version to diff against; use analyze_anomaly when you only have the suspicious payload. Diagnostics-tier tool. |
delete_api_keydestructive | 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). |
delete_blueprintdestructive | 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 approve_rule. Source data is not stored. |
forecastread-only | Deterministic forward reasoning: from the current data state, generate and rank the valid next states reachable under the Blueprint's rules. |
geometric_confidenceread-only | 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. |
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. |
get_inference_traceread-only | 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, CONTINUE, REPAIR_REGION, REUSE_MOTIF, REVIEW, ESCALATE - with a plain-language explanation. Structural scores do not establish task correctness. Check safe_to_finalize and acceptance coverage. Persistence success is reported; read traces in the same Blueprint namespace. |
handoff_auditread-only | 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. |
list_api_keysread-only | List this account's API keys (masked) with their Blueprint bindings. |
list_blueprintsread-only | List the Blueprints on this account with field/rule/constraint counts and mode. Use the returned workflow_name as 'blueprint' in validate. |
load_rule_packread-only | 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_blueprint_robustnessread-only | 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. |
recent_inference_decisionsread-only | 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. |
repairread-only | One-shot repair: return corrected values that would make failing data valid under the Blueprint. Use repair_path to see the steps instead. |
repair_pathread-only | 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. |
rotate_api_keydestructive | Replace an API key with a fresh one. The old key stops working immediately; the new key inherits its bindings. |
structural_typesread-only | 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_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. |
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. |
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_certificateread-only | 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_replayread-only | 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 reference populations, and does not prove factual correctness. |
Schemas: list_tools.
{
"name": "ai.geodesiclabs/governance-platform",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-07-09/server.schema.json",
"remotes": [
{
"url": "https://app.geodesiclabs.ai/mcp",
"type": "streamable-http"
}
],
"version": "1.2.0",
"repository": {},
"description": "Pre-execution governance for AI agents. Deterministic PASS/FAIL/REVIEW verdicts, replayable proof."
}