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

rewindmap

https://rewindmap.com

Registry code: 79c3760593e7aac1

api record

RewindMap historical map data. world_at_year lists documented border snapshots, find_polity retrieves one polity's history, and search_events finds events with optional year or month/day bounds. create_video_link returns a link that opens the site's short-video maker preloaded (years, area, title, labels); the visitor downloads the MP4 from that page. Negative years are BC, with no year 0. Month/day searches exclude events whose source date lacks that precision. Coverage is incomplete; cite returned source attribution and page/map links. Pass lang (the user's language) so links open the…

endpoint
https://rewindmap.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 rewindmap live?
Yes — it answered the hub's last check (checked 1h ago). It answered 98% of checks over the last 30 days.
Is rewindmap free to use?
Yes — the hub reached it with no key and no payment.
What tools does rewindmap have?
4 tools: world_at_year, find_polity, create_video_link, search_events.
Is rewindmap 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
98.3%

90 days 98.8%· all time 98.8%

latency
189ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 424 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • list historical borders in a given year
  • look up a historical state
  • search historical events
  • create a map video link
takes → gives
text → data, web pages
tools
4 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 4 tools
1 open 3 never probed 1 of 4 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.

  • search_events reads open 12h ago

    Search map events: battles (Wikidata), UCDP armed-conflict events since 1989, volcanic eruptions VEI 4+ (Smithsonian GVP), significant earthquakes (NOAA), witnessed meteorite falls, and UNESCO World Heritage sites (undated). Month/day bounds match only events recorded at least that precisely; undated heritage sites match only searches without a date bound. Results are sorted by date.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "bbox": {
          "type": "array",
          "items": {
            "type": "number"
          },
          "maxItems": 4,
          "minItems": 4,
          "description": "Bounding box [west, south, east, north] in degrees."
        },
        "lang": {
          "enum": [
            "en",
            "fr",
            "es",
            "pt",
            "de",
            "it",
            "nl",
            "ja",
            "ru",
            "pl",
            "tr",
            "id",
            "hi",
            "ar"
          ],
          "type": "string",
          "default": "en",
          "description": "Site language for returned page and map links. Use the language the user is writing in."
        },
        "layer": {
          "enum": [
            "conflict",
            "ucdp",
            "volcano",
            "quake",
            "meteorite",
            "heritage"
          ],
          "type": "string"
        },
        "limit": {
          "type": "integer",
          "default": 25,
          "maximum": 100,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "Substring of the event name or detail, e.g. \"Vienna\"."
        },
        "to_date": {
          "type": "object",
          "required": [
            "year",
            "month"
          ],
          "properties": {
            "day": {
              "type": "integer",
              "maximum": 31,
              "minimum": 1
            },
            "year": {
              "type": "integer",
              "description": "Year. Negative is BC: -500 = 500 BC. There is no year 0."
            },
            "month": {
              "type": "integer",
              "maximum": 12,
              "minimum": 1
            }
          },
          "description": "Source-calendar date fields at month precision, or day precision when day is supplied. Historical sources may use Julian dates; bounds compare their recorded fields without calendar conversion."
        },
        "to_year": {
          "type": "integer",
          "description": "Year. Negative is BC: -500 = 500 BC. There is no year 0."
        },
        "from_date": {
          "type": "object",
          "required": [
            "year",
            "month"
          ],
          "properties": {
            "day": {
              "type": "integer",
              "maximum": 31,
              "minimum": 1
            },
            "year": {
              "type": "integer",
              "description": "Year. Negative is BC: -500 = 500 BC. There is no year 0."
            },
            "month": {
              "type": "integer",
              "maximum": 12,
              "minimum": 1
            }
          },
          "description": "Source-calendar date fields at month precision, or day precision when day is supplied. Historical sources may use Julian dates; bounds compare their recorded fields without calendar conversion."
        },
        "from_year": {
          "type": "integer",
          "description": "Year. Negative is BC: -500 = 500 BC. There is no year 0."
        }
      }
    }
    arguments 112 lines
  • world_at_year reads unknown 12h ago

    List states, empires and cultures with an OpenHistoricalMap border snapshot in a given year, optionally overlapping a region. Coverage is incomplete; an empty result does not establish historical absence.

    mcp-tool

    {
      "type": "object",
      "required": [
        "year"
      ],
      "properties": {
        "bbox": {
          "type": "array",
          "items": {
            "type": "number"
          },
          "maxItems": 4,
          "minItems": 4,
          "description": "Bounding box [west, south, east, north] in degrees."
        },
        "lang": {
          "enum": [
            "en",
            "fr",
            "es",
            "pt",
            "de",
            "it",
            "nl",
            "ja",
            "ru",
            "pl",
            "tr",
            "id",
            "hi",
            "ar"
          ],
          "type": "string",
          "default": "en",
          "description": "Site language for returned page and map links. Use the language the user is writing in."
        },
        "year": {
          "type": "integer",
          "description": "Year. Negative is BC: -500 = 500 BC. There is no year 0."
        }
      }
    }
    arguments 42 lines
  • find_polity reads unknown 12h ago

    Look up a state or empire by name or any of its Wikidata labels and aliases (substring, case-insensitive), or by Wikidata QID. Returns its lifespan, every border snapshot with its bounding box, and links.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "lang": {
          "enum": [
            "en",
            "fr",
            "es",
            "pt",
            "de",
            "it",
            "nl",
            "ja",
            "ru",
            "pl",
            "tr",
            "id",
            "hi",
            "ar"
          ],
          "type": "string",
          "default": "en",
          "description": "Site language for returned page and map links. Use the language the user is writing in."
        },
        "query": {
          "type": "string",
          "description": "Name, e.g. \"Ottoman\", or a QID, e.g. \"Q12560\"."
        }
      }
    }
    arguments 33 lines
  • create_video_link reads unknown never probed

    Build a link that opens RewindMap's short-video maker preloaded with a map clip: borders (and optional event layers) changing from one year to another over a place, with an optional title and map labels. The visitor opens the link and taps Download to get a watermarked MP4 (vertical 9:16 for Shorts/Reels/TikTok, or landscape). Rendering happens in the visitor's browser; this tool returns the link only, never a video file.

    mcp-tool

    {
      "type": "object",
      "required": [
        "from_year",
        "to_year"
      ],
      "properties": {
        "bbox": {
          "type": "array",
          "items": {
            "type": "number"
          },
          "maxItems": 4,
          "minItems": 4,
          "description": "Area to frame [west, south, east, north] in degrees. Default: Europe and the Mediterranean."
        },
        "title": {
          "type": "string",
          "maxLength": 60,
          "description": "Text burned into the top of the video."
        },
        "format": {
          "enum": [
            "vertical",
            "landscape"
          ],
          "type": "string",
          "default": "vertical"
        },
        "labels": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "lon",
              "lat",
              "text"
            ],
            "properties": {
              "lat": {
                "type": "number"
              },
              "lon": {
                "type": "number"
              },
              "text": {
                "type": "string",
                "maxLength": 40
              }
            }
          },
          "maxItems": 5,
          "description": "Map labels drawn at fixed points in every frame."
        },
        "layers": {
          "type": "array",
          "items": {
            "enum": [
              "borders",
              "conflict",
              "ucdp",
              "volcano",
              "quake",
              "meteorite",
              "heritage"
            ],
            "type": "string"
          },
          "default": [
            "borders"
          ],
          "description": "Layers shown in the clip."
        },
        "seconds": {
          "enum": [
            6,
            10,
            15
          ],
          "type": "integer",
          "default": 10
        },
        "to_year": {
          "type": "integer",
          "description": "Year. Negative is BC: -500 = 500 BC. There is no year 0."
        },
        "from_year": {
          "type": "integer",
          "description": "Year. Negative is BC: -500 = 500 BC. There is no year 0."
        }
      }
    }
    arguments 92 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 79c3760593e7aac1.

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

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.