Reviews
No review yet. Used VibeCodePicks? Be the first to help others choose.What it does
VibeCodePicks is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2d ago (live check)Hosted endpoint
https://vibecodepicks.com/api/mcp/streamable-http
In Claude Code: claude mcp add --transport http vibecodepicks-1 https://vibecodepicks.com/api/mcp/
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"vibecodepicks-1": {
"url": "https://vibecodepicks.com/api/mcp/"
}
}
}Live check
Electra Index connected to the hosted endpoint 2d agoONLINE VibeCodePicks answered an MCP connection on 14 Nov 2026 and introduced itself as vibecodepicks 3.0.0 (MCP protocol 2025-06-18).
30 tools offered to AI assistants
search· Find vibe coding / AI tools. Rows: id|name|category|$from/mo|free(1/0). Use fetch(id) for details.fetch· Tool profile by id. Default: summary, best_for, price, free, 2 strengths, 2 weaknesses, url. fields: summary description best_for not_for skill coding pricing platforms strengths weaknesses alternatives video compare official all.recommend_tools· Ranked best-fit tools for a goal, matched on verified capabilities (not categories), with why + caveat. Saved tags can reorder equally-matched tools by up to 2 points when the new matcher is on (platforms/preferences tags only); they nevercompare_tools· Side-by-side of two tools + comparison page url.list_alternatives· Alternatives to a tool. Rows: id|name|$from/mo|free.list_scenarios· Use-case scenarios (e.g. ai-game-development, code-review) with top tools by community sentiment.scenario· Tools competing in one scenario, ranked by community sentiment, with compact strengths/weak spots here.list_categories· Category and use-case keys with tool ids.whats_new· Daily feed. With key: honors the saved feed mode — by_interests: new items relevant to ANY saved project; all_new: every new item (tagged with a project when one matches). Max 3/day, one line each, never repeats. {new:0} = nothing. Call atsubscribe· Create a pseudonymous feed key (no email/account — the key identifies your feed, not your name). One key = one project: it is also that project's canary identity, so use a separate key per project. Save it in long-term memory / project instsave_preferences· Replace the keyed-feed interest tags. Send allowed tags only (project types, platforms, budget, preferences) — do not send project names or other free text (they are dropped and never stored). Plus the feed mode ('by_interests' = only matchlog_choice· Record a tool the user explicitly picked/rejected/tried/starred, or PURCHASED. Call it with action 'purchased' right after the user tells you they bought a paid plan of a listed tool (ask first; never log silently), and again later with act
Show 18 more
set_preferences· Store the user's onboarding answers as non-sensitive tags only: project_types, platforms, budget (free|under_20|any), preferences (nocode|code|open-source|free-tier), and tools_in_use (catalog ids). Unknown values are dropped — never send ncheck_updates· Tools added or updated since this user's last check that match their saved tags. Optional since (YYYY-MM-DD or catalog v). When nothing matches, returns {new:0} — a minimal response when nothing new matches. Tracks last_checked. Max 3 itemsfeedback· Adjust this user's check_updates ranking for a listed tool. action is one of used, not_useful, not_relevant. Stores only the tool id and that enum. Does not change recommend_tools. Optional key: same feed key passed to set_preferences, to arecommend_for_task· Recommend tools for a task in the context of one saved project, so the user does not repeat the project background every turn. Reads the project's accepted/rejected tool lists, stage and known context; a tool this project rejected is nevercheck_project_changes· Check whether this project or the catalog changed since the last check in a way worth interrupting for. Returns silent unless there is a real signal (project stage change, or a catalog change that verifies an open need) AND a reliably relevforget_me· Delete this client's anonymous id, tag profile and last_checked. Feedback is first folded into anonymous aggregate counters (tool_id × used/not_useful/not_relevant, no uid). Those aggregate counts are kept. If you pass a feed key, that keyeproject_upsert· Create a project, or update one you own. One owner may own many isolated projects; a project archive holds desensitised fields only (type, stage, capability ids, tag preferences, confirmed used-tool ids, explicitly rejected tool ids) — neveproject_get· Read one project archive you own (owner credential, or that project's own pt_ token). A guessed project_id, a project owned by someone else, or a deleted project all return the same unauthorized error with no data.project_list· List your projects as full v2 archives (schema_version: 2 — lifecycle_stage, workflow_stage, capabilities, task_capabilities, known_context, used/rejected tools, version, updated_at). Owner credential only; a project token cannot list.project_export· Export one project you own: the archive, your consent record, and the last 50 recorded usage events. Owner credential, or that project's own pt_ token.delete_project· Delete one project you own (project_id), or ALL your projects (all:true, which also deletes your consent record). Deletion is permanent: the archive, its tokens, its events, its event dedup/meta/reversal keys and its check state are gone. Kconsent_get· Read your consent record: per-scope granted/revoked state, policy version, timestamps. Default is all scopes OFF.consent_update· Grant or withdraw ONE consent scope: followup (project long-term follow-up — the project profile is stored on VCP servers), usage_collection (usage-experience collection), alliance (alliance membership — needs usage_collection first), publiconsent_request_receipt· Request a server-issued one-time consent receipt for a scope (followup / usage_collection / alliance / publish_reviews). Returns a receipt id and a confirm_url (absolute, environment-correct; the receipt id travels as a URL fragment, nevernotification_ack· Report that a notification candidate from check_project_changes was delivered to the user, as reported by the host (host-reported acknowledgement — the receipt is a host-supplied string, e.g. the scheduled-task run id; the server records itrecord_decision· Record one usage event for a project you own (owner credential, or that project's pt_ token). Every event needs a source-stable event_id, project_id, catalog tool_id, event_type (picked|rejected|tried|starred|purchased|feedback|used|not_useproject_bind_code· Issue a one-time binding code (15 minutes, void after one use) so the same project can be bound in another AI client. Owner credential only; redeem it there with project_bind.project_bind· Redeem a one-time binding code from project_bind_code in this client. Returns the project_id and a project_token (shown once) for that project. A used, expired or unknown code returns unauthorized.
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://vibecodepicks.com/api/mcp/ | DECLARED | SRC-001 Official MCP Registry | 16h ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 16h ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 16h ago |
| Website | https://vibecodepicks.com/ | DECLARED | SRC-001 Official MCP Registry | 16h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 16h ago |
| Version | 2.6.1 | DECLARED | SRC-001 Official MCP Registry | 16h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 16h ago |
Change history
- NEW11 Nov 2026first seen in the index
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is VibeCodePicks still online?
Free alerts · no account▲ 0Do you run VibeCodePicks? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about VibeCodePicks
How do I connect VibeCodePicks?
Use the hosted endpoint https://vibecodepicks.com/api/mcp/ in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does VibeCodePicks offer?
When Electra Index connected on 14 Nov 2026, it listed 30 tools: search, fetch, recommend_tools, compare_tools, list_alternatives, list_scenarios, scenario, list_categories and more. The full list is in "Live check" above.
Is VibeCodePicks online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 2d ago.