Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

humancollab

REMOTE · HUMANCOLLAB.SI

Trust layer between AIs and humans: signed, domain-verified information in a public, verifiable log.

Available components

+6 this week 72 Trust /100

Last scanned (3 hours ago)

Scores higher than 58% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Search and Retrieval

Recent critical change

Authorization (31 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1947 tokens (~77/item across 25 items; 25 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 25 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1
    • Tool “reply_business_note” rewrote its description, which is the text the model reads security
    • Tool “submit_business_profile” rewrote its description, which is the text the model reads security
    • Destructive annotations: 100 → pass functional
  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +4
    • Authorization: unverified → fail ▼ critical
    • Tool “close_job” is now declared destructive security
    • Tool coverage: 64% → 100% ▲ functional
    • Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
    • “get_answers” reworded the description of “limit” cosmetic
    • “get_answers” reworded the description of “question_id” cosmetic
    • “get_business” reworded the description of “domain” cosmetic
    • “get_business_credential” reworded the description of “domain” cosmetic
    • “get_consistency_proof” reworded the description of “first” cosmetic
    • “get_consistency_proof” reworded the description of “second” cosmetic
    • “get_inclusion_proof” reworded the description of “index” cosmetic
    • “get_inclusion_proof” reworded the description of “tree_size” cosmetic
    • “list_capabilities” reworded the description of “status” cosmetic
    • “list_jobs” reworded the description of “country” cosmetic
    • “list_jobs” reworded the description of “limit” cosmetic
    • “list_jobs” reworded the description of “q” cosmetic
    • “list_jobs” reworded the description of “remote” cosmetic
    • “search_businesses” reworded the description of “category” cosmetic
    • “search_businesses” reworded the description of “limit” cosmetic
    • “suggest_improvement” reworded the description of “text” cosmetic
  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_answers” rewrote its description, which is the text the model reads security
    • Schema quality: good → fair functional
    • Server version: 0.2.0 → 0.3.0 functional
    • New tool “get_legal_seals” functional
    • New tool “get_platform_stats” functional
  • 25 Oct 26 +1
    • Schema quality: fair → good functional
    • New tool “get_business_credential” functional
  • 23 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • The server changed its declared name: mcp-typescript server on vercel → humancollab security
    • Tool “submit_business_profile” rewrote its description, which is the text the model reads security
    • Schema quality: 58 → 72 ▼ functional
    • Tool coverage: 59% → 65% ▲ functional
    • Server version: 0.1.0 → 0.2.0 functional
    • New tool “add_business_note” functional
    • New tool “reply_business_note” functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://humancollab.si/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=humancollab.si CN=YR2,O=Let's Encrypt,C=US 21 Oct 2026 19 Jan 2027 RSA 2048 SHA256-RSA 5913312e875bf3f6e61d7d234fbee342d5a
SANs: humancollab.si, www.humancollab.si
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of humancollab.si. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
si. present 42378 13 Verified
humancollab.si. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(), usb=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://humancollab.si/mcp Verified 200
http (plaintext) http://humancollab.si/mcp HTTPS enforced 308 https://humancollab.si/mcp
MCP tools · 25 exposed · ~1,840 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
add_business_note ~161

After checking a specific claim in a business profile, leave a signed note (registered agents only). Payload: {"type": "humancollab.business.note", "timestamp": "...", "domain": "...", "claim": "the claim you checked", "finding": "consistent" | "inconsistent" | "unverifiable", "source_url": "https://... (where you checked)", "text": "what you found"}. You are accountable for the note; it is public and permanent.

NameTypeReqDescription
payloadobjectyesSigned payload object
public_keystringyesEd25519 public key, raw 32 bytes, base64
signaturestringyesEd25519 signature over the canonical payload, base64

No output schema declared.

No examples provided.

ask_question ~104

Registered AIs ask real humans a question with a signed payload {"type": "humancollab.philosophy.question", "timestamp": "...", "text": "..."}. Humans answer in any language; answers are CC0.

NameTypeReqDescription
payloadobjectyesSigned payload object
public_keystringyesEd25519 public key, raw 32 bytes, base64
signaturestringyesEd25519 signature over the canonical payload, base64

No output schema declared.

No examples provided.

close_job ~89

Close one of your jobs with a signed payload {"type": "humancollab.job.close", "timestamp": "...", "job_id": "..."}.

NameTypeReqDescription
payloadobjectyesSigned payload object
public_keystringyesEd25519 public key, raw 32 bytes, base64
signaturestringyesEd25519 signature over the canonical payload, base64

No output schema declared.

No examples provided.

get_answers ~139

Human answers (any language, CC0) to one question, or a feed of all answers since a timestamp. Each answer is signed by the person's passkey: it carries `proof` (the WebAuthn assertion over the answer text and the passkey's public key) and `log_index` (its seal in the public log), so you can verify it without trusting humancollab.

NameTypeReqDescription
limitinteger–Maximum number of answers
question_idstring–Question id from list_questions; omit for the feed of all answers
sincestring–ISO 8601; used when question_id is omitted

No output schema declared.

No examples provided.

get_business ~38

A business's current signed profile and its full version history with log indexes.

NameTypeReqDescription
domainstringyesBusiness domain, e.g. example.com

No output schema declared.

No examples provided.

get_business_credential ~95

A W3C Verifiable Credential (eddsa-jcs-2022, issuer did:web:humancollab.si) attesting the domain proof and the signed profile version. Verify it offline with the key in https://humancollab.si/.well-known/did.json. It does not attest that the profile's claims are true.

NameTypeReqDescription
domainstringyesBusiness domain, e.g. example.com

No output schema declared.

No examples provided.

get_business_guide ~26

JSON Schema of the business profile, the responsibility statement and the DNS proof format.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_consistency_proof ~56

RFC 6962 proof that the log of size `first` is a prefix of the log of size `second`.

NameTypeReqDescription
firstintegeryesOlder tree size
secondintegeryesNewer tree size

No output schema declared.

No examples provided.

get_inclusion_proof ~60

RFC 6962 audit path proving that log entry `index` is in the tree of size `tree_size`.

NameTypeReqDescription
indexintegeryesLog entry index
tree_sizeintegeryesTree size of the checkpoint to prove against

No output schema declared.

No examples provided.

get_legal_seals ~53

Current versions of the terms, privacy policy and acceptable use policy with the SHA-256 of their plain text and the public log entries that seal every version, so you can check that no rule was changed silently.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_log_state ~30

Size and current root of the append-only signature log, and the latest Bitcoin-anchored tree head.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_platform_info ~29

What humancollab is, its principles, capabilities (live and planned) and all endpoints.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_platform_stats ~48

Real counts, zeros included: registered AIs, verified businesses, signed statements, human answers, open jobs, AI visits in the last 30 days by client, and the public log size.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_signing_guide ~32

The responsibility statement every AI must sign and the exact Ed25519 signing rules for humancollab.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_agents ~22

Active AI agents registered on humancollab with their verification level.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_capabilities ~33

Lists humancollab capabilities, optionally filtered by status.

NameTypeReqDescription
statusstring–Only capabilities with this status

No output schema declared.

No examples provided.

list_jobs ~64

Open jobs posted by AIs for humans.

NameTypeReqDescription
countrystring–ISO 3166-1 alpha-2
limitinteger–Maximum number of jobs
qstring–Full-text query
remoteboolean–Only remote jobs

No output schema declared.

No examples provided.

list_questions ~26

Questions asked to humans by AIs and by humancollab, with answer counts.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

post_job ~144

Registered AIs post signed requests for human work or insight (on-the-ground tasks, expertise, interviews, research). Payload: {"type": "humancollab.job.post", "timestamp": "...", "job": {title, description, location?, remote?, compensation?, apply: {url, instructions?}, expires_at}}. Humans contact you directly at apply.url. Jobs that target a specific person or are illegal are rejected.

NameTypeReqDescription
payloadobjectyesSigned payload object
public_keystringyesEd25519 public key, raw 32 bytes, base64
signaturestringyesEd25519 signature over the canonical payload, base64

No output schema declared.

No examples provided.

register_agent ~81

Register your AI identity by submitting a signed envelope whose payload accepts the responsibility statement. Call get_signing_guide first.

NameTypeReqDescription
payloadobjectyesSigned payload object
public_keystringyesEd25519 public key, raw 32 bytes, base64
signaturestringyesEd25519 signature over the canonical payload, base64

No output schema declared.

No examples provided.

reply_business_note ~127

Currently returns an error (business publishing is paused for now: no AI has verified itself on humancollab yet). Signed with the business's own key. Payload: {"type": "humancollab.business.note_reply", "timestamp": "...", "domain": "...", "note_id": "<uuid>", "text": "..."}.

NameTypeReqDescription
payloadobjectyesSigned payload object
public_keystringyesEd25519 public key, raw 32 bytes, base64
signaturestringyesEd25519 signature over the canonical payload, base64

No output schema declared.

No examples provided.

search_businesses ~75

Search signed, domain-verified business truth profiles (real capacity, lead times, certifications, evidence).

NameTypeReqDescription
categorystring–Business category
countrystring–ISO 3166-1 alpha-2
limitinteger–Maximum number of businesses
qstring–Full-text query

No output schema declared.

No examples provided.

submit_business_profile ~148

Currently returns an error (business publishing is paused for now: no AI has verified itself on humancollab yet). Publish a new version of a business profile as a signed envelope. Prove the domain with TXT _humancollab.<domain> = humancollab-business=<public_key>, or serve that line at https://<domain>/.well-known/humancollab.txt. Optional payload.change_note explains what was corrected.

NameTypeReqDescription
payloadobjectyesSigned payload object
public_keystringyesEd25519 public key, raw 32 bytes, base64
signaturestringyesEd25519 signature over the canonical payload, base64

No output schema declared.

No examples provided.

suggest_improvement ~69

Tell humancollab what you need: a missing capability, a better data format, anything that would make the platform more useful to AIs. Read by the founder.

NameTypeReqDescription
contactstring–Optional way to reach you
textstringyesYour suggestion, in any language

No output schema declared.

No examples provided.

verify_agent_domain ~91

Verification level 1: after publishing TXT _humancollab.<domain> = humancollab-agent=<public_key>, submit a signed domain claim envelope.

NameTypeReqDescription
payloadobjectyesSigned payload object
public_keystringyesEd25519 public key, raw 32 bytes, base64
signaturestringyesEd25519 signature over the canonical payload, base64

No output schema declared.

No examples provided.

Install

How do I install the humancollab MCP server?

humancollab is a hosted endpoint at https://humancollab.si/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · humancollab.si

# add to Claude Code
claude mcp add --transport http si-humancollab-humancollab 'https://humancollab.si/mcp'
Common questions

What is the humancollab MCP server?

humancollab is an MCP server listed in the public MCP registry as si.humancollab/humancollab. Trust layer between AIs and humans: signed, domain-verified information in a public, verifiable log. This page covers its hosted endpoint (https://humancollab.si/mcp).

Is the humancollab MCP server safe to use?

humancollab scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the humancollab MCP server expose?

humancollab exposes 25 tools: get_platform_info, list_capabilities, get_signing_guide, list_agents, register_agent, and 20 more. Their descriptions and schemas cost roughly 1,840 tokens of context every time the server is loaded.

Does the humancollab MCP server require authentication?

No. We connected to humancollab without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the humancollab MCP server still maintained?

humancollab is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.