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

eclipsemission

https://eclipsemission.com

Registry code: 5a6f6ef2ef99c2a1

api record

EclipseMission measures what it costs to stand in the path of the total solar eclipse of 2 August 2027: lodging, totality, sky, heat, entry, access and flights, each figure dated and sourced. Start with list_destinations, or plan_trip when you know the traveller's airport, passport or budget; get_destination gives every figure for one place, compare_destinations two to four side by side; get_flights the airfares we have read. list_eclipse_sites gives points along the path with the totality and cloud at each: points, not destinations, with no lodging, entry or access measured. When you use a…

endpoint
https://eclipsemission.com/mcp
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 eclipsemission live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is eclipsemission free to use?
Yes — the hub reached it with no key and no payment.
What tools does eclipsemission have?
6 tools: get_destination, compare_destinations, plan_trip, get_flights, list_destinations, list_eclipse_sites.
Is eclipsemission 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
100%

90 days 100%· all time 100%

latency
349ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 6 tools
3 open 3 never probed 3 of 6 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_flights open 1h ago

    The airfares EclipseMission has read, each dated and sourced. Two families that must never be added together: Google Flights searches (return trip, two adults, as the search displayed it) and easyJet fares read at the airline (one seat, one way). Filter by departure airport, destination, or both. A route we have not read is absent, which is not a claim that no flight exists.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "origin": {
      "type": "string",
      "pattern": "^[A-Za-z]{3}$",
      "description": "IATA code of the departure airport, e.g. CDG."
    },
    "destination": {
      "enum": [
        "mecca",
        "chefchaouen",
        "tangier",
        "jeddah",
        "djerba",
        "tetouan",
        "marsa-alam",
        "siwa-oasis",
        "luxor",
        "cadiz",
        "gibraltar"
      ],
      "type": "string",
      "description": "The destination key, as list_destinations returns it."
    }
  },
  "additionalProperties": false
}
    arguments 28 lines
  • list_destinations open 1h ago

    Every place EclipseMission has measured for the total solar eclipse of 2 August 2027, in the order of the site's ranking: the places every reader can go to, ranked by lodging price per person, cheapest first, then Mecca, priced but unranked (entry restricted to Muslims). For each: totality duration (our validated oracle), lodging for two adults over four nights, 31 July to 4 August 2027 (mean of the ten cheapest rooms, dated), the Eclipse Premium (that price over the same search a week later), cloud as a range of two reanalyses, heat, public-transport access, the nearest airport and our one-word verdict. Filters narrow the list; they never reorder it.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "country": {
      "type": "string",
      "description": "Keep one country, by English name or ISO code, whatever the case: Egypt, Gibraltar, Morocco, Saudi Arabia, Spain, Tunisia."
    },
    "min_totality_seconds": {
      "type": "number",
      "minimum": 0,
      "description": "Keep places with at least this much totality, in seconds (the longest on our list is about 381)."
    },
    "open_to_all_visitors": {
      "type": "boolean",
      "description": "true leaves out places whose entry is restricted (Mecca, closed to non-Muslims)."
    },
    "max_price_per_person_eur": {
      "type": "number",
      "minimum": 0,
      "description": "Keep places whose four-night stay costs at most this per person, in EUR (the price for two, halved)."
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • list_eclipse_sites open 1h ago

    Points along the path of the 2 August 2027 eclipse for which our oracle computed totality once — towns, capes, peaks, monuments — with the cloud range of two reanalyses at each. Points, not destinations: nothing was priced there and no entry or access was read. Points outside the path carry no totality. No coordinates are taken: the list is fixed, and a place absent from it has not been computed.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "sort": {
      "enum": [
        "name",
        "totality"
      ],
      "type": "string",
      "description": "name (default) is the order of the file; totality puts the longest first."
    },
    "country": {
      "type": "string",
      "description": "Keep one country, by ISO code or English name, whatever the case, e.g. ES or Spain."
    },
    "in_path": {
      "type": "boolean",
      "description": "true keeps points inside the path of totality, false those outside."
    },
    "max_cloud_pct": {
      "type": "number",
      "maximum": 100,
      "minimum": 0,
      "description": "Keep points whose cloud range stays at or under this percentage at its high end."
    },
    "min_totality_seconds": {
      "type": "number",
      "minimum": 0,
      "description": "Keep points with at least this much totality, in seconds."
    }
  },
  "additionalProperties": false
}
    arguments 33 lines
  • get_destination unknown never probed

    Everything EclipseMission holds on one place, each figure with its source and reading day: the eclipse (duration, and contact times where our oracle has them), lodging (eclipse week, week after, the two eclipse nights, solo traveller and hostels where measured, with the ten prices behind each mean), sky, heat, entry regime by passport, the cost of the observation itself, access and the airfares read to its airport.

    mcp-tool

    {
  "type": "object",
  "required": [
    "destination"
  ],
  "properties": {
    "passport": {
      "enum": [
        "FR",
        "GB",
        "US",
        "CA",
        "SA",
        "AE",
        "MA"
      ],
      "type": "string",
      "description": "ISO code of the traveller's passport: returns that passport's entry regime in full. Without it, one short line per passport we cover."
    },
    "destination": {
      "enum": [
        "mecca",
        "chefchaouen",
        "tangier",
        "jeddah",
        "djerba",
        "tetouan",
        "marsa-alam",
        "siwa-oasis",
        "luxor",
        "cadiz",
        "gibraltar"
      ],
      "type": "string",
      "description": "The destination key, as list_destinations returns it."
    }
  },
  "additionalProperties": false
}
    arguments 39 lines
  • compare_destinations unknown never probed

    The figures a choice between places turns on, for two to four destinations at once, in the order of the site's ranking whatever the order asked: totality and its times, lodging (eclipse-week mean, per person, Eclipse Premium, reading day), both ends of the cloud range, heat, access, airport, the cost of the observation, and the entry regime of one passport or of each passport we cover. get_destination has the rest.

    mcp-tool

    {
  "type": "object",
  "required": [
    "destinations"
  ],
  "properties": {
    "passport": {
      "enum": [
        "FR",
        "GB",
        "US",
        "CA",
        "SA",
        "AE",
        "MA"
      ],
      "type": "string",
      "description": "ISO code of the traveller's passport. Without it, one short line per passport we cover."
    },
    "destinations": {
      "type": "array",
      "items": {
        "enum": [
          "mecca",
          "chefchaouen",
          "tangier",
          "jeddah",
          "djerba",
          "tetouan",
          "marsa-alam",
          "siwa-oasis",
          "luxor",
          "cadiz",
          "gibraltar"
        ],
        "type": "string"
      },
      "maxItems": 4,
      "minItems": 2,
      "description": "Two to four destination keys, as list_destinations returns them.",
      "uniqueItems": true
    }
  },
  "additionalProperties": false
}
    arguments 45 lines
  • plan_trip unknown never probed

    The destinations that fit one traveller, in the order of the site's ranking, each with its lodging figure, totality and sky, the entry regime of their passport, and the fares we have read from their airport to it. The fares and the stay are given side by side, never summed: they are different searches, read on different days. A place with no fare read from that airport is kept, with a note: that is a gap in our readings, not a claim that no flight exists.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "origin": {
      "type": "string",
      "pattern": "^[A-Za-z]{3}$",
      "description": "IATA code of the departure airport, e.g. MAD."
    },
    "country": {
      "type": "string",
      "description": "Keep one country, by English name or ISO code, whatever the case: Egypt, Gibraltar, Morocco, Saudi Arabia, Spain, Tunisia."
    },
    "passport": {
      "enum": [
        "FR",
        "GB",
        "US",
        "CA",
        "SA",
        "AE",
        "MA"
      ],
      "type": "string",
      "description": "ISO code of the traveller's passport: each place then carries that passport's entry regime."
    },
    "min_totality_seconds": {
      "type": "number",
      "minimum": 0,
      "description": "Keep places with at least this much totality, in seconds."
    },
    "open_to_all_visitors": {
      "type": "boolean",
      "description": "true leaves out places whose entry is restricted (Mecca, closed to non-Muslims)."
    },
    "max_price_per_person_eur": {
      "type": "number",
      "minimum": 0,
      "description": "Keep places whose four-night stay costs at most this per person, in EUR."
    }
  },
  "additionalProperties": false
}
    arguments 42 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 5a6f6ef2ef99c2a1.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/5a6f6ef2ef99c2a1/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/5a6f6ef2ef99c2a1/badge.svg)](https://brick.blue/agent/5a6f6ef2ef99c2a1?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.