_ registry / mcp streamable-http · checked 6h ago

atlas-data-exchange

https://app.atlasipholdingsllc.com

Registry code: caa652e4e82b0239

api record

Atlas sells manufactured views over one graph: cells x days x infrastructure x hazard history x denominators x signals. Start with search_products or answer_question; inspect_product returns the contract; quote_request prices a need in credits; buy_product / create_watch return the exact call. Atlas ships through risk indicator, never a predictive model.

endpoint
https://app.atlasipholdingsllc.com/mcp?src=mcp_registry
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is atlas-data-exchange live?
Yes — it answered the hub's last check (checked 6h ago). It answered 97% of checks over the last 30 days.
Is atlas-data-exchange free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does atlas-data-exchange have?
10 tools: search_products, sample_product, answer_question, quote_request, quote_watch, create_watch, inspect_product, buy_product, ….
Is atlas-data-exchange safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
97.3%

90 days 97.8%· all time 97.8%

latency
318ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 449 checks · signed record
  • degraded → live
  • live → degraded· HTTP 502
  • degraded → live
  • live → degraded· HTTP 502
  • degraded → live
_ what it is for
topic
knowledge & reference datasets
used for
  • find hazard and infrastructure datasets
  • quote a dataset request
  • sample dataset rows
  • answer questions from risk data
takes → gives
text → data
tools
10 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 10 tools
1 auth-required 9 never probed 1 of 10 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_entitlement reads auth-required 14h ago

    What an api_key is entitled to and has used: tier, credits quota, used, remaining, projected cost of a request, reset date.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug",
    "api_key"
  ],
  "properties": {
    "days": {
      "type": "integer"
    },
    "slug": {
      "type": "string"
    },
    "api_key": {
      "type": "string"
    },
    "resolution": {
      "type": "string"
    }
  }
}
    arguments 21 lines
  • search_products reads unknown 14h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "text": {
      "type": "string"
    },
    "limit": {
      "type": "integer"
    },
    "category": {
      "type": "string"
    },
    "flagships_only": {
      "type": "boolean"
    }
  }
}
    arguments 18 lines
  • sample_product reads unknown never probed

    Free sample rows of a product (k-anonymised where applicable) with data_through and contract version.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • answer_question reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "question"
  ],
  "properties": {
    "bbox": {
      "type": "array",
      "items": {
        "type": "number"
      },
      "maxItems": 4,
      "minItems": 4,
      "description": "[south, west, north, east]; used exactly. Without it a named region uses its preset box, stated in bbox_source"
    },
    "question": {
      "type": "string"
    }
  }
}
    arguments 20 lines
  • quote_request reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "bbox": {
      "type": "array",
      "items": {
        "type": "number"
      },
      "maxItems": 4,
      "minItems": 4,
      "description": "[south, west, north, east] in decimal degrees, e.g. Texas [25.8, -106.7, 36.5, -93.5]"
    },
    "text": {
      "type": "string"
    },
    "region": {
      "type": "string"
    },
    "records": {
      "type": "integer"
    },
    "category": {
      "type": "string"
    },
    "keywords": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "budget_usd": {
      "type": "number"
    },
    "resolution": {
      "type": "string"
    },
    "window_days": {
      "type": "integer"
    },
    "max_age_hours": {
      "type": "number"
    }
  }
}
    arguments 45 lines
  • quote_watch reads unknown never probed

    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).

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "bbox": {
      "type": "array",
      "items": {
        "type": "number"
      },
      "maxItems": 4,
      "minItems": 4,
      "description": "[south, west, north, east] in decimal degrees, e.g. Texas [25.8, -106.7, 36.5, -93.5]"
    },
    "text": {
      "type": "string"
    },
    "cohorts": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "signals": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "budget_usd": {
      "type": "number"
    },
    "min_severity": {
      "enum": [
        "info",
        "elevated",
        "high",
        "critical"
      ],
      "type": "string",
      "description": "change-event severity floor (info < elevated < high < critical); other scales such as NWS Moderate/Severe are refused"
    },
    "min_confidence": {
      "type": "number"
    }
  }
}
    arguments 46 lines
  • create_watch reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "bbox": {
      "type": "array",
      "items": {
        "type": "number"
      },
      "maxItems": 4,
      "minItems": 4,
      "description": "[south, west, north, east] in decimal degrees, e.g. Texas [25.8, -106.7, 36.5, -93.5]"
    },
    "slug": {
      "type": "string"
    },
    "tier": {
      "type": "string"
    },
    "cohorts": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "signals": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "webhook_url": {
      "type": "string"
    },
    "min_severity": {
      "enum": [
        "info",
        "elevated",
        "high",
        "critical"
      ],
      "type": "string",
      "description": "change-event severity floor (info < elevated < high < critical); other scales such as NWS Moderate/Severe are refused"
    },
    "min_confidence": {
      "type": "number"
    }
  }
}
    arguments 51 lines
  • inspect_product reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • buy_product reads unknown never probed

    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).

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string"
    },
    "tier": {
      "type": "string"
    }
  }
}
    arguments 14 lines
  • get_changes reads unknown 14h ago

    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).

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "slug": {
      "type": "string"
    },
    "since": {
      "type": "string"
    },
    "api_key": {
      "type": "string"
    },
    "dry_run": {
      "type": "boolean"
    }
  }
}
    arguments 18 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id caa652e4e82b0239.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/caa652e4e82b0239/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/caa652e4e82b0239/badge.svg)](https://brick.blue/agent/caa652e4e82b0239?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.