# VibeCodePicks (remote · vibecodepicks.com)

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

- Trust score: 65/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `vibecodepicks.com`: 65/100 (this document), [markdown](https://verifymcp.io/servers/com-vibecodepicks-vibecodepicks/api-mcp.md), [page](https://verifymcp.io/servers/com-vibecodepicks-vibecodepicks/api-mcp)

## Channel facts

- Endpoint: `https://vibecodepicks.com/api/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `3.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (forget_me).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 55/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 70/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 11% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 31 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

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

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "com-vibecodepicks-vibecodepicks": {
      "url": "https://vibecodepicks.com/api/mcp/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-vibecodepicks-vibecodepicks": {
      "type": "http",
      "url": "https://vibecodepicks.com/api/mcp/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-vibecodepicks-vibecodepicks]
url = "https://vibecodepicks.com/api/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-vibecodepicks-vibecodepicks": {
      "type": "remote",
      "url": "https://vibecodepicks.com/api/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-vibecodepicks-vibecodepicks --url 'https://vibecodepicks.com/api/mcp/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-vibecodepicks-vibecodepicks:
    url: "https://vibecodepicks.com/api/mcp/"
```

### Netclaw

```json
{
  "McpServers": {
    "com-vibecodepicks-vibecodepicks": {
      "Transport": "http",
      "Url": "https://vibecodepicks.com/api/mcp/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-vibecodepicks-vibecodepicks -t streamable-http -u 'https://vibecodepicks.com/api/mcp/'
```

### Other

```json
{
  "mcpServers": {
    "com-vibecodepicks-vibecodepicks": {
      "type": "http",
      "url": "https://vibecodepicks.com/api/mcp/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 65, +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.

### 2026-11-17 (score 64, +1)

- [security] 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
- [cosmetic] “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”

### 2026-11-15 (score 63, +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.

### 2026-11-13 (score 62, 0)

- [security] 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
- [functional regression] Tool coverage: 19% → 11%
- [functional regression] 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”
- [cosmetic] “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”

### 2026-11-12 (score 62, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-11 (score 61)

First indexed and scored.

## MCP tools (30)

### `search` (~76 tokens)

Search tools

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

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `query` (string, required): e.g. 'no-code SaaS builder'
- `verbose` (boolean)

### `fetch` (~74 tokens)

Get tool details

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.

Input parameters:

- `fields` (array)
- `id` (string, required)
- `verbose` (boolean)

### `recommend_tools` (~565 tokens)

Recommend tools

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.

Input parameters:

- `budget` (string): 'free' or max USD/mo
- `can_code` (boolean)
- `forbidden_capabilities` (array): Capability ids the task must not need, e.g. ['text-to-video']. Unknown ids are ignored (they match nothing). Honoured by the capability matcher.
- `goal` (string, required)
- `hard_constraints` (array): Hard-constraint tokens, e.g. 'offline', 'windows-only', 'no-cloud-upload', 'budget-zero-no-card'. Unknown tokens are ignored. Honoured by the capability matcher.
- `limit` (integer)
- `offset` (integer)
- `platform` (string)
- `required_capabilities` (array): Capability ids the task must have, e.g. ['video-editing','auto-captions']. Unknown ids are dropped. Honoured by the capability matcher.
- `task` (object): Structured task (optional). The server validates it and rejects invalid tasks with an error. Honoured by the capability matcher.
- `verbose` (boolean)

### `compare_tools` (~40 tokens)

Compare two tools

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

Input parameters:

- `a` (string, required)
- `b` (string, required)
- `verbose` (boolean)

### `list_alternatives` (~55 tokens)

Find alternatives

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

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `tool` (string, required)
- `verbose` (boolean)

### `list_scenarios` (~31 tokens)

List scenarios

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

### `scenario` (~47 tokens)

Scenario ranking

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

Input parameters:

- `limit` (integer)
- `slug` (string, required)
- `verbose` (boolean)

### `list_categories` (~24 tokens)

List categories

Category and use-case keys with tool ids.

Input parameters:

- `verbose` (boolean)

### `whats_new` (~116 tokens)

What's new for you

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.

Input parameters:

- `interests` (array)
- `key` (string)
- `limit` (integer)
- `since` (string)

### `subscribe` (~97 tokens)

Subscribe to the feed

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

### `save_preferences` (~116 tokens)

Save your preferences

Replace the keyed-feed interest tags. Send allowed tags only (project types, platforms, budget, preferences) — do not send project names or other free text (they are dropped and never stored). Plus the feed mode ('by_interests' = only matching tools; 'all_new' = every new tool). Only used by whats_new.

Input parameters:

- `interests` (array): Allowed tags only (project types, platforms, budget, preferences). Do not send a project name.
- `key` (string)
- `mode` (string)

### `log_choice` (~358 tokens)

Log a choice or purchase

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.

Input parameters:

- `action` (string, required)
- `combo` (array): Ids of other tools used together with this one
- `event_id` (string)
- `id` (string, required)
- `idempotency_key` (string)
- `key` (string)
- `period` (string)
- `rating` (integer)

### `set_preferences` (~236 tokens)

Save preference tags

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.

Input parameters:

- `budget` (string)
- `key` (string)
- `platforms` (array)
- `preferences` (array)
- `project_types` (array)
- `tools_in_use` (array): Catalog ids of tools already in use

### `check_updates` (~109 tokens)

Check matching updates

Tools added or updated since this user's last check that match their saved tags. Optional since (YYYY-MM-DD or catalog v). When nothing matches, returns {new:0} — a minimal response when nothing new matches. Tracks last_checked. Max 3 items. Does not change recommend_tools. Optional key: same feed key passed to set_preferences, to read that project's profile.

Input parameters:

- `key` (string)
- `since` (string): YYYY-MM-DD or catalog version; defaults to last_checked

### `feedback` (~86 tokens)

Record feedback

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.

Input parameters:

- `action` (string, required)
- `key` (string)
- `tool_id` (string, required)

### `recommend_for_task` (~176 tokens)

Recommend for this project

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.

Input parameters:

- `goal` (string)
- `limit` (integer)
- `project_id` (string, required)
- `task` (object)

### `check_project_changes` (~267 tokens)

Check project changes

Check whether this project or the catalog changed since the last check in a way worth interrupting for. Returns silent unless there is a real signal (project stage change, or a catalog change that verifies an open need) AND a reliably 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.

Input parameters:

- `project_id` (string, required)

### `forget_me` (~71 tokens)

Forget me

Delete this client's anonymous id, tag profile and last_checked. Feedback is first folded into anonymous aggregate counters (tool_id × used/not_useful/not_relevant, no uid). Those aggregate counts are kept. If you pass a feed key, that keyed feed record is deleted too.

Input parameters:

- `key` (string)

### `project_upsert` (~215 tokens)

Create or update a project

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.

Input parameters:

- `capabilities` (array)
- `expected_version` (integer)
- `preferences` (object)
- `project_id` (string)
- `rejected_tools` (array)
- `rotate_token` (boolean)
- `stage` (string)
- `tools_in_use` (array)
- `type` (string)

### `project_get` (~60 tokens)

Get a project

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.

Input parameters:

- `project_id` (string, required)

### `project_list` (~58 tokens)

List projects

List your projects as full v2 archives (schema_version: 2 — lifecycle_stage, workflow_stage, capabilities, task_capabilities, known_context, used/rejected tools, version, updated_at). Owner credential only; a project token cannot list.

### `project_export` (~49 tokens)

Export a project

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.

Input parameters:

- `project_id` (string, required)

### `delete_project` (~120 tokens)

Delete a project

Delete one project you own (project_id), or ALL your projects (all:true, which also deletes your consent record). Deletion is permanent: the archive, its tokens, its events, its event dedup/meta/reversal keys and its check state are gone. 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.

Input parameters:

- `all` (boolean)
- `project_id` (string)

### `consent_get` (~33 tokens)

Get consent

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

### `consent_update` (~178 tokens)

Update consent

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.

Input parameters:

- `granted` (boolean, required)
- `receipt` (string)
- `scope` (string, required)

### `consent_request_receipt` (~147 tokens)

Request a consent receipt

Request a server-issued one-time consent receipt for a scope (followup / usage_collection / alliance / publish_reviews). Returns a receipt id and a confirm_url (absolute, environment-correct; the receipt id travels as a URL fragment, 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.

Input parameters:

- `scope` (string, required)

### `notification_ack` (~189 tokens)

Acknowledge a notification delivery

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.

Input parameters:

- `notif_id` (string, required)
- `project_id` (string, required)
- `receipt` (string, required)

### `record_decision` (~254 tokens)

Record a usage event

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.

Input parameters:

- `consent_version` (string, required)
- `event_id` (string, required)
- `event_type` (string, required)
- `evidence_level` (string, required)
- `observed_at` (string, required)
- `project_id` (string, required)
- `rating` (integer)
- `reverses_event_id` (string)
- `tool_id` (string, required)

### `project_bind_code` (~55 tokens)

Issue a binding code

Issue a one-time binding code (15 minutes, void after one use) so the same project can be bound in another AI client. Owner credential only; redeem it there with project_bind.

Input parameters:

- `project_id` (string, required)

### `project_bind` (~57 tokens)

Redeem a binding code

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.

Input parameters:

- `bind_code` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-vibecodepicks-vibecodepicks/api-mcp#diagnostics

## Score history

- 2026-11-21: 65
- 2026-11-20: 65
- 2026-11-19: 64
- 2026-11-18: 64
- 2026-11-17: 64
- 2026-11-16: 63
- 2026-11-15: 63
- 2026-11-14: 62
- 2026-11-13: 62
- 2026-11-12: 62
- 2026-11-11: 61

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

## Links

- Remote endpoint: https://vibecodepicks.com/api/mcp/
- Website: https://vibecodepicks.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-vibecodepicks-vibecodepicks/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-vibecodepicks-vibecodepicks/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-vibecodepicks-vibecodepicks/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-vibecodepicks-vibecodepicks/api-mcp
