Skip to content

Atlas absence index MCP server

tech.geosensor.atlas/absence-indexatlas.geosensor.techstreamable-httpv0.8.0Scanned

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

5 tools: 5 change things.

Tools: 0 delete, 0 irreversible, 5 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 3 findings

Tools listed without sign-in. Remote posture

Anlyon alternative

5 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Its sign-in does not let Anlyon set up an OAuth client on its own, so there is no link to it here.

What the Atlas absence index MCP server can do

The Atlas absence index MCP server is published by atlas.geosensor.tech, a domain the MCP Registry verified. It has 5 tools. It can create or change data (5 tools: request_capability, absence_rate, adoption_curve, host_report and 1 more), but cannot delete data. None of its tools only reads.

1 tool brings in text other people can write (adoption_curve).

The fixed checks matched 3 findings (credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 10, 2026, version 0.8.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 5Claude Code: ask
  • absence_rateMeasured absence rate for a population, with the evaluated denominator and sample provenance.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_curveDated adoption series: share of sites whose robots.txt takes a stance on AI agents, by Common Crawl epoch, single vantage.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe description's first sentence says "crawl": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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, `series: true` for all of them, or `withheld: true` for the undersampled epochs that are kept out of the series. Caveats are always included — read them before quoting a number.
  • bulk_exportPer-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…1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...ad it was derived from. FREE SAMPLE, no credential: https://atlas.geosensor.tech/free/samp..."

      What this check looks for
    Description, as the server wrote it
    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 SETTLED before anything is returned. A €19/month net + VAT subscription at https://atlas.geosensor.tech/paid/subscribe (23370000 atomic units) needs no per-call payment. TESTNET only (Base Sepolia): settlement is on-chain but moves test tokens with no monetary value. The tokens on this network are free from https://faucet.circle.com, and you need no ETH because the facilitator pays the gas.
  • host_reportPer-host findings.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "Per-host findings. Requires a bearer credential."

      What this check looks for
    Description, as the server wrote it
    Per-host findings. Requires a bearer credential.
  • request_capabilityASK US FOR WHAT IS NOT HERE.1 finding

    Why it is in this group

    • The name "request_capability" says "request": a word for a change.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...tional and only used to reply. Free, no credential, no payment."

      What this check looks for
    Description, as the server wrote it
    ASK US FOR WHAT IS NOT HERE. What would you like to buy? Tell us even if it is not in this inventory. If what you need is a machine-readable convention, or a property of one across a host population, we can usually measure it for you — and if we cannot, we will say so. Call the `request_capability` tool with `want` describing what you need. Free text is fine. A contact is optional and only used to reply. Free, no credential, no payment.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:19 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://atlas.geosensor.tech/.well-known/oauth-protected-resource/mcp
Authorization servers
https://atlas.geosensor.tech
Legacy HTTP+SSE transport
no
Dynamic client registration
no
Client ID metadata documents
no
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://atlas.geosensor.tech/mcp: tools/list returned 5 tools to an anonymous client, including request_capability (write), absence_rate (write), adoption_curve (write), host_report (write), bulk_export (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

3 info

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
  2. Tools2 changed.~2 changedView diff

Install

Pinned to version 0.8.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__absence-index__request_capability",
      "mcp__absence-index__absence_rate",
      "mcp__absence-index__adoption_curve",
      "mcp__absence-index__host_report",
      "mcp__absence-index__bulk_export"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as absence-index. Review it before you use it.

Capability tags behind 1 rule
  • mcp__absence-index__adoption_curve untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/tech.geosensor.atlas/absence-index/verify?hash=4b821f9b0cb4edb3bf8c7e43e50cc0f38d268a098682f8362129c2aff4e2392d" | jq -e '.changed == false'

Pinned hash 4b821f9b0cb4, from Nov 10, 2026, 13:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/tech.geosensor.atlas/absence-index/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for tech.geosensor.atlas/absence-index
[![Anlyon Radar](https://radar.anlyon.com/badge/tech.geosensor.atlas/absence-index.svg)](https://radar.anlyon.com/servers/tech.geosensor.atlas/absence-index)

Source: MCP Registry. Synced Nov 10, 2026, 13:18 UTC.

Atlas absence index MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Atlas absence index MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 5 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Atlas absence index MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Atlas absence index MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Atlas absence index MCP server have?

5 tools: 5 write. request_capability, absence_rate, adoption_curve, host_report and bulk_export.

Does the Atlas absence index MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Atlas absence index MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Atlas absence index MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.