Is the Atlas absence index MCP server down?

mcp-registry/tech.geosensor.atlas/absence-index · v0.8.0

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 19:19 UTC · handshake 629ms

As of 2026-11-22 19:19 UTC, the Atlas absence index MCP server is up with a Glimind reliability score of 71/100 (grade C). Over the last 30 days it answered 98.9% of Glimind's liveness checks. It had 14 outages in 90 days, with a median recovery of 9 minutes.

uptime (30d checks)
98.9%
checks observed
713
outages (90d)
14
tools
5

Measured rates at which web services lack machine-readable capabilities. Research demonstrator.

Point your MCP client at this streamable-http endpoint: https://atlas.geosensor.tech/mcp

Agent-readiness: C (75/100)

C (75/100): 0 error(s), 3 warning(s) across 5 tool(s); ~778 tokens of tool definitions.
Scores higher than 10% of 27,663 MCP servers Glimind has audited.
Its tool list costs an agent ~778 tokens per session — lighter than 80% of servers.
72 → 75 since 2026-11-17
no tool-poisoning patterns
Descriptions62
Safety hints30
Schemas100
Protocol100
Stability100
Token cost100
Reliability75
Client compatibility70

What to fix (4)

5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: absence_rate, adoption_curve, bulk_export, host_report, request_capability

2 parameter(s) across 2 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: absence_rate, host_report

Up 98.3% of the time over the 5 days we have observed; median recovery 9 min.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Ftech.geosensor.atlas%2Fabsence-index/fixes

bulk_export 1 change
{
  "name": "bulk_export",
  "description": "Per-class numerators with Wilson intervals and the discarded-as-unknown share, Kaplan-Meier survival of directive adoption by cohort, directive lineage, declaration growth, and RFC 9728 auth-discovery conformance detail — none of it on the free surface — with an ed25519 attestation naming the chain head it was derived from. FREE SAMPLE, no credential: https://atlas.geosensor.tech/free/sample. Price $0.02 or €0.02 + 23% VAT (PT) via x402 v2 in USDC or EURC; a credential is VERIFIED and then SETTL",
  "inputSchema": {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/tech.geosensor.atlas/absence-index"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/tech.geosensor.atlas/absence-index"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Ftech.geosensor.atlas%2Fabsence-index.svg)](https://glimind.com/server/mcp-registry%2Ftech.geosensor.atlas%2Fabsence-index?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Ftech.geosensor.atlas%2Fabsence-index?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Ftech.geosensor.atlas%2Fabsence-index.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:27ea07070feb1b24…, first seen 2026-11-17, included at leaf 319832 of 384,974. Version history · verify what your client received.

Tools (5)

Compare: most reliable data servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the Atlas absence index MCP server down right now?

As of 2026-11-22 19:19 UTC, the Atlas absence index MCP server is up with a Glimind reliability score of 71/100 (grade C). Over the last 30 days it answered 98.9% of Glimind's liveness checks. It had 14 outages in 90 days, with a median recovery of 9 minutes.

How many tools does Atlas absence index MCP server provide?

Atlas absence index MCP server advertises 5 tools, including absence_rate, adoption_curve, bulk_export, host_report, request_capability.

How do I install Atlas absence index MCP server?

Point your MCP client at this streamable-http endpoint: https://atlas.geosensor.tech/mcp

Is the Atlas absence index MCP server safe to connect to an AI agent?

Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Atlas absence index MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve