MCP
MCP servers and auth-bearing tool bridges.
No obvious metadata gaps in this area.
HeyClaude does not publish a named validator roster yet. This page exposes the real registry coverage we can stand behind today: source status, maintainer review flags, and safety/privacy metadata completeness.
MCP servers and auth-bearing tool bridges.
No obvious metadata gaps in this area.
Lifecycle hooks that can run local commands.
No obvious metadata gaps in this area.
Claude Skills and capability packs.
No obvious metadata gaps in this area.
Slash commands and command packs.
No obvious metadata gaps in this area.
Shell/UI statusline integrations.
No obvious metadata gaps in this area.
CLAUDE.md, AGENTS.md, editor rules, and configs.
No obvious metadata gaps in this area.
Entries needing runtime, install, file, or credential scrutiny.
No obvious metadata gaps in this area.
Entries that should disclose data flow, credentials, logs, or third-party requests.
No obvious metadata gaps in this area.
These tools inspect submitted metadata locally. They are review aids, not malware scanning or install approval.
Frontmatter, package references, checksum facts, submission metadata.
Server shape, package targets, placeholders, risky shell syntax, secret-like values.
Want to improve coverage? Open a focused PR that adds source-backed safety, privacy, or provenance metadata for specific entries.