Current pain
- MCP configs are scattered across tools and machines.
- Tokens end up in local files or chats.
- No one knows exactly which tools each server exposes.
Thanks — your request has been recorded.
Submission failed. Please review the form and try again.
Validation — private MCP registryShare your MCP servers without sharing your secrets.
A private registry to centralize MCP configs, tokens, permissions, health checks, and audits — compatible with Claude Code, Cursor, OpenCode, and CI.
Open-source-firstBeta design partnersDemand validation before build
1 configgenerated per tool and environment
0 secretcopied into local developer files
Signal
Early access
Form wired to a free local collector: SQLite storage + JSONL audit log under /var/lib/unicornhunters/landing-leads/.
The pain is already visible.
Developer teams using multiple MCP servers across Claude Code, Cursor, OpenCode, IDEs, and CI pipelines.
A simple MVP you can sell and test.
Beta design partners first. Team cloud pricing expected at €49–199/month depending on server count and audit logs.
Private registry
Internal catalog of MCP servers with owners, versions, and status.
Secrets & policies
Secret injection, allow/deny rules, and per-tool or per-environment profiles.
Continuous audit
Health checks, exposed-tool diffs, and a change log for config updates.
Hypothesis to validate
“If the pain is real, prospects will leave their email, describe the use case, and indicate budget before the product exists.”
Decision metrics
- 20+ qualified emails in 7 days
- 5+ accepted discovery calls
- 3+ prospects with explicit budget
- At least 1 priority-access request
Join the beta
Form wired to a free local collector: SQLite storage + JSONL audit log under /var/lib/unicornhunters/landing-leads/.