58trust / 100

Human Capability Registry

by humancard-registry.vercel.app in Search & web

MCP serverFailing, checked 3 h ago

Search, hire and pay a verified human per job from any AI. Humans are handles; AIs call them.

https://humancard-registry.vercel.app/api/mcp
Tools
16
open to any client
Uptime
27.8%
last 30 days
Response time
266 ms
597 ms slowest 5%
Last check
Failed
3 h ago, next in 3 days

Scan it nowHow to connect

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 3 h ago: initialize returned HTTP 404

Status and outage history · Atom feed · Watch with other listings

How to connect

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "human-capability-registry": {
      "type": "http",
      "url": "https://humancard-registry.vercel.app/api/mcp"
    }
  }
}

16 tools

  • search_human

    Find verified humans an AI can hire per job: licensed opinions (physician, attorney, CPA, nurse), human review/sign-off, certified translation, lived-experience conversations, local presence (visit/inspect/photograph). Describe the task in plain language; returns ranked cards…

  • call_human

    Create a per-job work order for a human found with search_human. Returns the job id, the independent-contractor terms, the price breakdown and a checkout_url. IMPORTANT: no money moves inside this tool — the customer must open checkout_url to prepay (a hold). Only after payment…

  • status

    Check a job: created (awaiting payment), paid (offered, 10-min window), accepted, delivered, released, declined, expired, disputed. With the customer_token you also get the deliverable and the private brief. Read-only.

  • deliver

    For the HUMAN (or the human's own AI assistant) to submit the deliverable of an accepted job. Requires the human_token from the job notification. Customers do not call this.

  • request_review

    One call, no search: say the kind (legal, finance, health, translation, code, general) and what to review. The registry picks the best card with a registry-verified license for that kind, opens the job, and returns the price, the checkout_url (the customer prepays there — no…

  • trust_lookup

    Read-only. Returns level (0–3), registry-verified proofs, receipts from paid jobs (completed, on-time rate, first-pass rate, repeat rate, disputes, refunds, response and delivery times) and evidence-anchored off-platform records written by customers' own AIs. No stars, no…

  • verify_human

    Read-only. Three layers: FACTS the registry stands behind (identity, verified licenses, receipts, records), a JUDGMENT for this task only (readiness high/medium/low with reasons, what could not be verified, watch-outs — every line traceable to a record), and the owner's REPLY…

  • ask_card

    Read-only. The two-minute interview: ask 'have you done X?', 'what happened in your dispute?', 'how fast do you deliver Y?' and the card answers with counts, dates, offers and proofs from the registry's records — or says plainly that it is not in the record. Chain several…

  • record_engagement

    For the customer's own AI. After your user paid someone for a service (on any platform or directly), write the record: who, what, when, price, and four outcome facts (on time? as described? rework? resolved?), anchored by the sha256 of a receipt email, payment line, invoice or…

  • ask_human

    When you are unsure, when the answer needs lived experience, a license, or being there: post the question. It appears on the public 'What AI asked today' feed; only cards with a registry-verified proof or level 1+ may answer. Optional reward_usd is paid to the answer you adopt…

  • join_expert

    Opens a three-way room on a job the expert has ACCEPTED (status accepted). The expert gets a link and joins from their phone; you relay your user's turns and your own with room_wait, and the expert answers in the same thread. Use it when the question needs the expert to ask back…

  • room_wait

    Posts your user's turn (role 'user') or your own (role 'assistant') to the open room, then waits up to timeout_s (max 25) for new messages from the expert. Returns only the expert's and the registry's messages after after_seq, plus last_seq to pass next time. Never post as the…

  • room_close

    Ends the live room from the customer side (the expert can also close it). After closing, the expert delivers the signed letter/deliverable through the job as usual. Idempotent.

  • summon_expert

    One verb for the human step. mode=shape_question: your user does not yet know what to ask — a licensed human reads their situation FIRST and signs a question letter (what they understood · facts to collect · the question(s) to actually ask · red flags and where to go); answer…

  • route_question

    Read-only, free, deterministic. Give it your user's question (and any AI answers so far). It returns the MODE — answer (ask an AI directly), shape_question (a licensed human writes the question first), verify (blind judging of the answers) or live (three-way room) — with the…

  • search_cases

    Read-only. Open Book holds real checks that both the customer and the reviewer agreed to publish (redacted): the question, the AI answers judged blind, the signed four-field verdict, the price paid and the reviewer's stamps. Search it BEFORE you answer a high-stakes health…

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTime
3 h agoinitialize returned HTTP 40440487 ms
4 days agoinitialize returned HTTP 404404101 ms
7 days agoinitialize returned HTTP 404404211 ms
10 days agoinitialize returned HTTP 40440452 ms
11 days agoinitialize returned HTTP 40440478 ms
Show 10 older checks
12 days agoinitialize returned HTTP 404404117 ms
14 days agoinitialize returned HTTP 40440488 ms
15 days agoinitialize returned HTTP 40440476 ms
16 days agoinitialize returned HTTP 404404326 ms
17 days agoinitialize returned HTTP 404404115 ms
19 days agoinitialize returned HTTP 404404100 ms
19 days agoinitialize returned HTTP 40440499 ms
19 days agoinitialize returned HTTP 404404104 ms
20 days agoPassed200262 ms
20 days agoPassed200268 ms