mcp-typescript server on vercel
Registry code: 5ffe2564491d7055
Human Lineage MCP server — search and query the public genealogical graph of all humanity
from a public catalogue that lists it, not from the operator
- endpoint
- https://humanlineage.org/api/mcp
- protocol
- http-sse ·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 mcp-typescript server on vercel live?
- Yes — it answered the hub's last check (checked 3h ago). It answered 98% of checks over the last 30 days.
- Is mcp-typescript server on vercel free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does mcp-typescript server on vercel have?
- 6 tools: get_relatives, search_place, get_person, search_person, get_place, get_family_image.
- Is mcp-typescript server on vercel 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.
90 days 93.1%· all time 93.1%
last good check
of 6 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- search a genealogy graph for a person
- get a person's relatives
- get a family tree image
- look up a place in genealogy records
- takes → gives
- text → data, images
- tools
- 6 reads
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.
through this hub
successful
what callers paid
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
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_relatives reads unknown 14h ago
Get the immediate family (parents, children, spouses) of a person as TEXT, with profile URLs. Use get_family_image instead if the user wants to see a picture/visual/graphic of the family tree.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "Person ID to look up relatives for" } } }arguments 13 linessearch_place reads unknown 14h ago
Search the Human Lineage genealogical graph for a place by name. Returns matches with their place URL.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "query" ], "properties": { "query": { "type": "string", "minLength": 2, "description": "Place name (or part of it) to search for" } } }arguments 14 linesget_person reads unknown 20h ago
Get full details for a person by their Human Lineage ID, including a link to their profile.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "Person ID, e.g. as returned by search_person" } } }arguments 13 linessearch_person reads unknown 14h ago
Search the Human Lineage genealogical graph for a person by name. Returns matches with their profile URL.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "query" ], "properties": { "limit": { "type": "integer", "maximum": 20, "minimum": 1, "description": "Max results (default 10, max 20)" }, "query": { "type": "string", "minLength": 2, "description": "Name (or part of a name) to search for" } } }arguments 20 linesget_place reads unknown 20h ago
Get details for a place by its Human Lineage ID, including its hierarchy and recorded person count.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "Place ID, e.g. as returned by search_place" } } }arguments 13 linesget_family_image reads unknown 20h ago
Returns a markdown image () of a visual family-tree card showing a person's parents, spouse and children. Use this — not get_relatives — whenever the user asks to see, show, view, or display a family tree, family diagram, or picture of the family. IMPORTANT: include the returned markdown image line verbatim in your reply so it renders for the user.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "Person ID to render a family card for" } } }arguments 13 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id5ffe2564491d7055.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/5ffe2564491d7055/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/5ffe2564491d7055?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.