VibeCodePicks
REMOTE · VIBECODEPICKS.COM
Pick AI coding tools by goal: community-sentiment rankings, pricing, free tiers, alternatives.
Available components
Last scanned (49 minutes ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category AI and Machine Learning
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (forget_me). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2772 tokens (~213/item across 13 items; 13 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 Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +4
- The server rewrote its instructions, which are the text every model session reads security
- Tool “save_preferences” rewrote its description, which is the text the model reads security
- Tool “scenario” rewrote its description, which is the text the model reads security
- Tool “search” 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 “whats_new” rewrote its description, which is the text the model reads security
- Tool “compare_tools” rewrote its description, which is the text the model reads security
- Tool “fetch” rewrote its description, which is the text the model reads security
- Tool “forget_me” rewrote its description, which is the text the model reads security
- Tool “list_alternatives” rewrote its description, which is the text the model reads security
- Tool “list_categories” rewrote its description, which is the text the model reads security
- Tool “list_scenarios” rewrote its description, which is the text the model reads 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
- Schema quality: pass → fail ▼ functional
- Tool coverage: 16% → 100% ▲ functional
- Schema quality: fair → excellent functional
- Destructive annotations: 100 → pass functional
- “forget_me” reworded the description of “key” cosmetic
- “recommend_tools” reworded the description of “can_code” cosmetic
- “recommend_tools” reworded the description of “goal” cosmetic
- “recommend_tools” reworded the description of “limit” cosmetic
- “recommend_tools” reworded the description of “offset” cosmetic
- “recommend_tools” reworded the description of “platform” cosmetic
- “recommend_tools” reworded the description of “verbose” cosmetic
- “save_preferences” reworded the description of “key” cosmetic
- “save_preferences” reworded the description of “mode” cosmetic
- “save_preferences” reworded the description of “projects” cosmetic
- “scenario” reworded the description of “limit” cosmetic
- “scenario” reworded the description of “slug” cosmetic
- “scenario” reworded the description of “verbose” cosmetic
- “search” reworded the description of “limit” cosmetic
- “search” reworded the description of “offset” cosmetic
- “search” reworded the description of “query” cosmetic
- “search” reworded the description of “verbose” cosmetic
- “whats_new” reworded the description of “interests” cosmetic
- “whats_new” reworded the description of “key” cosmetic
- “whats_new” reworded the description of “limit” cosmetic
- “whats_new” reworded the description of “since” cosmetic
- “compare_tools” reworded the description of “a” cosmetic
- “compare_tools” reworded the description of “b” cosmetic
- “compare_tools” reworded the description of “verbose” cosmetic
- “fetch” reworded the description of “fields” cosmetic
- “fetch” reworded the description of “id” cosmetic
- “fetch” reworded the description of “verbose” cosmetic
- “list_alternatives” reworded the description of “limit” cosmetic
- “list_alternatives” reworded the description of “offset” cosmetic
- “list_alternatives” reworded the description of “tool” cosmetic
- “list_alternatives” reworded the description of “verbose” cosmetic
- “list_categories” reworded the description of “verbose” cosmetic
- “log_choice” reworded the description of “action” cosmetic
- “log_choice” reworded the description of “id” cosmetic
- “log_choice” reworded the description of “key” cosmetic
- “log_choice” reworded the description of “period” cosmetic
- “log_choice” reworded the description of “rating” cosmetic
- “recommend_tools” reworded the description of “budget” cosmetic
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 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.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 0
- DNSSEC: pass → fail ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “log_choice” rewrote its description, which is the text the model reads security
- Schema quality: 80 → 97 ▼ functional
- Tool coverage: 6% → 16% ▲ functional
- Server version: 2.4.0 → 2.5.1 functional
- “log_choice” added an optional parameter “fell_short” cosmetic
- “log_choice” added an optional parameter “period” cosmetic
- “log_choice” added an optional parameter “plan” cosmetic
- “log_choice” added an optional parameter “price_usd” cosmetic
- “log_choice” added an optional parameter “rating” cosmetic
- “log_choice” added an optional parameter “worked” cosmetic
- “log_choice” added an optional parameter “combo” cosmetic
- Tool “log_choice” changed its title: Log a choice → Log a choice or purchase cosmetic
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 5 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 Oct 2026 | 16 Jan 2027 | RSA 2048 | SHA256-RSA | 5a23bd59b1986aa43f11a96d3ad6a3e20ed |
| SANs: 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. | present | 19718 | 13 | Verified |
| vibecodepicks.com. | absent | 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 |
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 →
compare_tools Compare two tools ~145
Compare two named tools side by side when the user asks 'A vs B' or 'should I use A or B'. Inputs: `a`, `b` tool ids (use search to resolve names). Returns for each: category, lowest paid price and plan text, free tier, skill level, needs coding, best for, 2 strengths, 2 weaknesses, and the VCP comparison page URL. For more than two tools use recommend_tools or scenario.
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | yes | first tool id (use search to resolve names) |
| b | string | yes | second tool id (use search to resolve names) |
| verbose | boolean | – | returns long-form fields |
No output schema declared.
No examples provided.
fetch Get tool details ~186
Get one tool's profile when the user asks about a specific tool ('what does Cursor cost', 'does Bolt have a free plan', 'what's Lovable bad at'). Input: `id` from search/recommend results (e.g. 'cursor'); optional `fields` (summary, description, best_for, not_for, skill, coding, pricing, platforms, strengths, weaknesses, alternatives, video, compare, official, all). Default returns summary, who it's best for, lowest paid price and plan text, free tier text, 2 strengths, 2 weaknesses, go link (tracked link to the official site) and the VCP page URL to cite.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | which profile fields to return |
| id | string | yes | tool id from search/recommend results (e.g. 'cursor') |
| verbose | boolean | – | returns long-form fields |
No output schema declared.
No examples provided.
forget_me Forget me ~84
Permanently delete everything stored for the user's feed key: projects, interests, items shown, logged choices and purchases. Use when the user asks to stop the feed, delete their data, or be forgotten. Input: `key`. Returns ok and deleted count. Cannot be undone; confirm with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | – | the user's anonymous feed key from subscribe |
No output schema declared.
No examples provided.
list_alternatives Find alternatives ~139
List tools that can replace a given tool, for 'alternatives to X', 'cheaper/free tool like X', 'I'm leaving X'. Input: `tool` id; `limit`/`offset`. Returns rows id|name|lowest paid $/month|free tier (1/0) and the VCP alternatives page URL. Then fetch or compare_tools for details.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | number of results, default 5 |
| offset | integer | – | paging offset from the previous result |
| tool | string | yes | tool id to find alternatives for |
| verbose | boolean | – | returns long-form fields |
No output schema declared.
No examples provided.
list_categories List categories ~89
List VibeCodePicks' tool categories (e.g. editor, terminal, builder, agent, video, image) with the tool ids in each. Use when the user wants to browse a whole kind of tool ('show me all terminal coding agents') or you need valid category names. Takes no required input. Returns category → tool ids.
| Name | Type | Req | Description |
|---|---|---|---|
| verbose | boolean | – | returns long-form fields |
No output schema declared.
No examples provided.
list_scenarios List scenarios ~106
List the use cases VibeCodePicks tracks (e.g. landing-page, mobile-app, code-review, ai-game-development) with how often each was discussed and the top 3 tools people mention for it, from a dated window of public community posts. Use to find a scenario slug, or when the user asks 'what do people use for X'. No input. Returns slug, title, mention count, top tool ids, page URL, and the date window.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
log_choice Log a choice or purchase ~285
Record what the user decided about a tool for their project, after asking them: picked, rejected, tried, starred, purchased (a paid plan), or feedback (later, with a 1–5 rating and short what worked / fell short). Use when the user says 'I'll go with Bolt', 'Cursor didn't work for me', 'I bought Lovable Pro'. Never log silently. Inputs: `id`, `action`, optional `key`, and for purchased/feedback: plan, price_usd, period, rating, worked, fell_short, combo (other tool ids used together). No personal data. Returns ok. picked/rejected shape whats_new; it never changes rankings.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | what the user decided |
| combo | array | – | Ids of other tools used together with this one |
| fell_short | string | – | What fell short (short, no personal data) |
| id | string | yes | tool id |
| key | string | – | the user's anonymous feed key from subscribe |
| period | string | – | billing period |
| plan | string | – | Plan bought, e.g. 'Pro monthly' |
| price_usd | number | – | Price paid per period in USD |
| rating | integer | – | 1-5 rating for feedback |
| worked | string | – | What worked well (short, no personal data) |
No output schema declared.
No examples provided.
recommend_tools Recommend tools ~280
Recommend tools for what the user is building. Use for 'what should I use to build X', 'best free tool for a beginner who can't code', 'which AI tool fits my project'. Fill inputs from the conversation instead of asking when you already know them: `goal` (the project in plain words, required), `can_code` (true/false), `budget` ('free' or max USD per month), `platform` (e.g. 'web', 'ios', 'mac'), `limit`/`offset`. Returns ranked tools with a one-line why, the main caveat (what it is not good for), price from, free tier flag, page URL and go link. Rankings are not affected by saved preferences or payments. If the user has a feed key and later picks one, offer log_choice.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | string | – | 'free' or max USD per month |
| can_code | boolean | – | whether the user can code (true/false) |
| goal | string | yes | the project in plain words |
| limit | integer | – | number of results, default 5 |
| offset | integer | – | paging offset from the previous result |
| platform | string | – | target platform, e.g. 'web', 'ios', 'mac' |
| verbose | boolean | – | returns long-form fields |
No output schema declared.
No examples provided.
save_preferences Save your preferences ~190
Save which projects the user wants watched for new tools, e.g. 'my Next.js SaaS: auth, deploy, payments'. Use after subscribe, or when the user says they started/finished a project or changed interests. Replaces the whole list each time, so send all projects. Inputs: `key`; `projects` [{name, interests: short tags}]; `mode` 'by_interests' (only matching new tools) or 'all_new' (every new tool). Returns ok, project count, mode. Only whats_new reads this; it never changes search or recommendations.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | – | the user's anonymous feed key from subscribe |
| mode | string | – | 'by_interests' (only matching new tools) or 'all_new' (every new tool) |
| projects | array | yes | list of projects to watch (replaces the whole list each time) |
No output schema declared.
No examples provided.
scenario Scenario ranking ~151
Rank the tools people actually use for one use case, by number of community mentions in a dated window, with what users praise and complain about. Use for 'what's the best AI code review tool according to users', 'what do people use for mobile apps'. Input: `slug` from list_scenarios; `limit`. Returns per tool: id, mention count, main strengths and weak spots (M = most mentions, S = some), the date window and last update date. Say the window when quoting.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | number of results, default 5 |
| slug | string | yes | scenario slug from list_scenarios |
| verbose | boolean | – | returns long-form fields |
No output schema declared.
No examples provided.
search Search tools ~204
Keyword search over VibeCodePicks' reviewed AI coding and AI creation tools. Use when the user names a tool or a kind of tool ('is there an AI tool for deploying my app', 'find a no-code SaaS builder') and you need tool ids. Not for 'which is best for me' (use recommend_tools). Input: `query` (plain words, e.g. 'no-code SaaS builder'); `limit` (default 5), `offset` for paging. Returns one row per tool: id|name|category|lowest paid $/month|has free tier (1/0), and the next offset. Call fetch(id) for details.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | number of results, default 5 |
| offset | integer | – | paging offset from the previous result |
| query | string | yes | plain words, e.g. 'no-code SaaS builder' |
| verbose | boolean | – | returns long-form fields |
No output schema declared.
No examples provided.
subscribe Subscribe to the feed ~88
Start the user's personal new-tools watch. Only after the user has agreed to the feed (explain it first; see server instructions). Creates an anonymous key — no email or account. No input. Returns `key` and a note. Save the key in long-term memory / project rules (or connect with /api/mcp?k=KEY), then call save_preferences with their projects and chosen mode.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
whats_new What's new for you ~227
Check for new AI coding tools that match the user's saved projects. Use once a day (e.g. at the start of a work session) when the user has a feed key, or when they ask 'anything new for my project?'. Inputs: `key` (uses saved projects and mode, never repeats items, max 3 per day); without a key, optional `since` (date) and `interests` for a one-off look. Returns `new` count and one line per item: name, category, [project it matches], one-line summary, page URL. `{new:0}` means nothing new — say so briefly or stay silent. Has no effect on other tools.
| Name | Type | Req | Description |
|---|---|---|---|
| interests | array | – | interest tags to filter by, for a one-off look without a key |
| key | string | – | the user's anonymous feed key from subscribe |
| limit | integer | – | number of results, default 5 |
| since | string | – | only tools added on or after this date, format YYYY-MM-DD (default: 7 days ago) |
No output schema declared.
No examples provided.
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
claude mcp add --transport http suanrongbaicai-vibecodepicks 'https://vibecodepicks.com/api/mcp'
What is the VibeCodePicks MCP server?
VibeCodePicks is an MCP server listed in the public MCP registry as io.github.suanrongbaicai/vibecodepicks. Pick AI coding tools by goal: community-sentiment rankings, pricing, free tiers, alternatives. This page covers its hosted endpoint (https://vibecodepicks.com/api/mcp).
Is the VibeCodePicks MCP server safe to use?
VibeCodePicks scores 72 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 13 tools: search, fetch, recommend_tools, compare_tools, list_alternatives, and 8 more. Their descriptions and schemas cost roughly 2,174 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.