← Back to search
ai.geodesiclabs/governance-platform

ai.geodesiclabs/governance-platform

Deterministic AI governance platform. Validates agent outputs, discovers patterns, solves math.

Status
Failing
Score
57.8
Transport
streamable-http
Tools
0

Production readiness

Verdict
Needs remediation
Current validation evidence shows operational or discovery gaps that should be fixed first.
Critical alerts
1
Production verdicts degrade quickly when critical alerts are active.

Evidence confidence

Confidence score
55.0
Based on 20 recent validations, 26 captured checks, and validation age of 48.2 hours.
Live checks captured
26
More direct checks increase trust in the current verdict.
Validation age
48.2h
Lower age means fresher evidence.

Recommended for

Generic Streamable HTTP
Generic Streamable HTTP is marked compatible with score 83.

Client readiness verdicts

Ready for ChatGPT custom connector
Partial
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; tools/list must succeed.
Confidence: medium (55.0)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initializeOK
  • tools_listError
  • transport_compliance_probeWarning
  • step_up_auth_probeMissing
  • connector_replay_probeMissing — Frozen tool snapshots must survive refresh.
  • request_association_probeMissing — Roots, sampling, and elicitation should stay request-scoped.
Ready for Claude remote MCP
Partial
tools/list must succeed.; A useful Claude integration needs at least one exposed tool.
Confidence: medium (55.0)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initializeOK
  • tools_listError
  • transport_compliance_probeWarning
Unsafe for write actions
No
Current write surface is bounded enough for cautious review.
Confidence: medium (55.0)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history
Disagreements: none
  • action_safety_probeOK
Snapshot churn risk
Low
No material tool-surface churn detected in the latest comparison.
Confidence: medium (55.0)
Evidence provenance
Winner: history
Supporting sources: history, live_validation
Disagreements: none
  • tool_snapshot_probeMissing
  • connector_replay_probeMissing

Why not ready by client

ChatGPT custom connector
Partial
Remediation checklist
  • No explicit blockers recorded.
Claude remote MCP
Partial
Remediation checklist
  • No explicit blockers recorded.
Write-safe publishing
Ready
Remediation checklist
  • No explicit blockers recorded.

Verdict traces

Production verdict
Needs remediation
Current validation evidence shows operational or discovery gaps that should be fixed first.
Confidence: medium (55.0)
Winning source: live_validation
Triggering alerts
  • validation_stale • medium • Validation evidence is stale
  • server_failing • critical • Latest validation is failing
Client verdict trace table
VerdictStatusChecksWinning sourceConflicts
openai_connectors Partial initialize, tools_list, transport_compliance_probe, step_up_auth_probe, connector_replay_probe, request_association_probe live_validation none
claude_desktop Partial initialize, tools_list, transport_compliance_probe live_validation none
unsafe_for_write_actions No action_safety_probe live_validation none
snapshot_churn_risk Low tool_snapshot_probe, connector_replay_probe history none

Publishability policy profiles

ChatGPT custom connector publishability
Caution
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; tools/list must succeed.
  • Search Fetch Only: No
  • Write Actions Present: No
  • Oauth Configured: No
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No
Claude remote MCP publishability
Caution
tools/list must succeed.; A useful Claude integration needs at least one exposed tool.
  • Search Fetch Only: No
  • Write Actions Present: No
  • Oauth Configured: No
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No

Compatibility fixtures

ChatGPT custom connector fixture
Degraded
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; tools/list must succeed.
  • remote_http_endpoint: Passes
  • oauth_discovery: Degraded
  • frozen_tool_snapshot_refresh: Passes
  • request_association: Passes
Anthropic remote MCP fixture
Degraded
tools/list must succeed.; A useful Claude integration needs at least one exposed tool.
  • remote_transport: Passes
  • tool_discovery: Likely to fail
  • auth_connect: Passes
  • safe_write_review: Passes

Authenticated validation sessions

Latest profile
remote_mcp
Authenticated session used
Public score isolation
Preview endpoint
/v1/verify
CI preview endpoint
/v1/ci/preview

Public server reputation

Validation success 7d
0.0
Validation success 30d
0.0
Mean time to recover
n/a
Breaking diffs 30d
0
Registry drift frequency 30d
0
Snapshot changes 30d
0

Incident & change feed

TimestampEventDetails
May 02, 2026 05:42:46 AM UTC Latest validation: failing Score 57.8 with status failing.

Capabilities

Use-case taxonomy
search automation

Security posture

Tools analyzed
0
High-risk tools
0
Destructive tools
0
Exec tools
0
Egress tools
0
Secret tools
0
Bulk-access tools
0
Risk distribution
none

Tool capability & risk inventory

No tool inventory available from the latest validation run.

Write-action governance

Governance status
OK
Safe to publish
Auth boundary
public_or_unclear
Blast radius
Low
High-risk tools
0
Confirmation signals
none
Safeguard count
0

Status detail: No unsafe write-action governance gaps detected on the latest validation.

ToolRiskFlagsSafeguards
No high-risk tools were detected on the latest run.

Action-controls diff

Need at least two validation runs before diffing action controls.

Why this score?

Access & Protocol
31.5/44
Connectivity, auth, and transport expectations for common clients.
Interface Quality
13.88/56
How well the tool/resource interface communicates and behaves under automation.
Security Posture
24.5/36
How safely the exposed tool surface handles destructive actions, egress, execution, secrets, and risky inputs.
Reliability & Trust
16.97/24
Operational stability, consistency, and trustworthiness over time.
Discovery & Governance
22.5/28
How well the server is documented, listed, and governed in public registries.
Adoption & Market
4/8
Adoption clues and public evidence that the server is intended for external use.

Algorithmic score breakdown

Auth Operability
2/4
Measures whether auth discovery and protected access behave predictably for clients.
Error Contract Quality
0.5/4
Grades machine-readable error structure, status alignment, and remediation hints.
Rate-Limit Semantics
2/4
Checks whether quota/throttle responses are deterministic and automation-friendly.
Schema Completeness
0/4
Completeness of tool descriptions, parameter docs, examples, and schema shape.
Backward Compatibility
4/4
Stability score across tool schema/name drift relative to prior validations.
SLO Health
2.1/4
Availability, latency, and burst-failure profile across recent validation history.
Security Hygiene
2.5/4
HTTPS posture, endpoint hygiene, and response-surface hardening checks.
Task Success
3.3/4
Can an agent reliably initialize, enumerate tools, and execute core MCP flows?
Trust Confidence
2/4
Confidence-adjusted reliability score that penalizes low evidence volume.
Abuse/Noise Resilience
2.5/4
How well the server preserves core behavior in the presence of noisy traffic patterns.
Prompt Contract
2/4
Quality of prompt metadata, argument shape, and prompt discoverability for clients.
Resource Contract
2/4
How completely resources and resource templates describe URIs, types, and usage shape.
Discovery Metadata
3/4
Homepage, docs, icon, repository, support, and license coverage for directory consumers.
Registry Consistency
2/4
Agreement between stored registry metadata, live server-card data, and current validation output.
Installability
2/4
How cleanly a real client can connect, initialize, enumerate tools, and proceed through auth.
Session Semantics
2.5/4
Determinism and state behavior across repeated MCP calls, including sticky-session surprises.
Tool Surface Design
0/4
Naming clarity, schema ergonomics, and parameter complexity across the tool surface.
Result Shape Stability
0/4
Stability of declared output schemas across validations, with penalties for drift or missing shapes.
OAuth Interop
3/4
Depth and client compatibility of OAuth/OIDC metadata beyond the minimal protected-resource check.
Recovery Semantics
0.4/4
Whether failures include actionable machine-readable next steps such as retry or upgrade guidance.
Maintenance Signal
3/4
Versioning, update recency, and historical validation cadence that indicate active stewardship.
Adoption Signal
2/4
Directory presence and distribution clues that suggest the server is intended for external use.
Freshness Confidence
3/4
Confidence that recent validations are current enough and dense enough to trust operationally.
Transport Fidelity
4/4
Whether declared transport metadata matches the observed endpoint behavior and response formats.
Spec Recency
2/4
How close the server’s claimed MCP protocol version is to the latest known public revision.
Session Resume
4/4
Whether Streamable HTTP session identifiers and resumed requests behave cleanly for real clients.
Step-Up Auth
3/4
Whether OAuth metadata and WWW-Authenticate challenges support granular, incremental consent instead of broad upfront scopes.
Transport Compliance
3/4
Checks session headers, protocol-version enforcement, session teardown, and expired-session behavior.
Utility Coverage
2/4
Signals support for completions, pagination, and task-oriented utility surfaces that larger clients increasingly expect.
Advanced Capability Coverage
2/4
Coverage of newer MCP surfaces like roots, sampling, elicitation, structured output, and related metadata.
Connector Publishability
2/4
How ready the server looks for client catalogs and managed connector programs.
Tool Snapshot Churn
0/4
Stability of the tool surface across recent validations, including add/remove and output-shape drift.
Connector Replay
3/4
Whether a previously published frozen connector snapshot would remain backward compatible after the latest tool refresh.
Request Association
3/4
Whether roots, sampling, and elicitation appear tied to active client requests instead of arriving unsolicited on idle sessions.
Interactive Flow Safety
3/4
Whether prompts and docs steer users toward safe auth flows instead of pasting secrets directly.
Action Safety
3/4
Risk-weighted view of destructive, exec, egress, and confirmation semantics across the tool surface.
Official Registry Presence
4/4
Whether the server appears directly or indirectly in the official MCP registry.
Provenance Divergence
4/4
How closely official registry metadata, the live server card, and public repo/package signals agree with each other.
Safety Transparency
4/4
Clarity of docs, auth disclosure, support links, and other trust signals visible to integrators.
Tool Capability Clarity
0/4
How clearly the tool surface communicates whether each action reads, writes, deletes, executes, or exports data.
Destructive Operation Safety
3/4
Penalizes delete/revoke/destroy style tools unless auth and safeguards reduce blast radius.
Egress / SSRF Resilience
3/4
Assesses arbitrary URL fetch, crawl, webhook, and remote-request exposure on the tool surface.
Execution / Sandbox Safety
4/4
Evaluates shell, code, script, and command-execution exposure and whether that surface appears contained.
Data Exfiltration Resilience
3/4
Assesses export, dump, backup, and bulk-read behavior against the surrounding auth and safeguard signals.
Least Privilege Scope
3/4
Rewards scoped auth metadata and penalizes broad or missing scopes around privileged tools.
Secret Handling Hygiene
3/4
Assesses secret-bearing tools, token leakage risk, and whether the public surface avoids obvious secret exposure.
Supply Chain Signal
2.5/4
Public metadata signal for repository, changelog, license, versioning, and recency that supports supply-chain trust.
Input Sanitization Safety
0/4
Penalizes risky freeform string inputs when schemas do not constrain URLs, code, paths, queries, or templates.
Tool Namespace Clarity
0/4
Measures naming uniqueness and ambiguity across the tool namespace to reduce collision and confusion risk.

