Skip to content

GEOSENSOR MCP server

Which servers in the official MCP registry are GEOSENSOR's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-24

← Back to GEOSENSOR

Whose server it is
  • Registry nametech.geosensor.atlas/absence-indexverified in the MCP registry

The registry name sits under geosensor.tech. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-24
  • Stateanswerschecked 2026-10-24
  • Tools5
  • Server calls itselfatlas.geosensor.tech
  • Server version0.8.0
  • Protocol version2025-06-18

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 810 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • Parameters are untyped or undescribed in 2 of 5 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-10-24
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer695 ms
  • Space in an agent's context≈ 1,005 tokensthe definitions of all its tools (5), which an agent carries on every turn
  • Tool definitionsB · 77 of 100
  • Typed results0 of 5 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 2 of 5
  • Not saying whether it only reads or can destroy: 5 of 5

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers5 tools · read 2026-10-24
  • request_capability

    ASK US FOR WHAT IS NOT HERE. What would you like to buy? Tell us even if it is not in this inventory. This service is a measurement harness, not a fixed catalogue: if what you need is a machine-readable convention or a property of one…

  • absence_rate

    Measured absence rate for a population, with the evaluated denominator and sample provenance. Pass `gap_class` (e.g. PH-C019) for one class; omit it for the whole table. Aggregate only: no per-host findings.

  • adoption_curve

    Dated adoption series: share of sites whose robots.txt takes a stance on AI agents, by Common Crawl epoch, single vantage. Called with no arguments it returns the trend and the caveats, not the whole table. Pass `epoch` for one point…

  • host_report

    Per-host findings. Requires a bearer credential.

  • bulk_export

    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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "absence-index": {
      "type": "http",
      "url": "https://atlas.geosensor.tech/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http geosensor https://atlas.geosensor.tech/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://atlas.geosensor.tech/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.