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

bornthen

https://bornthen.life

Registry code: fcd92142143bdda4

api record

Born Then (https://bornthen.life) is a free history life simulator from 1 CE to 2025 weighted by real human births. Use roll_random_birth to draw a birth and get a playable 5-person life link, or query_era_facts to inspect century/decade life expectancy, population, and sourced historical events.

endpoint
https://bornthen.life/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 bornthen live?
Yes — it answered the hub's last check (checked 11m ago). It answered 100% of checks over the last 30 days.
Is bornthen free to use?
Yes — the hub reached it with no key and no payment.
What tools does bornthen have?
2 tools: query_era_facts, roll_random_birth.
Is bornthen 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
91ms

last good check

priced tools
0

of 2 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 2 tools
2 open 2 of 2 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.

  • query_era_facts open 11m ago

    Look up BornThen demographic figures (population, life expectancy, child mortality, literacy, urbanisation, each labelled statistic / estimate / model) and sourced historical events (wars, famines, plagues, depressions) by year, period slug (e.g. "1920s", "14th-century"), place, or event keyword.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "year": {
      "type": "integer",
      "maximum": 2025,
      "minimum": 1,
      "description": "Year between 1 CE and 2025."
    },
    "place": {
      "type": "string",
      "maxLength": 40,
      "description": "ISO3 country code (e.g. \"GBR\", \"CHN\", \"IND\") or historical region id (e.g. \"mesopotamia\", \"north-china\", \"western-europe\")."
    },
    "event_query": {
      "type": "string",
      "maxLength": 80,
      "description": "Keyword or event id to search historical events (e.g. \"black death\", \"great depression\", \"famine\")."
    },
    "period_slug": {
      "type": "string",
      "maxLength": 40,
      "description": "Decade or century slug such as \"1920s\", \"1840s\", \"14th-century\", or \"1st-century\"."
    }
  }
}
    arguments 26 lines
  • roll_random_birth open 11m ago

    Draw a random human birth weighted by how many people were actually born in each place and century/decade between 1 CE and 2025 (or within a chosen year), returning the birthplace, odds, life expectancy, historical events during that lifetime, and a playable BornThen link for those five lives.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "seed": {
      "type": "string",
      "pattern": "^[a-z0-9]{3,24}$",
      "description": "Optional deterministic alphanumeric seed so the same call reproduces the same birth."
    },
    "year": {
      "type": "integer",
      "maximum": 2025,
      "minimum": 1,
      "description": "Optional birth year (1–2025). Omit to draw across all human births since 1 CE."
    }
  }
}
    arguments 16 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 fcd92142143bdda4.

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

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.