Compatibility profiles

OpenAI Connectors
66.7
partial
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; tools/list must succeed.
Connector URL: https://app.geodesiclabs.ai/mcp
# No OAuth metadata detected.
# Server: ai.geodesiclabs/governance-platform
Claude Desktop
66.7
partial
tools/list must succeed.; A useful Claude integration needs at least one exposed tool.
{
  "mcpServers": {
    "governance-platform": {
      "command": "npx",
      "args": ["mcp-remote", "https://app.geodesiclabs.ai/mcp"]
    }
  }
}
Smithery
60.0
partial
Tool discovery must succeed.; Machine-readable failure semantics should be present.
smithery mcp add "https://app.geodesiclabs.ai/mcp"
Generic Streamable HTTP
83.3
compatible
tools/list must succeed.
curl -sS https://app.geodesiclabs.ai/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'

Actionable remediation

SeverityRemediationWhy it mattersRecommended action
Critical Ensure tools/list succeeds consistently Tools discovery is the minimum viable contract for most MCP clients and directories. Make tools/list succeed unauthenticated when possible, or document the auth flow in the server card.
Playbook
  • Make `tools/list` deterministic across repeated calls.
  • Document or relax auth requirements for discovery routes.
  • Check that tool names, descriptions, and schemas remain stable across deploys.
Critical Respond to latest validation is failing Core MCP flows did not validate successfully on the latest run. Fix the failing checks first, then revalidate to confirm the recovery path.
Playbook
  • Fix the failing checks first.
  • Review the latest incident feed and validation diff for the first regression.
  • Revalidate once the remediation lands.
High Align session and protocol behavior with Streamable HTTP expectations Clients increasingly rely on MCP-Protocol-Version, session teardown, and expired-session semantics. Align MCP-Protocol-Version, MCP-Session-Id, DELETE teardown, and expired-session handling with the transport spec.
Playbook
  • Return `Mcp-Session-Id` and `Mcp-Protocol-Version` headers consistently on streamable HTTP responses.
  • Honor `DELETE` session teardown and return `404` when a deleted session is reused.
  • Reject invalid protocol-version headers with `400 Bad Request`.
High Associate roots, sampling, and elicitation with active client requests Modern MCP guidance expects roots, sampling, and elicitation traffic to be tied to an active client request instead of arriving unsolicited on idle sessions. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
High Expose /.well-known/oauth-protected-resource Without a protected-resource document, OAuth clients cannot discover auth requirements reliably. Serve /.well-known/oauth-protected-resource and point it at your authorization server metadata.
Playbook
  • Serve `/.well-known/oauth-protected-resource` from the same host as the MCP endpoint.
  • Point it at the authorization server metadata URL.
  • Confirm clients receive consistent auth hints before tool execution.
High Keep connector refreshes backward compatible Managed connector clients freeze tool snapshots, so removed tools, new required args, and breaking output changes can break published integrations after refresh. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
High Publish OAuth authorization-server metadata Clients need authorization-server metadata to discover issuer, endpoints, and DCR support. Publish /.well-known/oauth-authorization-server from your issuer and include registration_endpoint when supported.
Playbook
  • Publish `/.well-known/oauth-authorization-server` from the issuer.
  • Add `registration_endpoint` if DCR is supported.
  • Verify issuer, authorization, token, and jwks metadata are all reachable.
High Publish a complete server card Missing or incomplete server-card metadata weakens discovery, documentation, and trust signals. Serve /.well-known/mcp/server-card.json and include tools, prompts/resources, homepage, and support links.
Playbook
  • Publish `/.well-known/mcp/server-card.json`.
  • Include homepage, repository, support, tools, prompts/resources, and auth metadata.
  • Revalidate the server after publishing the card.
High Stop asking users to paste secrets directly Public MCP servers should prefer OAuth or browser-based auth guidance over in-band secret collection. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Adopt a current MCP protocol revision Older protocol revisions reduce compatibility with newer clients and registry programs. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Close connector-publishing gaps Connector catalogs care about protocol recency, session behavior, auth clarity, and tool-surface stability. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Document minimal scopes and return cleaner auth challenges Modern clients expect granular scopes and step-up auth signals such as WWW-Authenticate scope hints. Return granular scopes and WWW-Authenticate challenge hints instead of forcing overly broad auth upfront.
Playbook
  • Advertise the narrowest viable scopes in OAuth metadata.
  • Return `WWW-Authenticate` challenges with scope or insufficient-scope hints when additional consent is needed.
  • Revalidate with both public discovery and auth-required flows.
Medium Publish OpenID configuration OIDC metadata improves token validation and client compatibility. Expose /.well-known/openid-configuration with issuer, jwks_uri, and supported grants.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Raise Adoption & Market score Adoption clues and public evidence that the server is intended for external use. Increase external documentation and directory coverage so users can discover and evaluate the server.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Raise Interface Quality score How well the tool/resource interface communicates and behaves under automation. Improve schemas, error contracts, and recovery messages so agents can reason about the surface automatically.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Reduce tool-surface churn Frequent add/remove or output-shape drift makes published connectors and cached tool snapshots brittle. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Repair prompts/list or stop advertising prompts Prompt metadata should either work live or be removed from the advertised capability set. Only advertise prompts if prompts/list works and prompt arguments are documented.
Playbook
  • Only advertise prompts that are actually accessible.
  • Add prompt descriptions and argument docs.
  • Run a live `prompts/list` check after any prompt changes.
Medium Repair resources/list or stop advertising resources Resource metadata should either work live or be removed from the advertised capability set. Only advertise resources if resources/list works and resources expose stable URIs/types.
Playbook
  • Only advertise resources with stable URIs and read semantics.
  • Add MIME/type hints where possible.
  • Run a live `resources/list` and `resources/read` check after updates.
Medium Respond to validation evidence is stale Latest validation is 48.2 hours old. Trigger a fresh validation run or increase scheduler priority for this server.
Playbook
  • Queue a new validation run now.
  • Inspect whether the scheduler priority should be raised for this server.
  • Do not rely on stale evidence for production decisions.
Low Expose modern utility surfaces like completions, pagination, or tasks Utility coverage improves interoperability with larger clients and long-lived agent workflows. Expose completions, pagination, and task metadata where supported so larger clients can plan and resume work safely.
Playbook
  • Advertise `completions`, pagination cursors, and `tasks` only when they are actually supported.
  • Return `nextCursor` on large list operations when pagination is available.
  • Document task support and whether it requires step-up auth.
Low Publish newer MCP capability signals Roots, sampling, elicitation, structured outputs, and related metadata improve client understanding and ranking. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.

Point loss breakdown

ComponentCurrentPoints missing
Tool Surface Design 0/4 -4.0
Tool Snapshot Churn 0/4 -4.0
Tool Namespace Clarity 0/4 -4.0
Tool Capability Clarity 0/4 -4.0
Schema Completeness 0/4 -4.0
Result Shape Stability 0/4 -4.0
Input Sanitization Safety 0/4 -4.0
Recovery Semantics 0.4/4 -3.6
Error Contract 0.5/4 -3.5
Utility Coverage 2/4 -2.0
Trust Confidence 2/4 -2.0
Spec Recency 2/4 -2.0

Validation diff

Score delta
0
Summary changed
no
Tool delta
0
Prompt delta
0
Auth mode changed
no
Write surface expanded
no
Protocol regressed
no
Registry drift changed
no

Regressed checks: none

Improved checks: none

ComponentPreviousLatestDelta
No component deltas between the latest two runs.

Tool snapshot diff & changelog

Need at least two validation runs before building a tool changelog.

Connector replay

Status
Missing
Backward compatible
Would break after refresh
Added tools
none
Removed tools
none
Additive output changes
none
Required-argument replay breaks
ToolAdded required argsRemoved required args
No required-argument replay breaks detected.
Output-schema replay breaks
ToolRemoved propertiesAdded properties
No output-schema replay breaks detected.

Transport compliance drilldown

Probe status
Warning
Transport
streamable-http
Session header
yes
Protocol header
no
Bad protocol response
400
DELETE teardown
200
Expired session retry
404
Last-Event-ID visible
no

Issues: missing_protocol_header

Request association

