HumanReviewed docs

MCP server

Connect Claude or another MCP client to HumanReviewed. Verify anything anonymously; request reviews once paired to an organization.

Connect

bash
claude mcp add --transport http humanreviewed https://api.humanreviewed.ai/mcp

Verification tools work with no auth. To request reviews, pair the client to your org: in the console open Settings → Connected AI assistants, generate a pairing code, and paste it when the client runs its pairing step. The client receives a token scoped to your organization.

Tools

ToolTier
verify_attestationpublic
get_attestation, get_signer_identitypublic
hash_artefact (runs locally)public
get_badge_links, get_compliance_packpublic
get_request_status, list_review_requests, list_attestationsread
request_reviewwrite
No submit_review — by design
There is deliberately no tool for an AI to submit a review. An assistant can request that a human review something; only a human signs. Letting an agent attest “a human reviewed this” would defeat the entire standard.

Auth model

The long-lived pairing token (hrmcp_…) is hashed at rest and shown once. Each request mints a short-lived JWT that the API resolves through the same auth path as an API key — so MCP adds no new authorization surface. Revoke a connection in the console; access dies within a minute. Read-only pairings cannot call request_review.