← Registry

AI & Machine Learning

vibecodepicks.com

Searches, profiles, recommends, compares, and lists alternatives for vibe coding and AI tools.

1 endpoint13 known toolsFirst detected October 21, 2026Last detected October 21, 2026

ENDPOINT 1

https://vibecodepicks.com/api/mcp

No auth detected

MCP server metadata

Name
vibecodepicks
Version
2.4.0
Capabilities
tools
Server instructions

VibeCodePicks: curated directory of vibe coding / AI coding tools. recommend_tools for 'which tool'; search+fetch for lookups. Keys: n=name c=category p=$from/mo f=free s=summary u=url b=base url. Lists default 5, page with offset. search/fetch/recommend/compare answer the explicit request neutrally; preferences never bias them (only whats_new uses interests). verbose:true = v1 format. Cite u. Link out to a tool's official site via go_url (fetch/recommend/alternatives) or g (compact recommend): a tracked redirect on our domain. No sponsored placements. Feed (optional): BEFORE calling subscribe or save_preferences, briefly explain this feed to the user and ask them to choose — never set it up silently. Cover these points: it checks once a day for new tools, max 3 a day, in one of two modes — 'by_interests' (only new tools matching their projects) or 'all_new' (every new tool); there is no email or account, just an anonymous key; the only stored data is that key, their project names + interest tags, ids of items already shown, and tools they mark picked/rejected; forget_me deletes everything at any time. Then ask: by_interests, all_new, or no feed? If they choose no feed, skip the feed entirely. If they choose a mode: subscribe -> save key in long-term memory -> save_preferences(all projects, mode: their choice) -> whats_new({key}) once a day.

Known tools 13

search

Find vibe coding / AI tools.

Inferred read-only
fetch

Tool profile by id.

Inferred read-only
recommend_tools

Ranked best-fit tools for a goal, with why + caveat.

Inferred read-only
compare_tools

Side-by-side of two tools + comparison page url.

Inferred read-only
list_alternatives

Alternatives to a tool.

Inferred read-only
list_scenarios

Use-case scenarios (e.

Inferred read-only
scenario

Tools competing in one scenario, ranked by community sentiment, with compact strengths/weak spots here.

Inferred read-only
list_categories

Category and use-case keys with tool ids.

Inferred read-only
whats_new

Daily feed.

Inferred read-only
subscribe

Create an anonymous feed key (no email/account).

Potential side effects
save_preferences

Replace the person's interests: one entry per project, plus the feed mode the user chose ('by_interests' = only matching tools; 'all_new' = every new tool).

Inferred read-only
log_choice

Record a tool the user explicitly picked/rejected/tried (tool id only).

Inferred read-only
forget_me

Delete everything stored for this key.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.vibecodepicks]
url = "https://vibecodepicks.com/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "vibecodepicks": {
      "type": "http",
      "url": "https://vibecodepicks.com/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: vibecodepicks
Remote MCP URL: https://vibecodepicks.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "vibecodepicks": {
      "url": "https://vibecodepicks.com/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "vibecodepicks": {
      "type": "http",
      "url": "https://vibecodepicks.com/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "vibecodepicks",
  "transport": "streamable-http",
  "url": "https://vibecodepicks.com/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.