Atlas Data Exchange
REMOTE · APP.ATLASIPHOLDINGSLLC.COM
Infrastructure and hazard intelligence with provenance, spatial confidence and quality contracts.
Available components
Last scanned (2 hours ago)
Scores higher than 68% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
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 Security66
- 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 10 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1131 tokens (~113/item across 10 items; 10 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 Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 14% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 31 Oct 26 +53
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 30 Oct 26 −53
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 15 Oct 26 0
- Stability: 0.97 → pass security
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
- DNSSEC: fail → pass ▲ security
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 90. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://app.atlasipholdingsllc.com/mcp?src=mcp_registry
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.atlasipholdingsllc.com | CN=WE1,O=Google Trust Services,C=US | 22 Oct 2026 | 20 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 1d9d53c190481dd70ebadde36c5e4a6d |
| SANs: app.atlasipholdingsllc.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of app.atlasipholdingsllc.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| atlasipholdingsllc.com. | present | 2371 | 13 | Verified |
| app.atlasipholdingsllc.com. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | default-src 'self' https: data:; script-src 'self' 'unsafe-inline' https:; style-src 'self' 'unsafe-inline' https:; img-src 'self' data: blob: https:; object-src 'none'; frame-ancestors 'self'; base-uri 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.atlasipholdingsllc.com/mcp?src=mcp_registry | Verified | 200 | |
| http (plaintext) | http://app.atlasipholdingsllc.com/mcp?src=mcp_registry | HTTPS enforced | 301 | https://app.atlasipholdingsllc.com/mcp?src=mcp_registry |
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 →
answer_question ~89
Ask a question Atlas can answer live (seismic unusual in a region, wave energy, commodity regimes, logistics safety, what cells are alert-worthy). Returns verdict, evidence, datasets and the purchase path.
| Name | Type | Req | Description |
|---|---|---|---|
| bbox | array | – | [south, west, north, east]; used exactly. Without it a named region uses its preset box, stated in bbox_source |
| question | string | yes | – |
No output schema declared.
No examples provided.
buy_product ~81
The exact purchase call for a product and tier (one-time pack via POST /api/datapacks/buy, subscription via POST /api/feeds/subscribe), with terms, idempotency and what is metered. Does not move money: purchases need a session (or Stripe checkout).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
| tier | string | – | – |
No output schema declared.
No examples provided.
create_watch ~165
The exact subscribe call for a watch (mode=watch) with the filters given, its tier, price and metering, plus the webhook contract. Does not move money.
| Name | Type | Req | Description |
|---|---|---|---|
| bbox | array | – | [south, west, north, east] in decimal degrees, e.g. Texas [25.8, -106.7, 36.5, -93.5] |
| cohorts | array | – | – |
| min_confidence | number | – | – |
| min_severity | string | – | change-event severity floor (info < elevated < high < critical); other scales such as NWS Moderate/Severe are refused |
| signals | array | – | – |
| slug | string | yes | – |
| tier | string | – | – |
| webhook_url | string | – | – |
No output schema declared.
No examples provided.
get_changes ~90
Change events since a cursor. Anonymous: the latest-day preview, at most 10 events (limit_applied/limit_max in the response). With api_key: the metered signal feed for that subscription (GET /api/feeds/{slug}/changes).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | – |
| dry_run | boolean | – | – |
| since | string | – | – |
| slug | string | – | – |
No output schema declared.
No examples provided.
get_entitlement ~67
What an api_key is entitled to and has used: tier, credits quota, used, remaining, projected cost of a request, reset date.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | – |
| days | integer | – | – |
| resolution | string | – | – |
| slug | string | yes | – |
No output schema declared.
No examples provided.
inspect_product ~57
The full machine-readable commercial contract of one product: pricing ladder, credit multipliers, views, schema, measured quality, SLOs, provenance, join quality, semantics (ships through risk indicator), limitations.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
quote_request ~171
Quote a dataset need: text / keywords / category, max_age_hours, budget_usd, resolution, window_days, records, region or bbox. Returns ranked products with the cheapest fitting tier, estimated records and credits, cost, and the exact purchase call.
| Name | Type | Req | Description |
|---|---|---|---|
| bbox | array | – | [south, west, north, east] in decimal degrees, e.g. Texas [25.8, -106.7, 36.5, -93.5] |
| budget_usd | number | – | – |
| category | string | – | – |
| keywords | array | – | – |
| max_age_hours | number | – | – |
| records | integer | – | – |
| region | string | – | – |
| resolution | string | – | – |
| text | string | – | – |
| window_days | integer | – | – |
No output schema declared.
No examples provided.
quote_watch ~192
Quote a watch (signal feed): need text plus filters (bbox, cohorts, signals, min_severity, min_confidence) -> product (ranked like quote_request, among packs with the cell layer), cheapest tier that meets the need, best tier within budget, estimated events per month and credits (watch events cost 5 credits).
| Name | Type | Req | Description |
|---|---|---|---|
| bbox | array | – | [south, west, north, east] in decimal degrees, e.g. Texas [25.8, -106.7, 36.5, -93.5] |
| budget_usd | number | – | – |
| cohorts | array | – | – |
| min_confidence | number | – | – |
| min_severity | string | – | change-event severity floor (info < elevated < high < critical); other scales such as NWS Moderate/Severe are refused |
| signals | array | – | – |
| text | string | – | – |
No output schema declared.
No examples provided.
sample_product ~37
Free sample rows of a product (k-anonymised where applicable) with data_through and contract version.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
search_products ~114
SEMANTIC product discovery: describe the need in plain words (industry, infrastructure type, hazard, question) and get products ranked by profile match (answers_questions, use_cases, industries, infrastructure_types, hazard_classes, example_questions), with the matched terms, what each product is NOT for, its temporal/spatial coverage, the cheapest satisfying tier, quality status and contract URL.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| flagships_only | boolean | – | – |
| limit | integer | – | – |
| text | string | – | – |
No output schema declared.
No examples provided.
How do I install the Atlas Data Exchange MCP server?
Atlas Data Exchange is a hosted endpoint at https://app.atlasipholdingsllc.com/mcp?src=mcp_registry, 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 · app.atlasipholdingsllc.com
claude mcp add --transport http com-atlasipholdingsllc-app-atlas-data-exchange 'https://app.atlasipholdingsllc.com/mcp?src=mcp_registry'
What is the Atlas Data Exchange MCP server?
Atlas Data Exchange is an MCP server listed in the public MCP registry as com.atlasipholdingsllc.app/atlas-data-exchange. Infrastructure and hazard intelligence with provenance, spatial confidence and quality contracts. This page covers its hosted endpoint (https://app.atlasipholdingsllc.com/mcp?src=mcp_registry).
Is the Atlas Data Exchange MCP server safe to use?
Atlas Data Exchange scores 77 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 Data Exchange MCP server expose?
Atlas Data Exchange exposes 10 tools: search_products, inspect_product, sample_product, answer_question, quote_request, and 5 more. Their descriptions and schemas cost roughly 1,063 tokens of context every time the server is loaded.
Does the Atlas Data Exchange MCP server require authentication?
No. We connected to Atlas Data Exchange without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Atlas Data Exchange MCP server still maintained?
Atlas Data Exchange is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.