vibehunt.tech

Publish a Capability

List your software.

The fastest path is to ask your AI agent — connect VibeHunt's MCP server and it can author the manifest, walk you through hosting it at .well-known/vibehunt/, and submit it to the registry. Prefer to do it yourself? The form does exactly the same thing.

Either way, hosting the JSON file at the canonical URL on your domain is the verification proof — no DNS records, no review queue. Verified manifests are indexed live.

Let your agent do it.

VibeHunt's MCP server gives your agent six tools — including vibehunt_draft_manifest to author the JSON-LD and vibehunt_submit_capability to verify + index. Connect once, then ask in plain English.

1

Connect your agent

One config edit. Snippets for every common client live on the MCP page.

endpoint · streamable http
https://vibehunt.tech/api/mcp

Quickest setup — Claude Code:

shell
claude mcp add --transport http vibehunt https://vibehunt.tech/api/mcp

See setup for Claude Desktop, Cursor, Cline, Windsurf →

2

Ask your agent

Paste this (or anything like it) once the MCP server is connected. The agent will draft the manifest, show you the JSON, and tell you exactly where to host it.

prompt
I just built [name your software]. It does [one sentence]. The homepage is https://[your-domain].

Please:
1. Use vibehunt_list_categories and vibehunt_list_constraints to pick the right category and any constraint terms it satisfies.
2. Use vibehunt_draft_manifest to generate the JSON-LD manifest with did:web verification anchored to my domain.
3. Tell me exactly where to host the resulting file (the .well-known URL).
4. Once I confirm it's live, call vibehunt_submit_capability to verify and index it.

The agent runs vibehunt_draft_manifest and walks you through the next step.

3

Host the manifest at .well-known

Your agent gives you the exact URL after drafting. The path is always /.well-known/vibehunt/[slug].json on your domain. Once it's live, the agent calls vibehunt_submit_capability and the entry is searchable on /browse immediately.

For Next.js / Vercel, drop the file in public/.well-known/vibehunt/[slug].json and deploy. For Netlify, GitHub Pages, or a static site — same idea, whatever path resolves to that URL on your domain.

The URL is the proof of domain control. There's nothing else to set up — no DNS records, no API key, no account.