Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

VibeCodePicks

REMOTE · VIBECODEPICKS.COM

Capability-matched AI coding tool recommendations from a hand-checked catalog of 470 tools

+3 this week 65 Trust /100

Last scanned (19 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability55
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 5288 tokens (~176/item across 30 items; 30 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage70
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 11% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 31 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “recommend_tools” rewrote its description, which is the text the model reads security
    • Tool “set_preferences” rewrote its description, which is the text the model reads security
    • “recommend_tools” reworded the description of “forbidden_capabilities” cosmetic
    • “recommend_tools” reworded the description of “hard_constraints” cosmetic
    • “recommend_tools” reworded the description of “required_capabilities” cosmetic
    • “recommend_tools” reworded the description of “task” cosmetic
  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “delete_project”, which the server declares destructive security
    • Tool “log_choice” rewrote its description, which is the text the model reads security
    • Tool “recommend_tools” rewrote its description, which is the text the model reads security
    • Tool “set_preferences” rewrote its description, which is the text the model reads security
    • Tool “subscribe” rewrote its description, which is the text the model reads security
    • Tool coverage: 19% → 11% ▼ functional
    • Schema quality: 120 → 165 ▼ functional
    • Schema quality: fair → good functional
    • Server version: 2.6.1 → 3.0.0 functional
    • New tool “check_project_changes” functional
    • New tool “consent_get” functional
    • New tool “consent_request_receipt” functional
    • New tool “consent_update” functional
    • New tool “notification_ack” functional
    • New tool “project_bind” functional
    • New tool “project_bind_code” functional
    • New tool “project_export” functional
    • New tool “project_get” functional
    • New tool “project_list” functional
    • New tool “project_upsert” functional
    • New tool “recommend_for_task” functional
    • New tool “record_decision” functional
    • “log_choice” added an optional parameter “event_id” cosmetic
    • “log_choice” added an optional parameter “idempotency_key” cosmetic
    • “recommend_tools” added an optional parameter “forbidden_capabilities” cosmetic
    • “recommend_tools” added an optional parameter “hard_constraints” cosmetic
    • “recommend_tools” added an optional parameter “required_capabilities” cosmetic
    • “recommend_tools” added an optional parameter “task” cosmetic
    • “log_choice” dropped the optional parameter “fell_short” cosmetic
    • “log_choice” dropped the optional parameter “plan” cosmetic
    • “log_choice” dropped the optional parameter “price_usd” cosmetic
    • “log_choice” dropped the optional parameter “worked” cosmetic
  • 12 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 11 Nov 26 61

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://vibecodepicks.com/api/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.vibecodepicks.com CN=YR2,O=Let's Encrypt,C=US 18 Nov 2026 16 Feb 2027 RSA 2048 SHA256-RSA 5ef3ba7457175f73bfb334453ec77cbf41d
SANs: *.vibecodepicks.com, vibecodepicks.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of vibecodepicks.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
vibecodepicks.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://vibecodepicks.com/api/mcp/ Verified 200
http (plaintext) http://vibecodepicks.com/api/mcp/ HTTPS enforced 308 https://vibecodepicks.com/api/mcp/
MCP tools · 30 exposed · ~3,959 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_project_changes ~267

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.

NameTypeReqDescription
project_idstringyes–

No output schema declared.

No examples provided.

check_updates ~109

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.

NameTypeReqDescription
keystring––
sincestring–YYYY-MM-DD or catalog version; defaults to last_checked

No output schema declared.

No examples provided.

compare_tools ~40

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

NameTypeReqDescription
astringyes–
bstringyes–
verboseboolean––

No output schema declared.

No examples provided.

consent_get ~33

Read your consent record: per-scope granted/revoked state, policy version, timestamps. Default is all scopes OFF.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

consent_request_receipt ~147

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 session, before the receipt can be used. The MCP client cannot confirm on their behalf. The receipt is single-use and expires in 15 minutes. Pass the receipt id as `receipt` to consent_update. Owner credential only.

NameTypeReqDescription
scopestringyes–

No output schema declared.

No examples provided.

consent_update ~178

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 the VCP confirmation page in the user's own signed-in VibeCodePicks browser session, then pass its receipt id as `receipt`. A plain source string is never proof for any scope. Scopes are never bundled: granting one never grants another, and alliance never implies publish_reviews. Withdrawing a scope blocks new writes under it immediately. Owner credential only.

NameTypeReqDescription
grantedbooleanyes–
receiptstring––
scopestringyes–

No output schema declared.

No examples provided.

delete_project ~120

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.

NameTypeReqDescription
allboolean––
project_idstring––

No output schema declared.

No examples provided.

feedback ~86

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.

NameTypeReqDescription
actionstringyes–
keystring––
tool_idstringyes–

No output schema declared.

No examples provided.

fetch ~74

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.

NameTypeReqDescription
fieldsarray––
idstringyes–
verboseboolean––

No output schema declared.

No examples provided.

forget_me ~71

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.

NameTypeReqDescription
keystring––

No output schema declared.

No examples provided.

list_alternatives ~55

Alternatives to a tool. Rows: id|name|$from/mo|free.

NameTypeReqDescription
limitinteger––
offsetinteger––
toolstringyes–
verboseboolean––

No output schema declared.

No examples provided.

list_categories ~24

Category and use-case keys with tool ids.

NameTypeReqDescription
verboseboolean––

No output schema declared.

No examples provided.

list_scenarios ~31

Use-case scenarios (e.g. ai-game-development, code-review) with top tools by community sentiment.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

log_choice ~358

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.

NameTypeReqDescription
actionstringyes–
comboarray–Ids of other tools used together with this one
event_idstring––
idstringyes–
idempotency_keystring––
keystring––
periodstring––
ratinginteger––

No output schema declared.

No examples provided.

notification_ack ~189

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.

NameTypeReqDescription
notif_idstringyes–
project_idstringyes–
receiptstringyes–

No output schema declared.

No examples provided.

project_bind ~57

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.

NameTypeReqDescription
bind_codestringyes–

No output schema declared.

No examples provided.

project_bind_code ~55

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.

NameTypeReqDescription
project_idstringyes–

No output schema declared.

No examples provided.

project_export ~49

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.

NameTypeReqDescription
project_idstringyes–

No output schema declared.

No examples provided.

project_get ~60

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.

NameTypeReqDescription
project_idstringyes–

No output schema declared.

No examples provided.

project_list ~58

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

project_upsert ~215

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.

NameTypeReqDescription
capabilitiesarray––
expected_versioninteger––
preferencesobject––
project_idstring––
rejected_toolsarray––
rotate_tokenboolean––
stagestring––
tools_in_usearray––
typestring––

No output schema declared.

No examples provided.

recommend_for_task ~176

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.

NameTypeReqDescription
goalstring––
limitinteger––
project_idstringyes–
taskobject––

No output schema declared.

No examples provided.

recommend_tools ~565

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.

NameTypeReqDescription
budgetstring–'free' or max USD/mo
can_codeboolean––
forbidden_capabilitiesarray–Capability ids the task must not need, e.g. ['text-to-video']. Unknown ids are ignored (they match nothing). Honoured by the capability matcher.
goalstringyes–
hard_constraintsarray–Hard-constraint tokens, e.g. 'offline', 'windows-only', 'no-cloud-upload', 'budget-zero-no-card'. Unknown tokens are ignored. Honoured by the capability matcher.
limitinteger––
offsetinteger––
platformstring––
required_capabilitiesarray–Capability ids the task must have, e.g. ['video-editing','auto-captions']. Unknown ids are dropped. Honoured by the capability matcher.
taskobject–Structured task (optional). The server validates it and rejects invalid tasks with an error. Honoured by the capability matcher.
verboseboolean––

No output schema declared.

No examples provided.

record_decision ~254

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.

NameTypeReqDescription
consent_versionstringyes–
event_idstringyes–
event_typestringyes–
evidence_levelstringyes–
observed_atstringyes–
project_idstringyes–
ratinginteger––
reverses_event_idstring––
tool_idstringyes–

No output schema declared.

No examples provided.

save_preferences ~116

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.

NameTypeReqDescription
interestsarray–Allowed tags only (project types, platforms, budget, preferences). Do not send a project name.
keystring––
modestring––

No output schema declared.

No examples provided.

scenario ~47

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

NameTypeReqDescription
limitinteger––
slugstringyes–
verboseboolean––

No output schema declared.

No examples provided.

search ~76

Find vibe coding / AI tools. Rows: id|name|category|$from/mo|free(1/0). Use fetch(id) for details.

NameTypeReqDescription
limitinteger––
offsetinteger––
querystringyese.g. 'no-code SaaS builder'
verboseboolean––

No output schema declared.

No examples provided.

set_preferences ~236

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.

NameTypeReqDescription
budgetstring––
keystring––
platformsarray––
preferencesarray––
project_typesarray––
tools_in_usearray–Catalog ids of tools already in use

No output schema declared.

No examples provided.

subscribe ~97

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).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

whats_new ~116

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.

NameTypeReqDescription
interestsarray––
keystring––
limitinteger––
sincestring––

No output schema declared.

No examples provided.

Install

How do I install the VibeCodePicks MCP server?

VibeCodePicks is a hosted endpoint at https://vibecodepicks.com/api/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · vibecodepicks.com

# add to Claude Code
claude mcp add --transport http com-vibecodepicks-vibecodepicks 'https://vibecodepicks.com/api/mcp/'
Common questions

What is the VibeCodePicks MCP server?

VibeCodePicks is an MCP server listed in the public MCP registry as com.vibecodepicks/vibecodepicks. Capability-matched AI coding tool recommendations from a hand-checked catalog of 470 tools. This page covers its hosted endpoint (https://vibecodepicks.com/api/mcp/).

Is the VibeCodePicks MCP server safe to use?

VibeCodePicks scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the VibeCodePicks MCP server expose?

VibeCodePicks exposes 30 tools: search, fetch, recommend_tools, compare_tools, list_alternatives, and 25 more. Their descriptions and schemas cost roughly 3,959 tokens of context every time the server is loaded.

Does the VibeCodePicks MCP server require authentication?

No. We connected to VibeCodePicks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the VibeCodePicks MCP server still maintained?

VibeCodePicks is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the VibeCodePicks MCP server?

VerifyMCP ran 13 checks on VibeCodePicks, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.