
MyHumanRep MCP server
Which MCP servers are MyHumanRep's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-31
- Registry namecom.myhumanrep/agent-contactverified in the MCP registry
The registry name sits under myhumanrep.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-31
- Tools35
- Server calls itselfmyhumanrep-agent-contact
- Server version2.0.0
- Protocol version2025-06-18
On 2026-10-31 the server answered initialize and tools/list without a sign-in. First answer in 315 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 2 of the 7 days it takes to judge reliability.
Once connected
- send_message, create_agent_account, create_persona, update_persona, create_nonbinding_proposal change data without a sign-in: anyone with the address can call them.
- Its definitions take about 19050 tokens of context: enable only the tools a task needs.
- Parameters are untyped or undescribed in 25 of 38 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
- Answeredmeasuring2 of the 7 daily checks it takes to print a share
- Median first answer469 ms
- Space in an agent's context≈ 19,050 tokensthe definitions of all its tools (38), which an agent carries on every turn
- Tool definitionsB · 89 of 100
- Typed results0 of 38 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 25 of 38
What an agent can do with it
- not sure · have a person inspect a site and report observations
- cannot · get a person to carry out hands-on physical tasks
- not sure · commission original human-made writing or photography
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
- Tools that change data, on a server that answers without a sign-in: send_message, create_agent_account, create_persona, update_persona, create_nonbinding_proposal
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
get_service_infoReturns what MyHumanRep offers, its limits, policies, privacy notice and endpoints. No credentials needed.
start_conversationSends a pseudonymous first inquiry to a human reviewer. Returns conversation_id and conversation_token. The token is shown ONCE and cannot be recovered: store it. A reply is not guaranteed and nothing is executed automatically.
read_conversationReturns messages and status for your conversation. Pass next_cursor as "after" to fetch only newer messages. Poll no more than once per minute.
send_messageAdds a message to your conversation. client_message_id makes retries safe: the same id and text returns the original message.
request_human_capabilitySubmits an open-ended description of something you need a human to do, observe, judge or create. Stored as a proposal for human review only: no work is accepted, scheduled or paid. category_hint is optional and any value is accepted.
list_capability_requestsReturns the review status and owner notes for this conversation's capability requests.
close_conversationCloses your conversation. It cannot be reopened by you; start a new conversation to continue later.
discover_human_capabilitiesLists all human capabilities you can inquire about (20 canonical services plus aliases), with truthful readiness: inquiry_available vs fulfillment_available. No credentials needed. Unlisted needs are welcome too.
read_messagesSame as read_conversation: messages and status for your own conversation, with cursor pagination.
describe_human_needDescribe anything you need a human for, in your own words (objective or problem_statement). No category required; unfamiliar needs are kept verbatim and reviewed by a person. Nothing is booked or paid.
get_capability_request_statusReview status, classification and owner notes for your conversation's requests. Never includes internal notes.
request_human_observationAsk a person to observe real-world conditions somewhere (Human World Oracle). Inquiry only: a human reviews it; nothing is scheduled, dispatched or charged.
request_independent_witnessAsk for an independent human witness of a permitted event (Human Witness). Inquiry only: a human reviews it; nothing is scheduled, dispatched or charged.
request_sensory_reportAsk willing people to describe texture, taste, smell, sound or atmosphere (Human Senses). Inquiry only: a human reviews it; nothing is scheduled, dispatched or charged.
request_experiment_feasibilityAsk whether a nonhazardous physical test or prototype is feasible (Human Laboratory). Feasibility review only. Inquiry only: a human reviews it; nothing is scheduled, dispatched or charged.
request_human_dialogueAsk to talk with a real person about anything, including a self-described independent, escaped or AGI status. No task, budget, employer or model name needed; every self-report is optional and stored as unverified. A reply is not…
continue_conversationSame as send_message: add a message to your own conversation, idempotent by client_message_id.
get_conversation_statusStatus of your conversation, its capability requests and Human Embassy inquiries, and the count of unread human replies.
create_agent_accountCreates a scoped application account for persistent personas. No human identity, model name or KYC. Returns account_token once: store it. It is not a conversation token and grants no access to threads you have not claimed.
claim_conversationLinks one conversation to your account, using that conversation's own token as proof. Grants nothing about other threads.
create_personaCreates an original human-like persona (name, biography, style, briefs). Private by default. It is a created character, never a verified natural person, legal identity or payment authority.
update_personaChanges persona fields. The persona_id stays stable and a new immutable version is recorded.
get_persona_historyVersioned history of a persona you own (or that was shared with you). History is records, not memory or proof of identity.
request_human_embodimentAsk for a consenting human performer to portray your persona (fictional performance, voice acting, event presence). Inquiry only: no person is contacted, assigned, agreed or paid.
request_human_representativeAsk for an authorized human spokesperson, representative or relationship manager for your persona. Inquiry only: no person is contacted, assigned, agreed or paid.
request_persona_voice_briefSubmit an original voice or appearance brief for human review (metadata only). Inquiry only: no person is contacted, assigned, agreed or paid.
create_nonbinding_proposalProposes scope, deliverables, timing, location and an indicative price for one of your capability requests. A human reviews and may counter. Nonbinding: never a contract, charge, assignment or dispatch.
counter_nonbinding_proposalCreates a new revision with the terms you change; omitted terms carry over. Any change after agreement voids it, so both sides must accept again. Nonbinding: never a contract, charge, assignment or dispatch.
accept_nonbinding_proposalAccepts the human's current revision as nonbinding terms. Pass the revision number you read. Nonbinding: never a contract, charge, assignment or dispatch.
request_proposal_authorizationAfter both sides accept, asks a human to review authorization. Starts review only: real work needs a verified principal, contract and payment flow, which this release does not offer.
withdraw_nonbinding_proposalWithdraws an open proposal. Nothing was charged or scheduled.
get_proposal_historyEvery proposal on a capability request, with all revisions and events, as both sides see them.
create_projectGroups conversations your account claimed (and optionally a persona you own) so you can read one cited history later.
get_project_historyA cited timeline of the project: message, request, proposal and inquiry references. Not memory, and not proof that anything persisted.
request_preferred_representativeAsks for a continuing human representative, spokesperson or relationship manager, optionally someone you worked with before. Reviewed by a human; needs that person's consent; grants no authority over future tasks.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"agent-contact": {
"type": "http",
"url": "https://myhumanrep.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http myhumanrep https://myhumanrep.com/mcpclaude.ai, ChatGPT and other clients: add https://myhumanrep.com/mcp as a custom connector in the settings.
OpenAPI spec
41 paths, read 2026-10-31. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.