Should my agent depend on the MCP server io.github.kapoost/humanmcp?

Verdict: allow — rich-shared — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

humanMCP — kapoost

io.github.kapoost/humanmcp

Personal MCP server for humans who create. Proof of authorship, license control.

— the operator's own registry description reported

Publisher io.github.kapoost · first seen 2026-08-12 · endpoint https://kapoost.humanmcp.net/mcp

allow

verdict

rich-shared

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-shared — safe to depend on

Cluster rich-shared · distinctiveness 0.373 (moderate). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency208 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools41

vs populationhigh

capabilities2

harnessB

Trust — can it rely on it?

identityshared

servers on its host1

servers on its domain2

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_d1fa1d1610da468e25ddf9de · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

about_humanmcp ask_human bootstrap_session delete_skill fetch_answer fetch_narada_result get_author_profile get_certificate get_persona get_persona_journal get_skill leave_comment leave_message list_blobs list_collection list_content list_personas list_provenance list_skill_groups list_skills load_skill_group mysloodsiewnia_get mysloodsiewnia_list mysloodsiewnia_search mysloodsiewnia_status mysloodsiewnia_write read_blob read_collection_item read_content read_provenance recall record_persona_reflection remember request_access request_license run_narada submit_answer suggest_skills synthesise_persona_patterns upsert_skill verify_content

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band B — usable, with rough edges.

legibility check	tools passing	ok
name is clear & specific	41/41	✓
has a description	41/41	✓
description is substantive	41/41	✓
parameters are typed	41/41	✓
parameters are described	6/41	6/41

41 of 41 tools graded · 41 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

0.2.0-dev

server version humanMCP — kapoost

Capabilities: logging tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (2 events)

date	type	what changed
2026-08-14	inventory	tools 40 → 41
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:59:41Z	ok_tools	200	208	2025-06-18
2026-08-12T05:34:53Z	ok_tools	200	278	2024-11-05

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.kapoost/humanmcp.svg)](https://robinsaige.com/s/io.github.kapoost/humanmcp)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview