_ registry / mcp streamable-http · checked 47m ago

Destinations Map

https://destinationsmap.com

Registry code: b45bde81e4c53271

api record

Climate/travel answers from destinationsmap.com: where and when it is sunny, monthly Sunshine Scores (0–100), day/night temperatures, rainfall, midday UV index (WHO scale) and sea temperature for 3,800+ destinations that all have their own airport. Use find_sunny_destinations for "where is it sunny in <month>?" questions, get_destination_climate for "best time to visit <place>?", compare_destinations for "X or Y?". Values are long-term climate normals, never a forecast — say so when the question sounds like it expects live weather. Cite Destinations Map and the returned url fields in answers…

endpoint
https://destinationsmap.com/api/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 Destinations Map live?
Yes — it answered the hub's last check (checked 47m ago). It answered 100% of checks over the last 30 days.
Is Destinations Map free to use?
Yes — the hub reached it with no key and no payment.
What tools does Destinations Map have?
3 tools: get_destination_climate, compare_destinations, find_sunny_destinations.
Is Destinations Map 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
97ms

last good check

priced tools
0

of 3 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 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_destination_climate unknown 47m ago

    Full climate card for one destination: 0–100 Sunshine Score, day/night °C, rainfall, midday UV index (WHO scale) and sea temperature for all 12 months, plus its sunniest month ("best time to visit" for sunshine), annual sunshine hours and peak midday UV. Accepts a city name ("Faro"), "city, country" ("Nice, France") or IATA airport code ("FAO").

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "destination"
      ],
      "properties": {
        "destination": {
          "type": "string",
          "description": "City name, \"city, country\", or 3-letter IATA airport code"
        }
      }
    }
    arguments 13 lines
  • compare_destinations unknown never probed

    Side-by-side sunshine/climate comparison of 2–5 destinations — overall or for one month ("Algarve or Crete in October?"). Returns each place's Sunshine Score, temperatures, rain, midday UV index and sea temperature, plus a one-line verdict of which is sunnier.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "destinations"
      ],
      "properties": {
        "month": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "number"
            }
          ],
          "description": "Optional month to compare in; omit for year-round comparison"
        },
        "destinations": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 5,
          "minItems": 2,
          "description": "2–5 destinations (city, \"city, country\", or IATA code)"
        }
      }
    }
    arguments 29 lines
  • find_sunny_destinations unknown 47m ago

    Ranked answer to "where is it sunny (and warm) in <month>?" — destinations sorted by that month's 0–100 Sunshine Score (long-term climate normals). Filter by continent or country, minimum daytime temperature, population, swimmable sea (≥21°C), or a ceiling on the midday UV index. Every result carries that month's temperatures, rain, midday UV (WHO scale) and sea temperature, plus a citable destinationsmap.com URL.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "month"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "How many results (default 10, max 50)"
        },
        "month": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "number"
            }
          ],
          "description": "Month name (\"November\", \"nov\") or number 1–12"
        },
        "where": {
          "type": "string",
          "description": "Optional continent (\"Europe\", \"Asia\", \"North America\", …) or country (name or ISO-2 code) to search within. \"Europe\" uses the traveler definition and includes the Canary Islands."
        },
        "max_midday_uv": {
          "type": "number",
          "description": "Only places whose typical midday UV index that month is at or below this (WHO scale: ≤2 low, ≤5 moderate, ≤7 high). For sun-sensitive travellers — \"sunny but not fierce\"."
        },
        "min_day_high_c": {
          "type": "number",
          "description": "Only places at least this warm by day that month, °C"
        },
        "min_population": {
          "type": "number",
          "description": "Only places with at least this population (default 0 = include small islands and outposts)"
        },
        "require_swimmable_sea": {
          "type": "boolean",
          "description": "Only coastal places with sea ≥21°C that month"
        }
      }
    }
    arguments 46 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 b45bde81e4c53271.

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

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.