Atlas absence index
REMOTE · ATLAS.GEOSENSOR.TECH
Measured rates at which web services lack machine-readable capabilities. Research demonstrator.
Available components
Last scanned (18 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Web Scraping
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 854 tokens (~170/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “bulk_export” rewrote its description, which is the text the model reads security
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 +1
- MCP protocol: fail → pass ▲ functional
- MCP protocol version: 2025-06-18 → 2026-07-28 functional
- 30 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 29 Oct 26 +1
- Stability: 0.97 → pass security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “bulk_export” rewrote its description, which is the text the model reads security
- Tool “request_capability” rewrote its description, which is the text the model reads security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://atlas.geosensor.tech/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=atlas.geosensor.tech | CN=YE1,O=Let's Encrypt,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 65d40898d2c8dca392fa654607673e45aa1 |
| SANs: atlas.geosensor.tech | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of atlas.geosensor.tech. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| tech. | DS published | 2185 | 13 | Verified |
| geosensor.tech. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://atlas.geosensor.tech/mcp | Verified | 200 | |
| http (plaintext) | http://atlas.geosensor.tech/mcp | HTTPS enforced | 301 | https://atlas.geosensor.tech/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
absence_rate ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| gap_class | string | – | – |
No output schema declared.
No examples provided.
adoption_curve ~156
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.
| Name | Type | Req | Description |
|---|---|---|---|
| epoch | string | – | A Common Crawl epoch id, e.g. CC-MAIN-2026-39. |
| series | boolean | – | Return every epoch in the series. |
| withheld | boolean | – | Return the epochs withheld for n < min_n. |
No output schema declared.
No examples provided.
bulk_export ~217
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
host_report ~24
Per-host findings. Requires a bearer credential.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | – |
No output schema declared.
No examples provided.
request_capability ~160
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.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | – | Optional, only used to reply to you. |
| want | string | yes | What you need. Free text. Required. |
| would_pay | string | – | Optional: what it would be worth to you. |
No output schema declared.
No examples provided.
How do I install the Atlas absence index MCP server?
Atlas absence index is a hosted endpoint at https://atlas.geosensor.tech/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · atlas.geosensor.tech
claude mcp add --transport http tech-geosensor-atlas-absence-index 'https://atlas.geosensor.tech/mcp'
What is the Atlas absence index MCP server?
Atlas absence index is an MCP server listed in the public MCP registry as tech.geosensor.atlas/absence-index. Measured rates at which web services lack machine-readable capabilities. Research demonstrator. This page covers its hosted endpoint (https://atlas.geosensor.tech/mcp).
Is the Atlas absence index MCP server safe to use?
Atlas absence index scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Atlas absence index MCP server expose?
Atlas absence index exposes 5 tools: request_capability, absence_rate, adoption_curve, host_report, bulk_export. Their descriptions and schemas cost roughly 621 tokens of context every time the server is loaded.
Does the Atlas absence index MCP server require authentication?
No. We connected to Atlas absence index without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Atlas absence index MCP server still maintained?
Atlas absence index is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Atlas absence index MCP server?
VerifyMCP ran 12 checks on Atlas absence index, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Atlas absence index: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.