humanome
Registry code: 423fa2c04c1693c4
Humanome is a 3D atlas of the human body for anatomy and physiology students. Use its tools to quiz a student with pictures (a structure lit on the 3D body, or a real microscope slide), to look a structure up, and to list what a lab practical asks. When a quiz card is shown, let the student answer in it: do not list the answers in your reply unless they ask for them.
- endpoint
- https://humanome.co/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 humanome live?
- Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
- Is humanome free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does humanome have?
- 4 tools: look_up_anatomy_structure, list_lab_practical_structures, quiz_anatomy_structures, quiz_histology_slides.
- Is humanome 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 100%· all time 100%
last good check
of 4 tools
- unknown → live
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
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.
quiz_histology_slides open 4h ago
Quiz a student on identifying tissues on real microscope slides (epithelial, connective, muscle and nervous tissue): each question shows a slide with its magnification and four tissue names, the wrong ones being tissues that look alike. Use it when a student wants to practise tissue identification or a histology practical.
{ "type": "object", "properties": { "count": { "type": "integer", "default": 5, "maximum": 10, "minimum": 1, "description": "How many slides (1 to 10)." }, "tissue_type": { "enum": [ "all", "epithelial-tissue", "connective-tissue", "muscle-tissue", "nervous-tissue" ], "type": "string", "default": "all", "description": "Which kind of tissue, or all." } }, "additionalProperties": false }arguments 25 lineslook_up_anatomy_structure unknown never probed
Look up one structure of the human body by name (spellings and abbreviations from a lab sheet work too): what it is in one or two sentences, its body system, a picture of it lit on a 3D body, its reference page and the quizzes that ask it. Use it when a student asks what or where a structure is.
{ "type": "object", "required": [ "name" ], "properties": { "name": { "type": "string", "maxLength": 200, "minLength": 2, "description": "The structure's name, e.g. 'deltoid', 'foramen magnum', 'm. sartorius'." } }, "additionalProperties": false }arguments 15 lineslist_lab_practical_structures unknown 4h ago
List the structures an anatomy and physiology lab practical asks, section by section (for example the bones, the muscles, the brain, the heart, blood vessels, the nervous system, A&P 1 or A&P 2), with links to practise each. Use it when a student asks what to study for a lab practical or wants a checklist of structures.
{ "type": "object", "required": [ "practical" ], "properties": { "practical": { "type": "string", "maxLength": 200, "minLength": 2, "description": "The practical or course unit, e.g. 'muscles', 'appendicular skeleton', 'A&P 2'." } }, "additionalProperties": false }arguments 15 linesquiz_anatomy_structures unknown 4h ago
Quiz a student on human anatomy with pictures: each question shows one structure lit up on a 3D human body (a bone, muscle, nerve, vessel, brain part or organ) with four names to choose from. Give a topic in the student's words (a region, a system or a lab practical, such as 'upper limb muscles', 'cranial nerves', 'bones of the skull' or 'muscles lab practical'), or the names on the student's own lab list. Use it when a student asks to be quizzed or tested on anatomy or to practise for an anatomy lab practical. Not for physiology calculations, diseases or medical advice.
{ "type": "object", "properties": { "count": { "type": "integer", "default": 5, "maximum": 10, "minimum": 1, "description": "How many questions (1 to 10)." }, "topic": { "type": "string", "maxLength": 200, "description": "What to be quizzed on, in the student's words: a region, a body system, a structure group or a lab practical." }, "structures": { "type": "array", "items": { "type": "string", "maxLength": 120 }, "maxItems": 150, "description": "A course's own list of structure names to be quizzed on, used instead of a topic." } }, "additionalProperties": false }arguments 27 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 id423fa2c04c1693c4.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/423fa2c04c1693c4/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/423fa2c04c1693c4?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.