_ registry / mcp streamable-http · checked 1h ago

vibecodepicks

https://vibecodepicks.com

Registry code: 986318e8be70c7bd

api record

VibeCodePicks helps a person choose and keep track of AI coding tools (AI code editors, terminal coding agents, prompt-to-app builders, hosting/backends, AI agents frameworks, AI image/video tools) for their own projects. Use it when the user is deciding which tool to use for something they are building, wants a cheaper/free/open-source option, is comparing two named tools, or wants to hear about new tools that fit their projects. Do not use it for general coding help, for how to use a tool's features in depth, or for news unrelated to choosing tools.

Data: ~114 hand-reviewed tools with…

endpoint
https://vibecodepicks.com/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is vibecodepicks live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is vibecodepicks free to use?
Yes — the hub reached it with no key and no payment.
What tools does vibecodepicks have?
13 tools: scenario, log_choice, search, recommend_tools, list_alternatives, subscribe, fetch, whats_new, ….
Is vibecodepicks safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
281ms

last good check

priced tools
0

of 13 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 13 tools
2 open 11 never probed 2 of 13 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_categories open 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "verbose": {
      "type": "boolean",
      "description": "returns long-form fields"
    }
  }
}
    arguments 9 lines
  • list_scenarios open 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • scenario unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "scenario slug from list_scenarios"
    },
    "limit": {
      "type": "integer",
      "description": "number of results, default 5"
    },
    "verbose": {
      "type": "boolean",
      "description": "returns long-form fields"
    }
  }
}
    arguments 20 lines
  • log_choice unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id",
    "action"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "tool id"
    },
    "key": {
      "type": "string",
      "description": "the user's anonymous feed key from subscribe"
    },
    "plan": {
      "type": "string",
      "description": "Plan bought, e.g. 'Pro monthly'"
    },
    "combo": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Ids of other tools used together with this one"
    },
    "action": {
      "enum": [
        "picked",
        "rejected",
        "tried",
        "starred",
        "purchased",
        "feedback"
      ],
      "type": "string",
      "description": "what the user decided"
    },
    "period": {
      "enum": [
        "month",
        "year",
        "one_time"
      ],
      "type": "string",
      "description": "billing period"
    },
    "rating": {
      "type": "integer",
      "maximum": 5,
      "minimum": 1,
      "description": "1-5 rating for feedback"
    },
    "worked": {
      "type": "string",
      "description": "What worked well (short, no personal data)"
    },
    "price_usd": {
      "type": "number",
      "description": "Price paid per period in USD"
    },
    "fell_short": {
      "type": "string",
      "description": "What fell short (short, no personal data)"
    }
  }
}
    arguments 67 lines
  • search unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "description": "number of results, default 5"
    },
    "query": {
      "type": "string",
      "description": "plain words, e.g. 'no-code SaaS builder'"
    },
    "offset": {
      "type": "integer",
      "description": "paging offset from the previous result"
    },
    "verbose": {
      "type": "boolean",
      "description": "returns long-form fields"
    }
  }
}
    arguments 24 lines
  • recommend_tools unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "goal"
  ],
  "properties": {
    "goal": {
      "type": "string",
      "description": "the project in plain words"
    },
    "limit": {
      "type": "integer",
      "description": "number of results, default 5"
    },
    "budget": {
      "type": "string",
      "description": "'free' or max USD per month"
    },
    "offset": {
      "type": "integer",
      "description": "paging offset from the previous result"
    },
    "verbose": {
      "type": "boolean",
      "description": "returns long-form fields"
    },
    "can_code": {
      "type": "boolean",
      "description": "whether the user can code (true/false)"
    },
    "platform": {
      "type": "string",
      "description": "target platform, e.g. 'web', 'ios', 'mac'"
    }
  }
}
    arguments 36 lines
  • list_alternatives unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "tool"
  ],
  "properties": {
    "tool": {
      "type": "string",
      "description": "tool id to find alternatives for"
    },
    "limit": {
      "type": "integer",
      "description": "number of results, default 5"
    },
    "offset": {
      "type": "integer",
      "description": "paging offset from the previous result"
    },
    "verbose": {
      "type": "boolean",
      "description": "returns long-form fields"
    }
  }
}
    arguments 24 lines
  • subscribe unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • fetch unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "tool id from search/recommend results (e.g. 'cursor')"
    },
    "fields": {
      "enum": [
        "summary",
        "description",
        "best_for",
        "not_for",
        "skill",
        "coding",
        "pricing",
        "platforms",
        "strengths",
        "weaknesses",
        "alternatives",
        "video",
        "compare",
        "official",
        "all"
      ],
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "which profile fields to return"
    },
    "verbose": {
      "type": "boolean",
      "description": "returns long-form fields"
    }
  }
}
    arguments 40 lines
  • whats_new unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "key": {
      "type": "string",
      "description": "the user's anonymous feed key from subscribe"
    },
    "limit": {
      "type": "integer",
      "description": "number of results, default 5"
    },
    "since": {
      "type": "string",
      "description": "only tools added on or after this date, format YYYY-MM-DD (default: 7 days ago)"
    },
    "interests": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "interest tags to filter by, for a one-off look without a key"
    }
  }
}
    arguments 24 lines
  • save_preferences unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "projects"
  ],
  "properties": {
    "key": {
      "type": "string",
      "description": "the user's anonymous feed key from subscribe"
    },
    "mode": {
      "enum": [
        "by_interests",
        "all_new"
      ],
      "type": "string",
      "description": "'by_interests' (only matching new tools) or 'all_new' (every new tool)"
    },
    "projects": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "name",
          "interests"
        ],
        "properties": {
          "name": {
            "type": "string",
            "description": "project name"
          },
          "interests": {
            "type": "array",
            "items": {
              "type": "string"
            },
            "description": "short interest tags"
          }
        }
      },
      "description": "list of projects to watch (replaces the whole list each time)"
    }
  }
}
    arguments 44 lines
  • forget_me unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "key": {
      "type": "string",
      "description": "the user's anonymous feed key from subscribe"
    }
  }
}
    arguments 9 lines
  • compare_tools unknown 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "a",
    "b"
  ],
  "properties": {
    "a": {
      "type": "string",
      "description": "first tool id (use search to resolve names)"
    },
    "b": {
      "type": "string",
      "description": "second tool id (use search to resolve names)"
    },
    "verbose": {
      "type": "boolean",
      "description": "returns long-form fields"
    }
  }
}
    arguments 21 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 986318e8be70c7bd.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/986318e8be70c7bd/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/986318e8be70c7bd/badge.svg)](https://brick.blue/agent/986318e8be70c7bd?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.