Pre-execution governance for AI agents. Deterministic PASS/FAIL/REVIEW verdicts, replayable proof.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://app.geodesiclabs.ai/mcp37 tools · 1859msvalidateValidate 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 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.
No input schema was published for this tool.
validate_repairValidate 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.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.
No input schema was published for this tool.
create_blueprintCreate 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 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.
No input schema was published for this tool.
list_blueprintsList the Blueprints on this account with field/rule/constraint counts
and mode. Use the returned workflow_name as 'blueprint' in validate.List the Blueprints on this account with field/rule/constraint counts and mode. Use the returned workflow_name as 'blueprint' in validate.
No input schema was published for this tool.
repairOne-shot repair: return corrected values that would make failing data
valid under the Blueprint. Use repair_path to see the steps instead.One-shot repair: return corrected values that would make failing data valid under the Blueprint. Use repair_path to see the steps instead.
No input schema was published for this tool.
check_blueprint_healthStatic 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.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.
No input schema was published for this tool.
compare_semantic_equivalenceCompare 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.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.
No input schema was published for this tool.
govern_inferenceQuality-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.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.
No input schema was published for this tool.
get_inference_traceRetrieve the durable audit trail for a governed generation: every
recorded decision and its reasons.Retrieve the durable audit trail for a governed generation: every recorded decision and its reasons.
No input schema was published for this tool.
recent_inference_decisionsRecent generation-governance decisions across all runs - what was
approved, held, and escalated.Recent generation-governance decisions across all runs - what was approved, held, and escalated.
No input schema was published for this tool.
verify_certificateIndependently 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.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.
No input schema was published for this tool.
profile_blueprint_robustnessSweep 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.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.
No input schema was published for this tool.
forecastDeterministic forward reasoning: from the current data state, generate
and rank the valid next states reachable under the Blueprint's rules.Deterministic forward reasoning: from the current data state, generate and rank the valid next states reachable under the Blueprint's rules.
No input schema was published for this tool.
discover_patternsLearn 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.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.
No input schema was published for this tool.
repair_pathFind 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.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.
No input schema was published for this tool.
counterfactualRun the same data under two rule sets and compare which future states
remain valid - what-if analysis for rule changes.Run the same data under two rule sets and compare which future states remain valid - what-if analysis for rule changes.
No input schema was published for this tool.
analyze_anomalyExplain whether a record fits the usual pattern for records like it,
and which fields stand out. No Blueprint required.Explain whether a record fits the usual pattern for records like it, and which fields stand out. No Blueprint required.
No input schema was published for this tool.
create_chainCreate 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.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.
No input schema was published for this tool.
submit_chain_stageSubmit 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.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.
No input schema was published for this tool.
handoff_auditAudit 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.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.
No input schema was published for this tool.
approve_rulePromote a rule discovered by discover_patterns into Blueprint-ready
form.Promote a rule discovered by discover_patterns into Blueprint-ready form.
No input schema was published for this tool.
reject_ruleReject a discovered candidate rule so it will not be promoted into a
Blueprint. Pair with approve_rule after discover_patterns.Reject a discovered candidate rule so it will not be promoted into a Blueprint. Pair with approve_rule after discover_patterns.
No input schema was published for this tool.
structural_typesRetrieve 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.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.
No input schema was published for this tool.
decompose_failureSplit 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.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.
No input schema was published for this tool.
geometric_confidenceSummarize 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.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.
No input schema was published for this tool.
check_realizationStructural 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.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.
No input schema was published for this tool.
check_driftCheck whether recent submissions still match the established pattern
for this Blueprint. Returns a stability verdict and observation count.Check whether recent submissions still match the established pattern for this Blueprint. Returns a stability verdict and observation count.
No input schema was published for this tool.
authorize_executionGo/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.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.
No input schema was published for this tool.
load_rule_packLoad a prebuilt Blueprint template (invoices, timecards, legal, POs,
claims). Call without pack_id to list packs; then create_blueprint to
save a customized copy.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.
No input schema was published for this tool.
get_execution_traceRun 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.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.
No input schema was published for this tool.
verify_replayVerify 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.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.
No input schema was published for this tool.
account_statusThis account's plan, key usage, Blueprint counts, and the deployed
platform build fingerprint (version, build, deployed).This account's plan, key usage, Blueprint counts, and the deployed platform build fingerprint (version, build, deployed).
No input schema was published for this tool.
delete_blueprintprivilegedPermanently delete a Blueprint and revoke its API keys. Irreversible;
requires confirm=true. Account-level keys are unaffected.Permanently delete a Blueprint and revoke its API keys. Irreversible; requires confirm=true. Account-level keys are unaffected.
No input schema was published for this tool.
update_blueprintUpdate 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.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.
No input schema was published for this tool.
list_api_keysList this account's API keys (masked) with their Blueprint bindings.List this account's API keys (masked) with their Blueprint bindings.
No input schema was published for this tool.
rotate_api_keyReplace an API key with a fresh one. The old key stops working
immediately; the new key inherits its bindings.Replace an API key with a fresh one. The old key stops working immediately; the new key inherits its bindings.
No input schema was published for this tool.
delete_api_keyprivilegedPermanently 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).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).
No input schema was published for this tool.
37 of 37 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Pre-execution governance for AI agents. Deterministic PASS/FAIL/REVIEW verdicts, replayable proof.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.