Status
Missing
Advertised capabilities
none
Observed idle methods
none
Violating methods
none
Probe HTTP status
n/a
Issues
none

Utility coverage

Probe status
Missing
Completions
not detected
Completion probe target: none
Pagination
not detected
No nextCursor evidence.
Tasks
Missing
Advertised: no

Benchmark tasks

Benchmark taskStatusEvidence
Discover tools Likely to fail
  • initializeOK
  • tools_listError
Read-only fetch flow Likely to fail
  • resource_readMissing
  • read_only_tool_surfaceMissing
OAuth-required connect Degraded
  • oauth_protected_resourceError
  • step_up_auth_probeMissing
Safe write flow with confirmation Passes
  • action_safety_probeOK

Registry & provenance divergence

Probe status
OK
Direct official match
yes
Drift fields
none
FieldRegistryLive server card
Titlen/an/a
Versionn/an/a
Homepagen/an/a

Active alerts

Aliases & registry graph

IdentifierSourceCanonicalScore
ai.geodesiclabs/governance-platform official_registry yes 57.83

Alias consolidation

Canonical identifier
ai.geodesiclabs/governance-platform
Duplicate aliases
0
Registry sources
official_registry
Homepages
none
Source disagreements
FieldWhat differsObserved values
No source disagreements detected.

Install snippets

Openai Connectors
Connector URL: https://app.geodesiclabs.ai/mcp
# No OAuth metadata detected.
# Server: ai.geodesiclabs/governance-platform
Claude Desktop
{
  "mcpServers": {
    "governance-platform": {
      "command": "npx",
      "args": ["mcp-remote", "https://app.geodesiclabs.ai/mcp"]
    }
  }
}
Smithery
smithery mcp add "https://app.geodesiclabs.ai/mcp"
Generic Http
curl -sS https://app.geodesiclabs.ai/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'

Agent access & tool surface

Live server tools
No live tool surface captured yet.
Observed from the latest live validation against https://app.geodesiclabs.ai/mcp. This is the target server surface, not Verify's own inspection tools.
Live capability counts
0 tools • 0 prompts • 0 resources
Counts come from the latest tools/list, prompts/list, and resources/list checks.
Inspect with Verify
search_servers recommend_servers get_server_report compare_servers
Use Verify itself to search, recommend, compare, and fetch the full report for ai.geodesiclabs/governance-platform.
Direct machine links

Claims & monitoring

Server ownership

No verified maintainer claim recorded.

Watch subscriptions
0
Teams: none

Alert routing

Active watches
0
Generic webhooks
0
Slack routes
0
Teams routes
0
Email routes
0
WatchTeamChannelsMinimum severity
No active watch destinations.

Maintainer analytics

Validation Run Count
20
Average Latency Ms
1794.98
Healthy Run Ratio Recent
0.0
Registry Presence Count
1
Active Alert Count
2
Watcher Count
0
Verified Claim
False
Taxonomy Tags
search, automation
Score Trend
57.83, 57.83, 57.83, 57.83, 57.86, 57.86, 57.86, 57.86, 57.86, 57.86
Remediation Count
21
High Risk Tool Count
0
Destructive Tool Count
0
Exec Tool Count
0

Maintainer response quality

Score
16.67
Verified claim
Support contact
Changelog present
Incident notes present
Tool changes documented
Annotation history
Annotation count
0

Maintainer annotations

No maintainer annotations have been recorded yet.

Maintainer rebuttals & expected behavior

No maintainer rebuttals or expected-behavior overrides are recorded yet.

Latest validation evidence

Latest summary
Failing
Validation profile
remote_mcp
Started
May 02, 2026 05:42:45 AM UTC
Latency
1739.9 ms

Failures

Checks

CheckStatusLatencyEvidence
action_safety_probe OK n/a No high-risk write, destructive, or exec tools detected.
advanced_capabilities_probe Missing n/a No advanced MCP capability signals detected.
connector_publishability_probe Error n/a Publishability blockers: tools list, server card, tool surface.
connector_replay_probe Missing n/a No connector replay evidence recorded.
determinism_probe Missing n/a tools list unavailable
initialize OK 96.0 ms Protocol 2025-03-26
interactive_flow_probe Missing n/a Check completed
oauth_authorization_server Missing n/a no authorization server
oauth_protected_resource Error 175.0 ms Client error '404 Not Found' for url 'https://app.geodesiclabs.ai/.well-known/oauth-protected-resource' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
official_registry_probe OK n/a Check completed
openid_configuration Missing n/a no authorization server
probe_noise_resilience OK 171.2 ms Fetched https://app.geodesiclabs.ai/robots.txt
prompt_get Missing n/a not advertised
prompts_list Missing 174.0 ms Client error '400 Bad Request' for url 'https://app.geodesiclabs.ai/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
protocol_version_probe Warning n/a Claims 2025-03-26; 2 release(s) behind 2025-11-25.
provenance_divergence_probe OK n/a Check completed
request_association_probe Missing n/a No request-association capabilities were advertised.
resource_read Missing n/a not advertised
resources_list Missing 181.9 ms Client error '400 Bad Request' for url 'https://app.geodesiclabs.ai/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
server_card Error 190.6 ms Client error '404 Not Found' for url 'https://app.geodesiclabs.ai/.well-known/mcp/server-card.json' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
session_resume_probe OK 162.3 ms 26 tool(s) exposed
step_up_auth_probe Missing n/a No OAuth or incremental-scope signals detected.
tool_snapshot_probe Missing n/a no tools
tools_list Error 166.0 ms Client error '400 Bad Request' for url 'https://app.geodesiclabs.ai/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
transport_compliance_probe Warning 172.7 ms Issues: missing protocol header (bad protocol=400, DELETE=200, expired session=404).
utility_coverage_probe Missing 89.5 ms No completions evidence; no pagination evidence; tasks missing.

Raw evidence view

