Is ai.geodesiclabs/governance-platform up? Live MCP status
Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.
| Endpoint | https://app.geodesiclabs.ai/mcp |
|---|---|
| Page built |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Could not tell (HTTP 401)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://app.geodesiclabs.ai/mcp/server-card |
| MCP server card (SEP-1649 location) | Could not tell (HTTP 401)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Could not tell (HTTP 401)./.well-known/http-message-signatures-directory |
Read at https://app.geodesiclabs.ai with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 37 tools: account_status, analyze_anomaly, approve_rule, authorize_execution, check_blueprint_health, check_drift, check_realization, compare_semantic_equivalence, counterfactual, create_blueprint, create_chain, decompose_failure, delete_api_key, delete_blueprint, discover_patterns, forecast, geometric_confidence, get_execution_trace, get_inference_trace, govern_inference, handoff_audit, list_api_keys, list_blueprints, load_rule_pack, profile_blueprint_robustness, recent_inference_decisions, reject_rule, repair, repair_path, rotate_api_key, structural_types, submit_chain_stage, update_blueprint, validate, validate_repair, verify_certificate, verify_replay.
Its tools changed between 2026-09 and 2026-10:
analyze_anomaly: input schema changedcompare_semantic_equivalence: description, input schema changedget_inference_trace: input schema changedgovern_inference: description, input schema changedrecent_inference_decisions: description, input schema changedverify_certificate: input schema changedverify_replay: description changed
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | ai.geodesiclabs/governance-platform |
|---|---|
| Endpoint | https://app.geodesiclabs.ai/mcp |
| Publisher repository | not known: the registry did not return this listing within 4 seconds |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt