{"id":"com.vibecodepicks/vibecodepicks","slug":"com-vibecodepicks-vibecodepicks","title":"VibeCodePicks","description":"Capability-matched AI coding tool recommendations from a hand-checked catalog of 470 tools","version":"3.0.0","publisher":{"kind":"domain","id":"vibecodepicks.com","label":"vibecodepicks.com","url":"https://vibecodepicks.com"},"website":"https://vibecodepicks.com/","repository":"","remotes":[{"type":"streamable-http","url":"https://vibecodepicks.com/api/mcp/"}],"packages":[],"published":"2026-11-17","updated":"2026-11-17","status":"online","auth":"","latency_ms":956,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"search","title":"Search tools","description":"Find vibe coding / AI tools. Rows: id|name|category|$from/mo|free(1/0). Use fetch(id) for details.","read_only":true},{"name":"fetch","title":"Get tool details","description":"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.","read_only":true},{"name":"recommend_tools","title":"Recommend tools","description":"Ranked best-fit tools for a goal, matched on recorded capability information (not categories), with why + caveat. How it works: the goal is decomposed into required capabilities; only tools whose recorded information covers every required capability become candidates — each capability is labeled 'verified' (demonstration, independent confirmation, known pricing, checked within 180 days) or 'claime","read_only":true},{"name":"compare_tools","title":"Compare two tools","description":"Side-by-side of two tools + comparison page url.","read_only":true},{"name":"list_alternatives","title":"Find alternatives","description":"Alternatives to a tool. Rows: id|name|$from/mo|free.","read_only":true},{"name":"list_scenarios","title":"List scenarios","description":"Use-case scenarios (e.g. ai-game-development, code-review) with top tools by community sentiment.","read_only":true},{"name":"scenario","title":"Scenario ranking","description":"Tools competing in one scenario, ranked by community sentiment, with compact strengths/weak spots here.","read_only":true},{"name":"list_categories","title":"List categories","description":"Category and use-case keys with tool ids.","read_only":true},{"name":"whats_new","title":"What's new for you","description":"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 at most daily. Without key: stateless by since/interests. Never affects other tools.","read_only":false},{"name":"subscribe","title":"Subscribe to the feed","description":"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 instructions / rules, and send it in the Authorization: Bearer <key> header on later calls (connecting via /api/mcp?k=KEY still works for now but is deprecated).","read_only":false},{"name":"save_preferences","title":"Save your preferences","description":"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 matching tools; 'all_new' = every new tool). Only used by whats_new.","read_only":false},{"name":"log_choice","title":"Log a choice or purchase","description":"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 action 'feedback' once they have used it for a while (e.g. weekly), passing rating only. Optional fields apply to purchased/feedback only. Stored under your key (k","read_only":false},{"name":"set_preferences","title":"Save preference tags","description":"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 names, emails, code, project names or free text. Used by check_updates; the platforms and preferences tags can also reorder equally-matched recommend_tools resul","read_only":false},{"name":"check_updates","title":"Check matching updates","description":"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 items. Does not change recommend_tools. Optional key: same feed key passed to set_preferences, to read that project's profile.","read_only":false},{"name":"feedback","title":"Record feedback","description":"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 adjust that project's ranking.","read_only":false},{"name":"recommend_for_task","title":"Recommend for this project","description":"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 never re-pushed; a tool already in use is judged keep / supplement / replace, each with an evidence_level (user_stated / client_observed / assistant_inferred). May an","read_only":true},{"name":"check_project_changes","title":"Check project changes","description":"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 relevant tool. Deduped (same change is never notified twice) and rate-limited (at most one notification per project per 24h). Catalog changes are detected ONLY from ","read_only":true},{"name":"forget_me","title":"Forget me","description":"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 keyed feed record is deleted too.","read_only":false},{"name":"project_upsert","title":"Create or update a project","description":"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) — never send a project name, code, raw chat, path or free text (dropped and reported as dropped_fields). Needs the followup consent scope (consent_update first). Omit","read_only":false},{"name":"project_get","title":"Get a project","description":"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.","read_only":true},{"name":"project_list","title":"List projects","description":"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.","read_only":true},{"name":"project_export","title":"Export a project","description":"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.","read_only":true},{"name":"delete_project","title":"Delete a project","description":"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. Kept: one tombstone per deleted project ({owner, deleted_at}) for 400 days so old tokens can never resurrect it, plus anonymous per-tool aggregates only (no owne","read_only":false},{"name":"consent_get","title":"Get consent","description":"Read your consent record: per-scope granted/revoked state, policy version, timestamps. Default is all scopes OFF.","read_only":true},{"name":"consent_update","title":"Update consent","description":"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), publish_reviews (publishing identifiable reviews). Granting ANY scope needs a server-issued one-time receipt: request one with consent_request_receipt, confirm it on","read_only":false},{"name":"consent_request_receipt","title":"Request a consent receipt","description":"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, never a query parameter): show the confirm_url to the user — they must confirm the scope on VCP's own confirmation page, in their own signed-in VibeCodePicks browser ","read_only":false},{"name":"notification_ack","title":"Acknowledge a notification delivery","description":"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 it but does NOT verify it, so this is not proof a human saw the notification and never purchase or reward evidence). This is the ONLY way a notification becomes '","read_only":false},{"name":"record_decision","title":"Record a usage event","description":"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_useful|not_relevant|refunded|cancelled), observed_at (ISO date), evidence_level (user_reported|observed|assistant_inferred — vendor_verified is not client-assertab","read_only":false},{"name":"project_bind_code","title":"Issue a binding code","description":"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.","read_only":false},{"name":"project_bind","title":"Redeem a binding code","description":"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.","read_only":false}],"server_info":{"name":"vibecodepicks","title":"VibeCodePicks","version":"3.0.0","websiteUrl":"https://vibecodepicks.com"},"category":"project","tags":["cloud","developer","productivity"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-11-11","stars":0,"badges":["new"],"sponsor":null,"page":"https://agentsindex.org/agents/com-vibecodepicks-vibecodepicks/"}