Show raw JSON evidence
{
  "checks": {
    "action_safety_probe": {
      "details": {
        "auth_present": false,
        "confirmation_signals": [],
        "safeguard_count": 0,
        "summary": {
          "bulk_access_tools": 0,
          "capability_distribution": {},
          "destructive_tools": 0,
          "egress_tools": 0,
          "exec_tools": 0,
          "high_risk_tools": 0,
          "risk_distribution": {
            "critical": 0,
            "high": 0,
            "low": 0,
            "medium": 0
          },
          "secret_tools": 0,
          "tool_count": 0
        }
      },
      "latency_ms": null,
      "status": "ok"
    },
    "advanced_capabilities_probe": {
      "details": {
        "capabilities": {
          "completions": false,
          "elicitation": false,
          "prompts": false,
          "resource_links": false,
          "resources": false,
          "roots": false,
          "sampling": false,
          "structured_outputs": false
        },
        "enabled": [],
        "enabled_count": 0,
        "initialize_capability_keys": [
          "experimental",
          "prompts",
          "resources",
          "tools"
        ]
      },
      "latency_ms": null,
      "status": "missing"
    },
    "connector_publishability_probe": {
      "details": {
        "blockers": [
          "tools_list",
          "server_card",
          "tool_surface"
        ],
        "criteria": {
          "action_safety": true,
          "auth_flow": true,
          "connector_replay": true,
          "initialize": true,
          "protocol_version": true,
          "remote_transport": true,
          "request_association": true,
          "server_card": false,
          "session_resume": true,
          "step_up_auth": true,
          "tool_surface": false,
          "tools_list": false,
          "transport_compliance": true
        },
        "high_risk_tools": 0,
        "tool_count": 0,
        "transport": "streamable-http"
      },
      "latency_ms": null,
      "status": "error"
    },
    "connector_replay_probe": {
      "details": {
        "reason": "no_tools"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "determinism_probe": {
      "details": {
        "reason": "tools_list_unavailable"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "initialize": {
      "details": {
        "headers": {
          "content-type": "text/event-stream",
          "mcp-session-id": "ef9e6c1308e048abadf095f562f7a8ec"
        },
        "http_status": 200,
        "payload": {
          "id": 1,
          "jsonrpc": "2.0",
          "result": {
            "capabilities": {
              "experimental": {},
              "prompts": {
                "listChanged": false
              },
              "resources": {
                "listChanged": false,
                "subscribe": false
              },
              "tools": {
                "listChanged": false
              }
            },
            "instructions": "GeodesicAI is a deterministic governance and computation platform for AI agents. It does three things:\n\n1. GOVERNANCE \u2014 Validate agent outputs against Blueprint rules before execution. Catches math errors, field inconsistencies, and constraint violations. Returns PASS, FAIL, or REVIEW with repair suggestions and a tamper-proof determinism hash. Requires a Blueprint (governance contract). Use load_rule_pack for fast onboarding or create_blueprint to define custom rules.\n\n2. DISCOVERY \u2014 Find structural patterns in batches of data without machine learning. Detect anomalies, classify structural types, track drift across data streams. No Blueprint required.\n\n3. DETERMINISTIC COMPUTATION \u2014 Route computable problems to the platform's deterministic solvers (geometry, feasibility, constraint satisfaction, spectral analysis, structural reasoning) without consuming LLM tokens. Queries outside the deterministic envelope return a structured response indicating they're outside scope; the caller can route them to their own tooling. No Blueprint required.\n\nNo machine learning. No probabilistic inference in the validation pipeline. Every result is structurally provable and fully traceable.\n\nMental model: Other tools do something. GeodesicAI decides if it should be allowed to happen.\n\nDOCUMENTATION \u2014 For the full user guide covering all tools, Blueprint design, Trajectory mode, and demo walkthroughs, read the 'user_guide' resource (geodesicai://docs/user-guide), or fetch https://app.geodesiclabs.ai/static/GeodesicAI_User_Guide.pdf. For Blueprint design specifics, invoke the 'blueprint_guide' prompt. To turn a validation result into plain English using your own LLM, invoke the 'explain_result' prompt.\n\nSign up at geodesiclabs.ai for an API key.",
            "protocolVersion": "2025-03-26",
            "serverInfo": {
              "name": "GeodesicAI",
              "version": "1.27.0"
            }
          }
        },
        "url": "https://app.geodesiclabs.ai/mcp"
      },
      "latency_ms": 96.05,
      "status": "ok"
    },
    "interactive_flow_probe": {
      "details": {
        "oauth_supported": false,
        "prompt_available": false,
        "risk_hits": [],
        "safe_hits": []
      },
      "latency_ms": null,
      "status": "missing"
    },
    "oauth_authorization_server": {
      "details": {
        "reason": "no_authorization_server"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "oauth_protected_resource": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://app.geodesiclabs.ai/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "url": "https://app.geodesiclabs.ai/.well-known/oauth-protected-resource"
      },
      "latency_ms": 175.03,
      "status": "error"
    },
    "official_registry_probe": {
      "details": {
        "direct_match": true,
        "official_peer_count": 1,
        "registry_identifier": "ai.geodesiclabs/governance-platform",
        "registry_source": "official_registry"
      },
      "latency_ms": null,
      "status": "ok"
    },
    "openid_configuration": {
      "details": {
        "reason": "no_authorization_server"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "probe_noise_resilience": {
      "details": {
        "headers": {
          "content-type": "text/plain; charset=utf-8"
        },
        "http_status": 200,
        "url": "https://app.geodesiclabs.ai/robots.txt"
      },
      "latency_ms": 171.16,
      "status": "ok"
    },
    "prompt_get": {
      "details": {
        "reason": "not_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "prompts_list": {
      "details": {
        "error": "Client error '400 Bad Request' for url 'https://app.geodesiclabs.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400",
        "headers": {
          "content-type": "application/json",
          "mcp-session-id": "d41e13e5ccd74394924bbbf638d4d1ec"
        },
        "http_status": 400,
        "payload": {},
        "reason": "not_advertised",
        "url": "https://app.geodesiclabs.ai/mcp"
      },
      "latency_ms": 173.97,
      "status": "missing"
    },
    "protocol_version_probe": {
      "details": {
        "claimed_version": "2025-03-26",
        "lag_days": 244,
        "latest_known_version": "2025-11-25",
        "releases_behind": 2,
        "validator_protocol_version": "2025-03-26"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "provenance_divergence_probe": {
      "details": {
        "direct_official_match": true,
        "drift_fields": [],
        "metadata_document_count": 1,
        "registry_homepage": null,
        "registry_repository": null,
        "registry_title": null,
        "registry_version": null,
        "server_card_homepage": null,
        "server_card_repository": null,
        "server_card_title": null,
        "server_card_version": null
      },
      "latency_ms": null,
      "status": "ok"
    },
    "request_association_probe": {
      "details": {
        "reason": "no_request_association_capabilities_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "resource_read": {
      "details": {
        "reason": "not_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "resources_list": {
      "details": {
        "error": "Client error '400 Bad Request' for url 'https://app.geodesiclabs.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400",
        "headers": {
          "content-type": "application/json",
          "mcp-session-id": "c9b4d4819ae3438f985aca315fe2daa7"
        },
        "http_status": 400,
        "payload": {},
        "reason": "not_advertised",
        "url": "https://app.geodesiclabs.ai/mcp"
      },
      "latency_ms": 181.88,
      "status": "missing"
    },
    "server_card": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://app.geodesiclabs.ai/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "url": "https://app.geodesiclabs.ai/.well-known/mcp/server-card.json"
      },
      "latency_ms": 190.55,
      "status": "error"
    },
    "session_resume_probe": {
      "details": {
        "headers": {
          "content-type": "text/event-stream",
          "mcp-session-id": "ef9e6c1308e048abadf095f562f7a8ec"
        },
        "http_status": 200,
        "payload": {
          "id": 301,
          "jsonrpc": "2.0",
          "result": {
            "tools": [
              {
                "description": "\n    Validate structured data against a Blueprint's rules. Returns PASS, FAIL, or REVIEW.\n\n    The platform checks mathematical accuracy (do the numbers add up?),\n    structural consistency (do the fields satisfy all constraints?), and\n    semantic plausibility (do the values make sense in context?).\n\n    Every result includes a determinism hash \u2014 the same input with the same\n    Blueprint always produces the same result. Auditable, replayable, legally defensible.\n\n    A Blueprint is required for meaningful validation. Without one, use\n    create_blueprint or load_rule_pack to define your governance rules first.\n\n    Args:\n        api_key: GeodesicAI API key (starts with gai_)\n        structured_data: The data to validate (key-value pairs)\n        blueprint: Name of the Blueprint to validate against. Use list_blueprints to see options.\n    ",
                "inputSchema": {
                  "properties": {
                    "api_key": {
                      "title": "Api Key",
                      "type": "string"
                    },
                    "blueprint": {
                      "default": "default",
                      "title": "Blueprint",
                      "type": "string"
                    },
                    "structured_data": {
                      "additionalProperties": true,
                      "title": "Structured Data",
                      "type": "object"
                    }
                  },
                  "required": [
                    "api_key",
                    "structured_data"
                  ],
                  "title": "validateArguments",
                  "type": "object"
                },
                "name": "validate"
              },
              {
                "description": "\n    Validate structured data and automatically compute repairs if it fails.\n    Single call that combines validate + repair.\n\n    If PASS: returns the validated data with determinism hash.\n    If FAIL: returns the failure details AND a repaired payload with\n    field-by-field corrections and confidence scores. The agent can\n    inspect the repairs and resubmit the corrected data.\n    If REVIEW: returns the flagged data with review reasoning.\n\n    This is the recommended starting point for most agent integrations.\n\n    Args:\n        api_key: GeodesicAI API key (starts with gai_)\n        structured_data: The data to validate (key-value pairs)\n        blueprint: Name of the Blueprint to validate against. Use list_blueprints to see options.\n    ",
                "inputSchema": {
                  "properties": {
                    "api_key": {
                      "title": "Api Key",
                      "type": "string"
                    },
                    "blueprint": {
                      "default": "default",
                      "title": "Blueprint",
                      "type": "string"
                    },
                    "structured_data": {
                      "additionalProperties": true,
                      "title": "Structured Data",
                      "type": "object"
                    }
                  },
                  "required": [
                    "api_key",
                    "structured_data"
                  ],
                  "title": "validate_and_repairArguments",
                  "type": "object"
                },
                "name": "validate_and_repair"
              },
              {
                "description": "\n    Create a Blueprint \u2014 a governance contract that defines validation rules.\n\n    A Blueprint tells the platform what \"correct\" means for your data: which\n    fields exist, what math must hold between them, and what value ranges\n    are acceptable. Without a Blueprint, the platform has nothing to validate against.\n\n    If you don't know what rules to define, use load_rule_pack to start from\n    a prebuilt template, or use discover_patterns to find rules from your data.\n\n    Use the blueprint_guide prompt for the complete reference of all available\n    rule types, constraint types, and configuration options.\n\n    Args:\n        api_key: GeodesicAI API key (starts with gai_)\n        customer_name: Organization or project name (used for folder naming)\n        workflow_name: Unique identifier for this Blueprint (used as the 'blueprint' parameter in validate)\n        mode: \"observe\" (platform checks agent's work) or \"enforce\" (platform computes derived fields)\n        extracted_fields: Fields the agent extracts from source data (e.g. [\"vendor\", \"qty\", \"unit_cost\"])\n        derived_fields: Fields computed from other fields (e.g. [\"subtotal\", \"total\"])\n        derivation_rules: Math rules defining field relationships. Available types: \"add\" (target = a + b), \"subtract\" (target = a - b), \"multiply\" (target = a \u00d7 b), \"divide\" (target = a \u00f7 b), \"round\" (round field to N places), \"copy\" (copy source to target), \"items_multiply\" (per-item a \u00d7 b in a list), \"items_sum\" (sum a field across list items). Each rule requires \"type\" and the relevant fields. See blueprint_guide prompt for full schema.\n        formal_constraints: Value bounds and ratio constraints. Available types: \"magnitude_anchor\" (field within min/max range, requires \"field\", \"min\", \"max\"), \"relative_anchor\" (ratio a/b within tolerance, requires \"a\", \"b\", \"expected_ratio\", \"tolerance\"), \"max_action_threshold\" (trigger action if field exceeds threshold, requires \"field\", \"threshold\", \"action\"). See blueprint_guide prompt for full schema.\n        semantic_checks: Domain-specific validation checks\n        require_math: Validate mathematical relationships (default true)\n        require_consistency: Check internal consistency (default true)\n        require_coherence: Check structural coherence (default true)\n        require_provenance: Require agents to report extraction source locations\n        require_high_assurance: Strictest validation \u2014 feasibility, spectral, and global consistency required\n        enable_anomaly_detection: Geometric fingerprinting to detect structural outliers\n        enable_drift_tracking: Monitor pattern stability across batches\n    ",
                "inputSchema": {
                  "properties": {
                    "api_key": {
                      "title": "Api Key",
                      "type": "string"
                    },
                    "customer_name": {
                      "title": "Customer Name",
                      "type": "string"
                    },
                    "derivation_rules": {
                      "default": null,
                      "items": {},
                      "title": "Derivation Rules",
                      "type": "array"
                    },
                    "derived_fields": {
                      "default": null,
                      "items": {},
                      "title": "Derived Fields",
                      "type": "array"
                    },
                    "enable_anomaly_detection": {
                      "default": false,
                      "title": "Enable Anomaly Detection",
                      "type": "boolean"
                    },
                    "enable_drift_tracking": {
                      "default": false,
                      "title": "Enable Drift Tracking",
                      "type": "boolean"
                    },
                    "extracted_fields": {
                      "default": null,
                      "items": {},
                      "title": "Extracted Fields",
                      "type": "array"
                    },
                    "formal_constraints": {
                      "default": null,
                      "items": {},
                      "title": "Formal Constraints",
                      "type": "array"
                    },
                    "mode": {
                      "default": "observe",
                      "title": "Mode",
                      "type": "string"
                    },
                    "require_coherence": {
                      "default": true,
                      "title": "Require Coherence",
                      "type": "boolean"
                    },
                    "require_consistency": {
                      "default": true,
                      "title": "Require Consistency",
                      "type": "boolean"
                    },
                    "require_high_assurance": {
                      "default": false,
                      "title": "Require High Assurance",
                      "type": "boolean"
                    },
                    "require_math": {
                      "default": true,
                      "title": "Require Math",
                      "type": "boolean"
                    },
                    "require_provenance": {
                      "default": false,
                      "title": "Require Provenance",
                      "type": "boolean"
                    },
                    "semantic_checks": {
                      "default": null,
                      "items": {},
                      "title": "Semantic Checks",
                      "type": "array"
                    },
                    "workflow_name": {
                      "title": "Workflow Name",
                      "type": "string"
                    }
                  },
                  "required": [
                    "api_key",
                    "customer_name",
                    "workflow_name"
                  ],
                  "title": "create_blueprintArguments",
                  "type": "object"
                },
                "name": "create_blueprint"
              },
              {
                "description": "\n    List Blueprints owned by the calling account.\n\n    Returns each Blueprint's name, workflow identifier, mode, and\n    field/rule/constraint counts. Use the workflow_name as the\n    'blueprint' parameter when calling validate.\n\n    Blueprint modes \u2014 important for agents that summarize results:\n      - \"observe\" (Observation mode): the platform validates data\n        against the Blueprint's rules and returns PASS, FAIL, or\n        REVIEW with repair suggestions. Validation is detection-only;\n        the caller decides what to do with the result.\n      - \"enforce\" (Execution mode): the platform performs the same\n        validation AND authorizes downstream side effects. Side\n        effects are blocked if validation fails. In this mode, rules\n        that compute derived values (like totals) publish the\n        platform's computed result as authoritative, so downstream\n        consumers see the canonical value rather than the agent's.\n\n    Both modes run the same rule checks. The difference is what\n    happens after validation, not during it.\n\n    Scope: only Blueprints created by the calling account are returned.\n    Use validate / repair / etc. with the workflow_name to operate on them.\n\n    Args:\n        api_key: GeodesicAI API key (starts with gai_)\n    ",
                "inputSchema": {
                  "properties": {
                    "api_key": {
                      "title": "Api Key",
                      "type": "string"
                    }
                  },
                  "required": [
                    "api_key"
                  ],
                  "title": "list_blueprintsArguments",
                  "type": "object"
                },
                "name": "list_blueprints"
              },
              {
                "description": "\n    Compute the nearest valid point on the constraint manifold.\n\n    Given structured data with errors, missing values, or inconsistencies,\n    returns field-by-field repair suggestions with geometric confidence scores.\n    Uses algebraic projection for linear constraints and iterative geodesic\n    projection for nonlinear constraints.\n\n    Can accept rules directly or load them from a Blueprint.\n\n    Args:\n        api_key: GeodesicAI API key (starts with gai_)\n        structured_data: The data to repair (key-value pairs)\n        derivation_rules: Math rules (optional if blueprint is provided)\n        formal_constraints: Constraints (optional if blueprint is provided)\n        blueprint: Load rules from this Blueprint instead of specifying them directly\n    ",
                "inputSchema": {
                  "properties": {
                    "api_key": {
                      "title": "Api Key",
                      "type": "string"
                    },
                    "blueprint": {
                      "default": null,
                      "title": "Blueprint",
                      "type": "string"
                    },
                    "derivation_rules": {
                      "default": null,
                      "items": {},
                      "title": "Derivation Rules",
                      "type": "array"
                    },
                    "formal_constraints": {
                      "default": null,
                      "items": {},
                      "title": "Formal Constraints",
                      "type": "array"
                    },
                    "structured_data": {
                      "additionalProperties": true,
                      "title": "Structured Data",
                      "type": "object"
                    }
                  },
                  "required": [
                    "api_key",
                    "structured_data"
                  ],
                  "title": "repairArguments",
                  "type": "object"
                },
                "name": "repair"
              },
              {
                "description": "\n    Check whether a set of constraints can be simultaneously satisfied.\n\n    Uses the twist-compression operator to detect structural obstructions \u2014\n    fundamental conflicts in the constraint system that cannot be resolved\n    by adjusting any single field. Returns obstruction type, magnitude,\n    and the specific constraint interactions causing the conflict.\n\n    Fast pre-check before running full validation.\n\n    Args:\n        api_key: GeodesicAI API key (starts with gai_)\n        constraints: List of derivation rules and formal constraints to check\n        field_values: Current field values (numeric key-value pairs)\n    ",
                "inputSchema": {
                  "properties": {
                    "api_key": {
                      "title": "Api Key",
                      "type": "string"
                    },
                    "constraints": {
                      "items": {},
                      "title": "Constraints",
                      "type": "array"
                    },
                    "field_values": {
                      "additionalProperties": true,
                      "title": "Field Values",
                      "type": "object"
                    }
                  },
                  "required": [
                    "api_key",
                    "constraints",
                    "field_values"
                  ],
                  "title": "check_feasibilityArguments",
                  "type": "object"
                },
                "name": "check_feasibility"
              },
              {
                "description": "\n    Deterministic forward reasoning \u2014 show what valid states are reachable.\n\n    Given the current data state, generates candidate next states by\n    applying Blueprint rules, then ranks them by structural quality\n    (lowest drift, highest confidence, shortest path, or lowest risk).\n\n    Args:\n        api_key: GeodesicAI API key (starts with gai_)\n        api_key: GeodesicAI API key (starts with gai_)\n        structured_data: Current data state\n        blueprint: Blueprint to use for rules and constraints\n        max_depth: How many steps ahead to forecast (1-10)\n        max_branches: Maximum branches per step (1-10)\n        rank_by: Ranking criterion \u2014 \"drift\" (most stable), \"confidence\" (highest geometric confidence), \"shortest\" (fewest changes), \"risk\" (lowest risk)\n    ",
                "inputSchema": {
                  "properties": {
                    "api_key": {
                      "title": "Api Key",
                      "type": "string"
                    },
                    "blueprint": {
                      "default": "default",
                      "title": "Blueprint",
                      "type": "string"
                    },
                    "max_branches": {
                      "default": 5,
                      "title": "Max Branches",
                      "type": "integer"
                    },
                    "max_depth": {
                      "default": 3,
                      "title": "Max Depth",
                      "type": "integer"
                    },
                    "rank_by": {
                      "default": "drift",
                      "title": "Rank By",
                      "type": "string"
                    },
                    "structured_data": {
                      "additionalProperties": true,
                      "title": "Structured Data",
                      "type": "object"
                    }
                  },
                  "required": [
                    "api_key",
                    "structured_data"
                  ],
                  "title": "forecastArguments",
                  "type": "object"
                },
                "name": "forecast"
              },
              {
                "description": "\n    Feed a batch of structured data to discover patterns deterministically.\n    No Blueprint required \u2014 discovers rules from the data itself.\n\n    Analyzes the batch using motif discovery, structural routing, and\n    geometric fingerprinting. Returns candidate validation rules with\n    confidence scores, structural type classifications, and anomaly counts.\n    Source data is never stored \u2014 only statistical summaries persist.\n\n    Discovered rules can be promoted into Blueprints using approve_rule.\n\n    Args:\n        api_key: GeodesicAI API key (starts with gai_)\n        documents: List of structured data objects to analyze\n        api_key: GeodesicAI API key (starts with gai_)\n        blueprint: Namespace for this discovery session\n    ",
                "inputSchema": {
                  "properties": {
                    "api_key": {
                      "title": "Api Key",
                      "type": "string"
                    },
                    "blueprint": {
                      "default": "default",
                      "title": "Blueprint",
                      "type": "string"
                    },
                    "documents": {
                      "items": {},
                      "title": "Documents",
                      "type": "array"
                    }
                  },
                  "required": [
                    "api_key",
                    "documents"
                  ],
                  "title": "discover_patternsArguments",
                  "type": "object"
                },
                "name": "discover_patterns"
              },
              {
                "description": "\n    Find the shortest path from an invalid state to a valid one.\n\n    Given data that fails validation, computes a sequence of minimal\n    field changes that would bring the data into compliance with the\n    Blueprint's rules and constraints.\n\n    Args:\n        structured_data: Current (invalid) data state\n        blueprint: Blueprint defining the valid constraint space\n        max_depth: Maximum repair steps to search (1-10)\n        rank_by: Ranking criterion \u2014 \"shortest\", \"drift\", \"confidence\", \"risk\"\n    ",
                "inputSchema": {
                  "properties": {
                    "api_key": {
                      "title": "Api Key",
                      "type": "string"
                    },
                    "blueprint": {
                      "default": "default",
                      "title": "Blueprint",
                      "type": "string"
                    },
                    "max_depth": {
                      "default": 4,
                      "title": "Max Depth",
                      "type": "integer"
                    },
                    "rank_by": {
                      "default": "shortest",
                      "title": "Rank By",
                      "type": "string"
                    },
                    "structured_data": {
                      "additionalProperties": true,
                      "title": "Structured Data",
                      "type": "object"
                    }
                  },
                  "required": [
                    "api_key",
                    "structured_data"
                  ],
                  "title": "repair_pathArguments",
                  "type": "object"
                },
                "name": "repair_path"
              },
              {
                "description": "\n    Compare outcomes under different rule sets.\n\n    Given the same data, runs trajectory analysis under two different\n    sets of rules/constraints and shows how the valid state space differs.\n    Useful for what-if analysis: \"what happens if I change this rule?\"\n\n    Args:\n        api_key: GeodesicAI API key (starts with gai_)\n        structured_data: Data to analyze\n        blueprint: Primary Blueprint (rule set A)\n        rules_b: Alternative derivation rules (rule set B)\n        constraints_b: Alternative constraints (rule set B)\n    ",
                "inputSchema": {
                  "properties": {
                    "api_key": {
                      "title": "Api Key",
                      "type": "string"
                    },
                    "blueprint": {
                      "default": "default",
                      "title": "Blueprint",
                      "type": "string"
                    },
                    "constraints_b": {
                      "default": null,
                      "items": {},
                      "title": "Constraints B",
                      "type": "array"
                    },
                    "rules_b": {
                      "default": null,
                      "items": {},
                      "title": "Rules B",
                      "type": "array"
                    },
                    "structured_data": {
                      "additionalProperties": true,
                      "title": "Structured Data",
                      "type": "object"
                    }
                  },
                  "required": [
                    "api_key",
                    "structured_data"
                  ],
                  "title": "counterfactualArguments",
                  "type": "object"
                },
                "name": "counterfactual"
              },
              {
                "description": "\n    Deep anomaly analysis with geometric proof. No Blueprint required.\n\n    Explains WHY data is anomalous using three independent methods:\n    1. Structural fingerprinting \u2014 distance from the learned manifold\n    2. Cluster analysis \u2014 deviation from structural type centroids\n    3. Twist-compression obstruction \u2014 fundamental constraint conflicts\n\n    Returns a human-readable geometric proof of anomaly, not just a flag.\n\n    Args:\n        structured_data: The data to analyze for anomalies\n    ",
                "inputSchema": {
                  "properties": {
                    "api_key": {
                      "title": "Api Key",
                      "type": "string"
                    },
                    "structured_data": {
                      "additionalProperties": true,
                      "title": "Structured Data",
                      "type": "object"
                    }
                  },
                  "required": [
                    "api_key",
                    "structured_data"
                  ],
                  "title": "analyze_anomalyArguments",
                  "type": "object"
                },
                "name": "analyze_anomaly"
              },
              {
                "description": "\n    Create a multi-agent sequential execution chain.\n\n    Defines a pipeline where multiple agents process data in sequence.\n    Each stage is validated against the Blueprint before the next stage\n    can proceed. Repair suggestions propagate forward through the chain.\n\n    Args:\n        blueprint: Blueprint governing all stages\n        stages: List of stage definitions, e.g. [{\"stage_name\": \"extract\", \"agent_name\": \"PDF Scanner\"}, {\"stage_name\": \"validate\", \"agent_name\": \"QA Agent\"}]\n        ttl: Chain timeout in seconds (default 3600)\n    ",
                "inputSchema": {
                  "properties": {
                    "api_key": {
                      "title": "Api Key",
                      "type": "string"
                    },
                    "blueprint": {
                      "title": "Blueprint",
                      "type": "string"
                    },
                    "stages": {
                      "items": {},
                      "title": "Stages",
                      "type": "array"
                    },
                    "ttl": {
                      "default": 3600,
                      "title": "Ttl",
                      "type": "integer"
                    }
                  },
                  "required": [
                    "api_key",
                    "blueprint",
                    "stages"
                  ],
                  "title": "create_chainArguments",
                  "type": "object"
                },
                "name": "create_chain"
              },
              {
                "description": "\n    Submit data for a chain stage. The platform validates the data\n    using the chain's Blueprint, then advances the chain if validation passes.\n\n    The response includes the next stage info and any accumulated\n    repair suggestions from prior stages.\n\n    Args:\n        api_key: GeodesicAI API key (starts with gai_)\n        chain_id: Chain identifier from create_chain\n        stage: Stage name to submit for\n        structured_data: Data for this stage\n    ",
                "inputSchema": {
                  "properties": {
                    "api_key": {
                      "title": "Api Key",
                      "type": "string"
                    },
                    "chain_id": {
                      "title": "Chain Id",
                      "type": "string"
                    },
                    "stage": {
                      "title": "Stage",
                      "type": "string"
                    },
                    "structured_data": {
                      "additionalProperties": true,
                      "title": "Structured Data",
                      "type": "object"
                    }
                  },
                  "required": [
                    "api_key",
                    "chain_id",
                    "stage",
                    "structured_data"
                  ],
                  "title": "submit_chain_stageArguments",
                  "type": "object"
                },
                "name": "submit_chain_stage"
              },
              {
                "description": "\n    Audit a handoff between two chain stages. Returns a context capsule\n    with verified facts from the prior stage and checks structural\n    compatibility of proposed data for the next stage.\n\n    Use this between chain stages to ensure Agent B receives only\n    verified data from Agent A, and that nothing was mutated in transit.\n\n    The context capsule contains:\n    - Verified fields and their values from the prior stage\n    - Determinism hash proving the prior stage's results\n    - Blueprint constraints the next stage must satisfy\n    - Compatibility verdict if proposed_data is provided\n\n    Args:\n        api_key: GeodesicAI API key (starts with gai_)\n        chain_id: Chain identifier from create_chain\n        from_stage: Stage name that completed (Agent A)\n        to_stage: Stage name about to start (Agent B)\n        proposed_data: Optional data Agent B intends to submit \u2014 checked for compatibility\n    ",
                "inputSchema": {
                  "properties": {
                    "api_key": {
                      "title": "Api Key",
                      "type": "string"
                    },
                    "chain_id": {
                      "title": "Chain Id",
                      "type": "string"
                    },
                    "from_stage": {
                      "title": "From Stage",
                      "type": "string"
                    },
                    "proposed_data": {
                      "additionalProperties": true,
                      "default": null,
                      "title": "Proposed Data",
                      "type": "object"
                    },
                    "to_stage": {
                      "title": "To Stage",
                      "type": "string"
                    }
                  },
                  "required": [
                    "api_key",
                    "chain_id",
                    "from_stage",
                    "to_stage"
                  ],
                  "title": "handoff_auditArguments",
                  "type": "object"
                },
                "name": "handoff_audit"
              },
              {
                "description": "\n    Promote a discovered rule into Blueprint-compatible format.\n\n    After running discover_patterns, use this to approve high-confidence\n    rules for inclusion in a Blueprint.\n\n    Args:\n        api_key: GeodesicAI API key (starts with gai_)\n        rule_id: ID of the discovered rule (from discover_patterns results)\n        blueprint: Discovery session namespace\n    ",
                "inputSchema": {
                  "properties": {
                    "api_key": {
                      "title": "Api Key",
                      "type": "string"
                    },
                    "blueprint": {
                      "default": "default",
                      "title": "Blueprint",
                      "type": "string"
                    },
                    "rule_id": {
                      "title": "Rule Id",
                      "type": "string"
                    }
                  },
                  "required": [
                    "api_key",
                    "rule_id"
                  ],
                  "title": "approve_ruleArguments",
                  "type": "object"
                },
                "name": "approve_rule"
              },
              {
                "description": "\n    Reject a discovered candidate rule.\n\n    Args:\n        api_key: GeodesicAI API key (starts with gai_)\n        rule_id: ID of the discovered rule to reject\n        blueprint: Discovery session namespace\n    ",
                "inputSchema": {
                  "properties": {
                    "api_key": {
                      "title": "Api Key",
                      "type": "string"
                    },
                    "blueprint": {
                      "default": "default",
                      "title": "Blueprint",
                      "type": "string"
                    },
                    "rule_id": {
                      "title": "Rule Id",
                      "type": "string"
                    }
                  },
                  "required": [
                    "api_key",
                    "rule_id"
                  ],
                  "title": "reject_ruleArguments",
                  "type": "object"
                },
                "name": "reject_rule"
              },
              {
                "description": "\n    Get auto-discovered structural type classifications.\n\n    After running discover_patterns, returns the structural categories\n    the platform identified in the data \u2014 without being told what\n    categories exist. Shows document counts, distinguishing fields,\n    and domain hints per type.\n\n    Args:\n        blueprint: Discovery session namespace\n    ",
                "inputSchema": {
                  "properties": {
                    "api_key": {
                      "title": "Api Key",
                      "type": "string"
                    },
                    "blueprint": {
                      "default": "default",
                      "title": "Blueprint",
                      "type": "string"
                    }
                  },
                  "required": [
                    "api_key"
                  ],
                  "title": "structural_typesArguments",
                  "type": "object"
                },
                "name": "structural_types"
              },
              {
                "description": "\n    Hodge-style decomposition of validation failures.\n\n    Splits the error between original and corrected values into three\n    orthogonal components:\n    - Exact: direct rule violations (a field breaks a specific math rule)\n    - Co-exact: constraint boundary violations (a field is at the edge of valid range)\n    - Harmonic: systemic structural errors (the overall data shape is wrong)\n\n    Identifies the primary failure type and contributing fields.\n\n    Args:\n        api_key: GeodesicAI API key (starts with gai_)\n        original_values: The original field values (numeric key-value pairs)\n        corrected_values: The corrected/expected field values\n        derivation_rules: Math rules (optional if blueprint provided)\n        formal_constraints: Constraints (optional if blueprint provided)\n        blueprint: Load rules from this Blueprint\n    ",
                "inputSchema": {
                  "properties": {
                    "api_key": {
                      "title": "Api Key",
                      "type": "string"
                    },
                    "blueprint": {
                      "default": null,
                      "title": "Blueprint",
                      "type": "string"
                    },
                    "corrected_values": {
                      "additionalProperties": true,
                      "title": "Corrected Values",
                      "type": "object"
                    },
                    "derivation_rules": {
                      "default": null,
                      "items": {},
                      "title": "Derivation Rules",
                      "type": "array"
                    },
                    "formal_constraints": {
                      "default": null,
                      "items": {},
                      "title": "Formal Constraints",
                      "type": "array"
                    },
                    "original_values": {
                      "additionalProperties": true,
                      "title": "Original Values",
                      "type": "object"
                    }
                  },
                  "required": [
                    "api_key",
                    "original_values",
                    "corrected_values"
                  ],
                  "title": "decompose_failureArguments",
                  "type": "object"
                },
                "name": "decompose_failure"
              },
              {
                "description": "\n    Compute a composite geometric confidence score from validation signals.\n    No Blueprint required \u2014 works on any validate result.\n\n    Combines six weighted signals into a single confidence score:\n    - Surface distance (how close to the constraint manifold)\n    - Geometric health (projection quality, regulator, closure)\n    - Anomaly score (structural fingerprint deviation)\n    - Stability score (batch drift)\n    - Motif compliance (pattern violations)\n    - Motif gate (enforcement decision)\n\n    Returns confidence level (high/medium/low) and a recommendation.\n\n    Typically called with the state_vector from a validate result.\n\n    Args:\n        api_key: GeodesicAI API key (starts with gai_)\n        state_vector: State vector dictionary (from validate results)\n    ",
                "inputSchema": {
                  "properties": {
                    "api_key": {
                      "title": "Api Key",
                      "type": "string"
                    },
                    "state_vector": {
                      "additionalProperties": true,
                      "title": "State Vector",
                      "type": "object"
                    }
                  },
                  "required": [
                    "api_key",
                    "state_vector"
                  ],
                  "title": "geometric_confidenceArguments",
                  "type": "object"
                },
                "name": "geometric_confidence"
              },
              {
                "description": "\n    Run structural realization analysis on a payload.\n\n    Embeds the payload via the Blueprint's declared embedding schema,\n    projects it onto the Blueprint's reference subspace, and returns\n    a realization score, residual, projection angle, and full report.\n\n    The Blueprint must include a `realization` configuration block\n    (see RealizationConfig in Platform_Agent.realization.schema). If\n    no realization config is present, the report status is \"skipped\"\n    and the payload is treated as unconstrained by the realization\n    layer.\n\n    For Blueprints using basis mode \"auto\", the first N payloads\n    bootstrap the reference subspace; until the bootstrap pool is\n    full, the report status is \"skipped\". After bootstrap, every\n    subsequent payload is projected against the locked subspace and\n    receives a real score.\n\n    Args:\n        api_key: GeodesicAI API key (starts with gai_)\n        structured_data: payload to analyze\n        blueprint: Blueprint name (defaults to \"default\")\n\n    Returns:\n        dict with keys:\n          status:              \"pass\" | \"review\" | \"skipped\"\n          realization_score:   float in [0, 1], higher = better fit\n          residual:            ||v - P_U(v)||\n          angle_degrees:       angle between v and P_U(v)\n          in_subspace:         bool \u2014 residual < tolerance\n          basis_mode:          \"vectors\" | \"auto\" | \"uninitialized\"\n          basis_dimension:     k of the reference subspace\n          vector_dimension:    D of the embedded payload\n          report:              full RealizationReport dict (may include\n                               invariance/stability stacks if enabled)\n    ",
                "inputSchema": {
                  "properties": {
                    "api_key": {
                      "title": "Api Key",
                      "type": "string"
                    },
                    "blueprint": {
                      "default": "default",
                      "title": "Blueprint",
                      "type": "string"
                    },
                    "structured_data": {
                      "additionalProperties": true,
                      "title": "Structured Data",
                      "type": "object"
                    }
                  },
                  "required": [
                    "api_key",
                    "structured_data"
                  ],
                  "title": "check_realizationArguments",
                  "type": "object"
                },
                "name": "check_realization"
              },
              {
                "description": "\n    Check whether the data pattern has shifted since previous observations.\n\n    Works with or without a Blueprint. Monitors structural stability across\n    a stream of data. Detects regime changes when the data's geometric\n    embedding moves to a different region of the constraint space \u2014\n    indicating the source data's structure has fundamentally changed.\n\n    Call this repeatedly as new data arrives to track drift over time.\n\n    Args:\n        api_key: GeodesicAI API key (starts with gai_)\n        structured_data: New data point to check for drift\n        blueprint: Blueprint for geometric embedding context\n    ",
                "inputSchema": {
                  "properties": {
                    "api_key": {
                      "title": "Api Key",
                      "type": "string"
                    },
                    "blueprint": {
                      "default": "default",
                      "title": "Blueprint",
                      "type": "string"
                    },
                    "structured_data": {
                      "additionalProperties": true,
                      "title": "Structured Data",
                      "type": "object"
                    }
                  },
                  "required": [
                    "api_key",
                    "structured_data"
                  ],
                  "title": "check_driftArguments",
                  "type": "object"
                },
                "name": "check_drift"
              },
              {
                "description": "\n    Decide whether an action should be allowed to proceed.\n\n    Runs full validation, then applies the Blueprint's execution gate.\n    Returns a simple allow/block decision with reasoning.\n\n    Use this when your agent is about to take a real-world action (payment,\n    filing, API call, data write) and needs a deterministic go/no-go.\n\n    Different from validate: validate says \"is this data correct?\"\n    authorize_execution says \"should this action happen?\"\n\n    Args:\n        api_key: GeodesicAI API key (starts with gai_)\n        structured_data: The data associated with the action\n        blueprint: Blueprint governing this action type\n    ",
                "inputSchema": {
                  "properties": {
                    "api_key": {
                      "title": "Api Key",
                      "type": "string"
                    },
                    "blueprint": {
                      "title": "Blueprint",
                      "type": "string"
                    },
                    "structured_data": {
                      "additionalProperties": true,
                      "title": "Structured Data",
                      "type": "object"
                    }
                  },
                  "required": [
                    "api_key",
                    "structured_data",
                    "blueprint"
                  ],
                  "title": "authorize_executionArguments",
                  "type": "object"
                },
                "name": "authorize_execution"
              },
              {
                "description": "\n    Load a prebuilt Blueprint template for fast onboarding.\n\n    Rule Packs are ready-made governance configurations for common use cases.\n    Call with no pack_id to list all available packs. Call with a pack_id\n    to load the full configuration, then use create_blueprint to save it.\n\n    Available packs include templates for: invoice governance, timecard/payroll\n    governance, legal document governance, purchase order governance, and\n    insurance claims governance. Each includes field definitions, derivation\n    rules, constraints, and agent conditioning instructions.\n\n    Args:\n        api_key: GeodesicAI API key (starts with gai_)\n        pack_id: ID of the rule pack to load. Omit to list available packs.\n    ",
                "inputSchema": {
                  "properties": {
                    "api_key": {
                      "title": "Api Key",
                      "type": "string"
                    },
                    "pack_id": {
                      "default": null,
                      "title": "Pack Id",
                      "type": "string"
                    }
                  },
                  "required": [
                    "api_key"
                  ],
                  "title": "load_rule_packArguments",
                  "type": "object"
                },
                "name": "load_rule_pack"
              },
              {
                "description": "\n    Run validation and return the detailed execution trace.\n\n    Shows the exact sequence of validation nodes that ran, whether each was\n    deterministic, and the runtime of each node. Use for debugging, compliance\n    audits, or understanding exactly what the platform checked.\n\n    Args:\n        api_key: GeodesicAI API key (starts with gai_)\n        structured_data: The data to trace validation for\n        blueprint: Blueprint to validate against\n    ",
                "inputSchema": {
                  "properties": {
                    "api_key": {
                      "title": "Api Key",
                      "type": "string"
                    },
                    "blueprint": {
                      "default": "default",
                      "title": "Blueprint",
                      "type": "string"
                    },
                    "structured_data": {
                      "additionalProperties": true,
                      "title": "Structured Data",
                      "type": "object"
                    }
                  },
                  "required": [
                    "api_key",
                    "structured_data"
                  ],
                  "title": "get_execution_traceArguments",
                  "type": "object"
                },
                "name": "get_execution_trace"
              },
              {
                "description": "\n    Verify that two execution replay contracts represent the same deterministic result.\n\n    This is the programmatic proof of GeodesicAI's core promise: same input + same\n    rules = same result, every time. Given two replay contracts (e.g. from the\n    original execution and a re-run), this tool compares all component hashes and\n    reports whether the executions are byte-identical.\n\n    Use this to:\n    - Prove to an auditor that a decision from March 3rd matches a re-run today.\n    - Detect when a rule change has altered execution behavior (input hash matches\n      but canonical trace hash differs \u2192 the rules diverged).\n    - Confirm a Blueprint migration didn't change any observable outcomes.\n\n    Args:\n        api_key: GeodesicAI API key (starts with gai_)\n        contract_a: A replay contract dict (the `replay_contract` field from a\n                    prior validate/execute_task response)\n        contract_b: Another replay contract dict to compare against contract_a\n\n    Returns:\n        replay_match: bool \u2014 True if the top-level replay_hash matches (fully identical)\n        contract_version_match: bool\n        matches: dict of field_name \u2192 value, for every field that agreed\n        mismatches: dict of field_name \u2192 {expected, actual}, for every field that disagreed\n        summary: plain-English one-liner describing the result\n\n    Interpretation of mismatches:\n        - input_payload_hash: the two runs were fed different data\n        - template_version: the Blueprint was upgraded between runs\n        - solver_registry_hash: the platform itself changed between runs\n        - canonical_trace_hash: same inputs and rules but different execution path\n            (should never happen under determinism; indicates a platform bug)\n        - graph_hash: DAG topology changed between runs\n    ",
                "inputSchema": {
                  "properties": {
                    "api_key": {
                      "title": "Api Key",
                      "type": "string"
                    },
                    "contract_a": {
                      "additionalProperties": true,
                      "title": "Contract A",
                      "type": "object"
                    },
                    "contract_b": {
                      "additionalProperties": true,
                      "title": "Contract B",
                      "type": "object"
                    }
                  },
                  "required": [
                    "api_key",
                    "contract_a",
                    "contract_b"
                  ],
                  "title": "verify_replayArguments",
                  "type": "object"
                },
                "name": "verify_replay"
              },
              {
                "description": "\n    Report the calling account's plan, key usage, and limits.\n\n    Use this to introspect what the caller is allowed to do. Agents that hit\n    rate limits or key-count caps can call this to explain the limit to the\n    human and suggest upgrading if needed.\n\n    Args:\n        api_key: GeodesicAI API key (starts with gai_)\n\n    Returns:\n        plan: The user's current plan \u2014 one of pilot, trial, tier1, tier2, beta, enterprise\n        plan_label: Human-readable plan name (e.g. \"Personal Access\", \"Small Business\")\n        account_key_count: Number of account-level API keys currently issued\n        account_key_limit: Maximum account keys allowed on this plan\n        blueprint_count: Number of Blueprints owned by this user\n        blueprint_limit: Maximum Blueprints allowed on this plan\n        email: The user's email address (for reference in support)\n        user_id: Stable user identifier\n        trial_days_remaining: Days left on trial, if plan == \"trial\"; else null\n    ",
                "inputSchema": {
                  "properties": {
                    "api_key": {
                      "title": "Api Key",
                      "type": "string"
                    }
                  },
                  "required": [
                    "api_key"
                  ],
                  "title": "account_statusArguments",
                  "type": "object"
                },
                "name": "account_status"
              }
            ]
          }
        },
        "requested_protocol_version": "2025-03-26",
        "resumed": true,
        "session_id_present": true,
        "transport": "streamable-http",
        "url": "https://app.geodesiclabs.ai/mcp"
      },
      "latency_ms": 162.27,
      "status": "ok"
    },
    "step_up_auth_probe": {
      "details": {
        "auth_required_checks": [],
        "broad_scopes": [],
        "challenge_headers": [],
        "minimal_scope_documented": false,
        "oauth_present": false,
        "scope_specificity_ratio": 0.0,
        "step_up_signals": [],
        "supported_scopes": []
      },
      "latency_ms": null,
      "status": "missing"
    },
    "tool_snapshot_probe": {
      "details": {
        "reason": "no_tools"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "tools_list": {
      "details": {
        "error": "Client error '400 Bad Request' for url 'https://app.geodesiclabs.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400",
        "headers": {
          "content-type": "application/json",
          "mcp-session-id": "9151297e2f8b468fbbb05b783db3a63a"
        },
        "http_status": 400,
        "payload": {},
        "url": "https://app.geodesiclabs.ai/mcp"
      },
      "latency_ms": 166.04,
      "status": "error"
    },
    "transport_compliance_probe": {
      "details": {
        "bad_protocol_error": null,
        "bad_protocol_headers": {
          "content-type": "application/json",
          "mcp-session-id": "ef9e6c1308e048abadf095f562f7a8ec"
        },
        "bad_protocol_payload": {
          "error": {
            "code": -32600,
            "message": "Bad Request: Unsupported protocol version: 1999-99-99. Supported versions: 2024-11-05, 2025-03-26, 2025-06-18, 2025-11-25"
          },
          "id": "server-error",
          "jsonrpc": "2.0"
        },
        "bad_protocol_status_code": 400,
        "delete_error": null,
        "delete_status_code": 200,
        "expired_session_error": null,
        "expired_session_status_code": 404,
        "issues": [
          "missing_protocol_header"
        ],
        "last_event_id_visible": false,
        "protocol_header_present": false,
        "requested_protocol_version": "2025-03-26",
        "session_id_present": true,
        "transport": "streamable-http"
      },
      "latency_ms": 172.68,
      "status": "warning"
    },
    "utility_coverage_probe": {
      "details": {
        "completions": {
          "advertised": false,
          "live_probe": "not_executed",
          "sample_target": null
        },
        "initialize_capability_keys": [
          "experimental",
          "prompts",
          "resources",
          "tools"
        ],
        "pagination": {
          "metadata_signal": false,
          "next_cursor_methods": [],
          "supported": false
        },
        "tasks": {
          "advertised": false,
          "http_status": 400,
          "probe_status": "missing"
        }
      },
      "latency_ms": 89.46,
      "status": "missing"
    }
  },
  "failures": {
    "oauth_authorization_server": {
      "reason": "no_authorization_server"
    },
    "oauth_protected_resource": {
      "error": "Client error '404 Not Found' for url 'https://app.geodesiclabs.ai/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "url": "https://app.geodesiclabs.ai/.well-known/oauth-protected-resource"
    },
    "openid_configuration": {
      "reason": "no_authorization_server"
    },
    "server_card": {
      "error": "Client error '404 Not Found' for url 'https://app.geodesiclabs.ai/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "url": "https://app.geodesiclabs.ai/.well-known/mcp/server-card.json"
    },
    "tools_list": {
      "error": "Client error '400 Bad Request' for url 'https://app.geodesiclabs.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400",
      "headers": {
        "content-type": "application/json",
        "mcp-session-id": "9151297e2f8b468fbbb05b783db3a63a"
      },
      "http_status": 400,
      "payload": {},
      "url": "https://app.geodesiclabs.ai/mcp"
    }
  },
  "remote_url": "https://app.geodesiclabs.ai/mcp",
  "server_card_payload": null,
  "server_identifier": "ai.geodesiclabs/governance-platform"
}

Known versions

Validation history

7 day score delta
n/a
30 day score delta
n/a
Recent healthy ratio
0%
Freshness
48.2h
TimestampStatusScoreLatencyTools
May 02, 2026 05:42:46 AM UTC Failing 57.8 1739.9 ms 0
May 02, 2026 05:40:47 AM UTC Failing 57.8 1608.3 ms 0
May 02, 2026 05:38:30 AM UTC Failing 57.8 1852.0 ms 0
May 02, 2026 05:35:01 AM UTC Failing 57.8 2008.2 ms 0
May 02, 2026 05:31:40 AM UTC Failing 57.9 1655.5 ms 0
May 02, 2026 05:28:22 AM UTC Failing 57.9 1811.4 ms 0
May 02, 2026 05:25:02 AM UTC Failing 57.9 1939.9 ms 0
May 02, 2026 05:21:32 AM UTC Failing 57.9 1653.1 ms 0

Validation timeline

ValidatedSummaryScoreProtocolAuth modeToolsHigh-risk toolsChanges
May 02, 2026 05:42:46 AM UTC Failing 57.8 2025-03-26 public 0 0 none
May 02, 2026 05:40:47 AM UTC Failing 57.8 2025-03-26 public 0 0 none
May 02, 2026 05:38:30 AM UTC Failing 57.8 2025-03-26 public 0 0 none
May 02, 2026 05:35:01 AM UTC Failing 57.8 2025-03-26 public 0 0 none
May 02, 2026 05:31:40 AM UTC Failing 57.9 2025-03-26 public 0 0 none
May 02, 2026 05:28:22 AM UTC Failing 57.9 2025-03-26 public 0 0 none
May 02, 2026 05:25:02 AM UTC Failing 57.9 2025-03-26 public 0 0 none
May 02, 2026 05:21:32 AM UTC Failing 57.9 2025-03-26 public 0 0 none
May 02, 2026 05:18:42 AM UTC Failing 57.9 2025-03-26 public 0 0 none
May 02, 2026 05:15:34 AM UTC Failing 57.9 2025-03-26 public 0 0 none
May 02, 2026 05:13:09 AM UTC Failing 57.9 2025-03-26 public 0 0 none
May 02, 2026 05:10:02 AM UTC Failing 57.9 2025-03-26 public 0 0 none

Recent validation runs

StartedStatusSummaryLatencyChecks
May 02, 2026 05:42:45 AM UTC Completed Failing 1739.9 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 02, 2026 05:40:45 AM UTC Completed Failing 1608.3 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 02, 2026 05:38:28 AM UTC Completed Failing 1852.0 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 02, 2026 05:34:59 AM UTC Completed Failing 2008.2 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 02, 2026 05:31:39 AM UTC Completed Failing 1655.5 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 02, 2026 05:28:21 AM UTC Completed Failing 1811.4 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 02, 2026 05:25:00 AM UTC Completed Failing 1939.9 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 02, 2026 05:21:30 AM UTC Completed Failing 1653.1 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 02, 2026 05:18:40 AM UTC Completed Failing 1671.1 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
May 02, 2026 05:15:32 AM UTC Completed Failing 1770.0 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe