Skip to content

VibeCodePicks MCP server

io.github.suanrongbaicai/vibecodepickssuanrongbaicaistreamable-httpv2.4.0Scanned

Pick AI coding tools by goal: community-sentiment rankings, pricing, free tiers, alternatives.

30 tools: 2 can delete or cancel things, 19 change things and 9 only read.

Tools: 2 delete, 0 irreversible, 19 write, 9 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 0
  • 13 findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the VibeCodePicks MCP server can do

The VibeCodePicks MCP server is published by the GitHub account suanrongbaicai. It has 30 tools. It can delete or cancel things (2 tools: forget_me and delete_project) and create or change data (19 tools: recommend_tools, scenario, whats_new, subscribe and 15 more). 9 tools only read.

1 tool reads private data (project_get); 1 tool brings in text other people can write (compare_tools).

The fixed checks matched 13 findings (annotation-conflict and credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 2.4.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

30 tools

Deletes or cancels 2Claude Code: deny
  • delete_projectDelete one project you own (project_id), or ALL your projects (all:true, which also deletes your consent record).1 finding

    Why it is in this group

    • The name "delete_project" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...s only (no owner or project ids). Owner credential only."

      What this check looks for
    Description, as the server wrote it
    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 owner or project ids). Owner credential only.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • forget_meDelete this client's anonymous id, tag profile and last_checked.No findings

    Why it is in this group

    • The description's first verb is "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Changes things 19Claude Code: ask
  • check_project_changesCheck whether this project or the catalog changed since the last check in a way worth interrupting for.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...project_id and an Authorization: Bearer credential (owner key or project token); a key pas..."

      What this check looks for
    Description, as the server wrote it
    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 the server-side catalog diff ledger (no ledger entry exists yet, so currently only project stage changes trigger); a client claim that the catalog changed is never accepted. The server has no scheduler and cannot push: this only answers when the host calls it. Whether the host can schedule is a server-side hint from the declared clientInfo.name (ChatGPT scheduled tasks and Cursor Automations count; other hosts do not) — a capability hint, not a verified host identity — never from a client claim; otherwise the answer is silent with reason host_no_scheduler and the host should check manually. The most this returns is a notification candidate (with a notif_id to acknowledge via notification_ack), never a confirmed delivery. Requires project_id and an Authorization: Bearer credential (owner key or project token); a key passed as a tool argument is never accepted.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • check_updatesTools added or updated since this user's last check that match their saved tags.No findings

    Why it is in this group

    • The name "check_updates" says "update": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • feedbackAdjust this user's check_updates ranking for a listed tool.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • log_choiceRecord a tool the user explicitly picked/rejected/tried/starred, or PURCHASED.1 finding

    Why it is in this group

    • The name "log_choice" says "log": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    Findings

    • Warn

      The server marks "log_choice" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "log_choice" says "log": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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 (key-associated / pseudonymous — the key identifies your feed, not your name); forget_me deletes it. picked/rejected also shape whats_new. purchased/feedback are the durable usage-experience record: they are written ONLY when the key owner has the usage_collection consent scope active (consent_request_receipt -> confirm on the VCP page -> consent_update); without it the call is refused. picked/rejected/tried/starred are feed-shaping signals covered by the explicit feed opt-in (subscribe) and work without usage_collection. Pass a stable event_id (or idempotency_key) to make the call deduped: a replay with the same key returns duplicate:1 and writes nothing. A call with no key is legacy: it always appends, and the response marks it legacy:1/unverified:1. A purchase logged here is self-reported, never a verified order. Prefer record_decision for project-bound usage events.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • notification_ackReport 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 s…1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...he check response, and a receipt. Owner credential, or that project's own pt_ token."

      What this check looks for
    Description, as the server wrote it
    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 'delivered': the server never claims delivery on its own, and notified_at / notified_fingerprint in the check state are set only here. A candidate that is never acked is never counted as delivered, and the same change may be notified again. Requires project_id, the notif_id from the check response, and a receipt. Owner credential, or that project's own pt_ token.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • project_bindRedeem a one-time binding code from project_bind_code in this client.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • project_bind_codeIssue a one-time binding code (15 minutes, void after one use) so the same project can be bound in another AI client.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...an be bound in another AI client. Owner credential only; redeem it there with project_bind..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • project_exportExport one project you own: the archive, your consent record, and the last 50 recorded usage events.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...he last 50 recorded usage events. Owner credential, or that project's own pt_ token."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • project_upsertCreate a project, or update one you own.1 finding

    Why it is in this group

    • The name "project_upsert" says "upsert": a word for a change.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...on mismatch); rotate_token:true (owner credential only) invalidates all old project token..."

      What this check looks for
    Description, as the server wrote it
    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 project_id to create (returns project_id + a project_token shown once); pass expected_version to guard concurrent updates (version_conflict on mismatch); rotate_token:true (owner credential only) invalidates all old project tokens and returns a new one.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • recommend_for_taskRecommend tools for a task in the context of one saved project, so the user does not repeat the project background every turn.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...project_id and an Authorization: Bearer credential (owner key or project token); a key pas..."

      What this check looks for
    Description, as the server wrote it
    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 answer need_clarification with exactly one question, or no_match when no catalog tool verifies the task — never pads with unverified candidates. Requires project_id and an Authorization: Bearer credential (owner key or project token); a key passed as a tool argument is never accepted.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • recommend_toolsRanked best-fit tools for a goal, matched on recorded capability information (not categories), with why + caveat.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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 'claimed' (vendor-stated, not independently confirmed; never presented as verified). An independent review step then ranks the candidates and gives reasons, or honestly abstains. Possible decisions: recommend; need_clarification (exactly one question, when a key fact is missing); no_match (no tool's recorded information covers the goal — closest partial matches are named); no_recommendation (candidates exist but none is a defensible fit); review_unavailable (the review step could not run — stated plainly, never replaced by a weaker ranking). Every answer carries narrow_by hints: pass budget ('free' or a monthly USD cap), platform, required_capabilities or hard_constraints back to shrink the field on the next round. Pass the goal in plain words, or the already-extracted structured task object (task: action, input_type, output_type, required_capabilities / forbidden_capabilities capability ids, hard_constraints tokens, confidence, known_context) — the server validates the task object and rejects invalid tasks with an error; in the top-level required_capabilities / forbidden_capabilities / hard_constraints arrays, unknown ids/tokens are dropped or ignored instead. On a new user's first call, also returns short onboarding questions (project types, platforms, budget, preferences, tools in use) for you to ask, then call set_preferences with tags only.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • record_decisionRecord one usage event for a project you own (owner credential, or that project's pt_ token).1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...sage event for a project you own (owner credential, or that project's pt_ token). Every ev..."

      What this check looks for
    Description, as the server wrote it
    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-assertable), and consent_version 2026-11-11-v1. Needs the usage_collection consent scope. A retry with the same event_id returns duplicate:1 and writes nothing twice. refunded/cancelled must name the earlier event in reverses_event_id and never edit history. Purchases recorded here are self-reported and never enter any verified-payment ledger.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • save_preferencesReplace the keyed-feed interest tags.No findings

    Why it is in this group

    • The name "save_preferences" says "save": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • scenarioTools competing in one scenario, ranked by community sentiment, with compact strengths/weak spots here.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Tools competing in one scenario, ranked by community sentiment, with compact strengths/weak spots here.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • set_preferencesStore 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_…No findings

    Why it is in this group

    • The name "set_preferences" says "set": a word for a change.
    Description, as the server wrote it
    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 results by up to 2 points (tie-break only, never overriding a capability filter). project_types, budget and tools_in_use never affect recommend_tools. Optional key: pass a feed key (from subscribe; send it in the Authorization: Bearer <key> header — the /api/mcp?k=KEY URL form is deprecated but still works during the transition) to keep this profile separate per project; without it, the anonymous client identity is used.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • subscribeCreate a pseudonymous feed key (no email/account — the key identifies your feed, not your name).No findings

    Why it is in this group

    • The name "subscribe" says "subscribe": a word for a change.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • whats_newDaily feed.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 9Show 9 read-only tools
  • compare_toolsSide-by-side of two tools + comparison page url.Reads text others writeNo findings

    Why it is in this group

    • The name "compare_tools" says "compare": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Side-by-side of two tools + comparison page url.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • fetchTool profile by id.No findings

    Why it is in this group

    • The name "fetch" says "fetch": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • list_alternativesAlternatives to a tool.No findings

    Why it is in this group

    • The name "list_alternatives" says "list": a word for reading.
    Description, as the server wrote it
    Alternatives to a tool. Rows: id|name|$from/mo|free.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • list_categoriesCategory and use-case keys with tool ids.No findings

    Why it is in this group

    • The name "list_categories" says "list": a word for reading.
    Description, as the server wrote it
    Category and use-case keys with tool ids.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • list_scenariosUse-case scenarios (e.g.No findings

    Why it is in this group

    • The name "list_scenarios" says "list": a word for reading.
    Description, as the server wrote it
    Use-case scenarios (e.g. ai-game-development, code-review) with top tools by community sentiment.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • project_getRead one project archive you own (owner credential, or that project's own pt_ token).Reads private data1 finding

    Why it is in this group

    • The name "project_get" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "credential": it reads secrets.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "Read one project archive you own (owner credential, or that project's own pt_ token). A gu..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • project_listList your projects as full v2 archives (schema_version: 2 — lifecycle_stage, workflow_stage, capabilities, task_capabilities, known_context, used/rejected tools, version, updated_a…1 finding

    Why it is in this group

    • The name "project_list" says "list": a word for reading.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...cted tools, version, updated_at). Owner credential only; a project token cannot list."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:11 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
21
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 21 tools that change things (2 destructive, 19 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://vibecodepicks.com/api/mcp: tools/list returned 30 tools to an anonymous client, including forget_me (destructive), delete_project (destructive), recommend_tools (write), scenario (write), whats_new (write) and 16 more

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 7 to 21
  2. Oct 29, 2026
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 7
    • Protocol version: none to 2025-06-18

Findings

Matches of fixed checks, with the text they matched.

1 warn12 info
  • The server marks "log_choice" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "log_choice" says "log": a word for reading.

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "...project_id and an Authorization: Bearer credential (owner key or project token); a key pas..."

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "...project_id and an Authorization: Bearer credential (owner key or project token); a key pas..."

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "...on mismatch); rotate_token:true (owner credential only) invalidates all old project token..."

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "Read one project archive you own (owner credential, or that project's own pt_ token). A gu..."

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "...cted tools, version, updated_at). Owner credential only; a project token cannot list."

    What this check looks for
Show 7 more findings

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools14 added, 6 changed.+14 added~6 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 7 -> 21.View diff
    • Tools that change things, listed without credentials: 7 to 21
  3. Tools3 added, 4 changed.+3 added~4 changedView diff
  4. PostureRemote posture changed. Reachable: no -> yes; HTTP status of an anonymous initialize: none -> 200; tools/list served without credentials: no -> yes (and 2 more).View diff
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 7
    • Protocol version: none to 2025-06-18

Install

Pinned to version 2.4.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http vibecodepicks https://vibecodepicks.com/api/mcp
claude mcp add --transport http vibecodepicks https://vibecodepicks.com/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__vibecodepicks__search",
      "mcp__vibecodepicks__fetch",
      "mcp__vibecodepicks__compare_tools",
      "mcp__vibecodepicks__list_alternatives",
      "mcp__vibecodepicks__list_scenarios",
      "mcp__vibecodepicks__list_categories",
      "mcp__vibecodepicks__project_get",
      "mcp__vibecodepicks__project_list",
      "mcp__vibecodepicks__consent_get"
    ],
    "ask": [
      "mcp__vibecodepicks__recommend_tools",
      "mcp__vibecodepicks__scenario",
      "mcp__vibecodepicks__whats_new",
      "mcp__vibecodepicks__subscribe",
      "mcp__vibecodepicks__save_preferences",
      "mcp__vibecodepicks__log_choice",
      "mcp__vibecodepicks__set_preferences",
      "mcp__vibecodepicks__check_updates",
      "mcp__vibecodepicks__feedback",
      "mcp__vibecodepicks__recommend_for_task",
      "mcp__vibecodepicks__check_project_changes",
      "mcp__vibecodepicks__project_upsert",
      "mcp__vibecodepicks__project_export",
      "mcp__vibecodepicks__consent_update",
      "mcp__vibecodepicks__consent_request_receipt",
      "mcp__vibecodepicks__notification_ack",
      "mcp__vibecodepicks__record_decision",
      "mcp__vibecodepicks__project_bind_code",
      "mcp__vibecodepicks__project_bind"
    ],
    "deny": [
      "mcp__vibecodepicks__forget_me",
      "mcp__vibecodepicks__delete_project"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as vibecodepicks. Review it before you use it.

Capability tags behind 2 rules
  • mcp__vibecodepicks__compare_tools untrusted-input
  • mcp__vibecodepicks__project_get private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.suanrongbaicai/vibecodepicks/verify?hash=bce0d192e63cb88e0d5d0375afe8012535f0de1a4e3a2c50509bb9cdca5aa2a1" | jq -e '.changed == false'

Pinned hash bce0d192e63c, from Nov 20, 2026, 14:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.suanrongbaicai/vibecodepicks/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.suanrongbaicai/vibecodepicks
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.suanrongbaicai/vibecodepicks.svg)](https://radar.anlyon.com/servers/io.github.suanrongbaicai/vibecodepicks)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:49 UTC.

VibeCodePicks MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the VibeCodePicks MCP server safe?

No scan can promise that. What its definitions show: 30 tools, 21 of which can change, send or delete something, and 13 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the VibeCodePicks MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: forget_me and delete_project.

Can the VibeCodePicks MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the VibeCodePicks MCP server have?

30 tools: 2 destructive, 19 write, 9 read. forget_me, delete_project, recommend_tools, scenario, whats_new, subscribe, save_preferences, log_choice and 22 more.

Does the VibeCodePicks MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the VibeCodePicks MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the VibeCodePicks MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.