Should my agent depend on the MCP server io.github.JSONbored/heyclaude?

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

HeyClaude — Claude & AI workflow directory

io.github.JSONbored/heyclaude

Search the HeyClaude directory of Claude Code agents, MCP servers, skills, and tools.

— the operator's own registry description reported

Publisher io.github.JSONbored · first seen 2026-08-12 · endpoint https://heyclau.de/api/mcp

allow

verdict

mid-slow-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — mid-slow-solo — safe to depend on

Cluster mid-slow-solo · distinctiveness 0.709 (unusual). 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

latency6244 ms

vs populationslow

protocolcurrent

authopen

Use — can it use it?

tools28

vs populationmid

capabilities3

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_0cfdbdda5720b1ea5322778c · 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

entry.asset entry.compare entry.coverage entry.detail entry.related entry.safety entry.trust install.adapter install.compatibility install.guidance install.setup registry.feeds registry.info registry.list registry.plan registry.recommend registry.search registry.stats registry.updates submission.duplicates submission.examples submission.guidance submission.policy submission.prepare submission.review submission.schema submission.urls submission.validate

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 A — an agent can pick and call these reliably.

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

28 of 28 tools graded · 28 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.14.9

server version heyclaude-registry

Capabilities: prompts resources 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 (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:59:04Z	ok_tools	200	6244	2025-06-18
2026-08-12T05:34:18Z	ok_tools	200	126	2025-06-18

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.JSONbored/heyclaude.svg)](https://robinsaige.com/s/io.github.JSONbored/heyclaude)

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