Vibe Coding Builders (vibecoding.builders) is a directory of people who build with AI and the projects they launch. search_launches, get_project, search_builders and get_builder read public builders and approved projects, and work with no sign-in. get_my_page, manage_my_page, manage_my_project and submit_feedback need a sign-in and act as the signed-in member only. get_my_page reads the member's own page, with project ids and the review state of each project. manage_my_page changes the member's profile and story; manage_my_project adds a project or changes the story of an own project; submit_feedback sends a private note to the VCB team. A new project is not public until the VCB team reviews it; changes to the profile, the story and project story fields are live at once. A refused call is a result with isError, a status, a code and a message. A 409 result means a conflict that the message names, for example a project link that is already listed; a 429 result means the limit was reached, and retry_after_sec gives the wait in seconds.
Discoverability
0 pass · 1 partial0 passed · 1 partial8/100
Client listings and public setup information.
mcp.json or server-card.json
Either mcp.json or an MCP Server Card declaring this endpoint passes.
No matching mcp.json manifest or MCP Server Card was found at the checked URLs.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description83/100
Lists the public, approved projects on Vibe Coding Builders, newest listing first. The launch date is the date the project was listed, in Pacific time. Filters: words in the name or tagline, and a date range.
Describe the returned information so the agent knows whether it will answer the request.
Inputs45/100
3 of 5 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
query
Words to find in a project name or tagline.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
since
First listing date, YYYY-MM-DD, Pacific time, included.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
until
Last listing date, YYYY-MM-DD, Pacific time, included.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
limit
Not provided
Missing description. Explain what this value means and how to supply it.
offset
Not provided
Missing description. Explain what this value means and how to supply it.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description89/100
Returns one public, approved project on Vibe Coding Builders: name, tagline, description, link, stage, launch date, its VCB page and the builder with their newsletter or site link.
The description explains the capability, when to use it, and what to expect.
Inputs50/100
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
project
The project slug, the project id, or its vibecoding.builders link.
Clarify units, where to obtain this value, or conventions not already expressed in the schema.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
Expand internal abbreviations and remove technical prefixes from the display title.
Description78/100
Lists public builders on Vibe Coding Builders, the builder with the newest launch first. one_step_ahead_of gives the builders whose latest project is one stage after the given stage, for example launching for building.
The description explains the capability, when to use it, and what to expect.
Inputs44/100
2 of 4 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
query
Words to find. A builder matches when each word is in their username, name, expertise, or the tools of their projects (a tool name as typed, such as Claude Code, or its group, such as Claude).
Clear enough to supply this argument.
one_step_ahead_of
A stage. Returns builders whose latest project is at the next stage.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
limit
Not provided
Missing description. Explain what this value means and how to supply it.
offset
Not provided
Missing description. Explain what this value means and how to supply it.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "search_builders",
"title": "Search VCB builders",
"description": "Lists public builders on Vibe Coding Builders, the builder with the newest launch first. one_step_ahead_of gives the builders whose latest project is one stage after the given stage, for example launching for building.",
"inputSchema": {
"type": "object",
"properties": {
"limit": {
"type": "integer",
"default": 20,
"maximum": 50,
"minimum": 1
},
"query": {
"type": "string",
"maxLength": 100,
"description": "Words to find. A builder matches when each word is in their username, name, expertise, or the tools of their projects (a tool name as typed, such as Claude Code, or its group, such as Claude)."
},
"offset": {
"type": "integer",
"default": 0,
"maximum": 1000,
"minimum": 0
},
"one_step_ahead_of": {
"enum": [
"ideating",
"building",
"launching",
"launched",
"early_growth",
"scaling"
],
"type": "string",
"description": "A stage. Returns builders whose latest project is at the next stage."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Search VCB builders",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description91/100
Returns one public builder on Vibe Coding Builders: name, one line about them, their newsletter or site link, their VCB page, their latest launch and their approved projects.
The description explains the capability, when to use it, and what to expect.
Inputs96/100
Input documentation gives an agent enough context to populate the arguments.
username
The builder username, as in vibecoding.builders/builders/{username}, or that link.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_builder",
"title": "Get a VCB builder",
"description": "Returns one public builder on Vibe Coding Builders: name, one line about them, their newsletter or site link, their VCB page, their latest launch and their approved projects.",
"inputSchema": {
"type": "object",
"required": [
"username"
],
"properties": {
"username": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "The builder username, as in vibecoding.builders/builders/{username}, or that link."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Get a VCB builder",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
Returns the signed-in member's own Vibe Coding Builders page: the builder profile, the story fields and every project with its review state and ids. It reads only and changes nothing.
The description explains the capability, when to use it, and what to expect.
Inputs100/100
This tool declares no inputs, so argument descriptions are not needed.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_my_page",
"title": "Get my VCB page",
"description": "Returns the signed-in member's own Vibe Coding Builders page: the builder profile, the story fields and every project with its review state and ids. It reads only and changes nothing.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"title": "Get my VCB page",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
Expand internal abbreviations and remove technical prefixes from the display title.
Description88/100
Changes the signed-in member's own Vibe Coding Builders page. update_profile changes the builder profile; update_story changes the story page. Only the fields sent change. is_public true makes the page public. A page cannot be made private. Changes are live at once. Limits: 10 changes in 10 minutes, 40 a day.
The description explains the capability, when to use it, and what to expect.
Inputs50/100
17 of 27 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
action
Not provided
Missing description. Explain what this value means and how to supply it.
profile › name
Not provided
Missing description. Explain what this value means and how to supply it.
profile › display_name
Not provided
Missing description. Explain what this value means and how to supply it.
profile › bio
Not provided
Missing description. Explain what this value means and how to supply it.
profile › website_url
A full http(s) link, or null to clear it.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
profile › twitter_handle
The handle without @.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
profile › github_handle
The handle without @.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
profile › newsletter_url
A full http(s) link, or null to clear it.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
profile › avatar_url
A full https link to a picture.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
profile › expertise
Things the member knows well; at least 1 when sent.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
profile › themes
Themes of their work.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
profile › featured_project_ids
Up to 2 of the member's own project ids, first = pinned.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
profile › support_description
Not provided
Missing description. Explain what this value means and how to supply it.
profile › support_link
A full http(s) link, or null to clear it.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
profile › is_public
true makes the page public. A page cannot be made private.
Clear enough to supply this argument.
story › headline_quote
A short quote of the member, shown at the top.
Clear enough to supply this argument.
story › headline_quote_source_url
Where the quote was said.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
story › pull_quote
Not provided
Missing description. Explain what this value means and how to supply it.
story › pull_quote_source_url
A full http(s) link, or null to clear it.
Clear enough to supply this argument.
story › location
Not provided
Missing description. Explain what this value means and how to supply it.
story › primary_cta_label
The words on the main button, for example "Read my newsletter".
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
story › primary_cta_url
Where the main button goes.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
story › pinned_project_id
One of the member's own project ids to show first.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
story › story_extra › items › date
YYYY-MM-DD
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
story › story_extra › items › title
Not provided
Missing description. Explain what this value means and how to supply it.
story › story_extra › items › source_url
Not provided
Missing description. Explain what this value means and how to supply it.
story › story_extra › items › project_id
Not provided
Missing description. Explain what this value means and how to supply it.
Name the specific action and subject instead of using a generic label such as ‘manage’ or ‘tool’.
Description91/100
create adds a new project to the signed-in member's Vibe Coding Builders page. A new project is not public until the VCB team reviews it; the answer says review: waiting. A create makes the member's builder page public in the Builders list when the page has a name and 1 or more areas of expertise. update changes the standout fact and its source link (standout_source_url), next step and 4 build answers of one of the member's own projects; these changes are live at once. The name, tagline and link change only on the project's edit page (edit_url). A 409 result on create means the link is already listed. Limits: 3 new projects a day; 10 project changes in 10 minutes and 40 a day.
The description explains the capability, when to use it, and what to expect.
Inputs45/100
11 of 20 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
action
Not provided
Missing description. Explain what this value means and how to supply it.
project › name
The project name.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
project › tagline
One line that says what it does.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
project › description
Not provided
Missing description. Explain what this value means and how to supply it.
project › website_url
A public http(s) link to the project.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
project › category
For example Productivity, Developer Tools, Education.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
project › lifecycle_stage
Not provided
Missing description. Explain what this value means and how to supply it.
project › launch_date
YYYY-MM-DD, if launched.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
project › tech_stack
Languages, frameworks and services.
Clear enough to supply this argument.
project › ai_tools
The AI tools used to build it, for example Claude Code, Cursor.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
project › infrastructure
Hosting and data, for example Vercel, Supabase.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
project › tags
Short tags.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
id
For update: the id of one of the member's own projects, as the member's page lists it.
Clear enough to supply this argument.
fields › standout_fact
Not provided
Missing description. Explain what this value means and how to supply it.
fields › standout_source_url
A full http(s) link, or null to clear it.
Clear enough to supply this argument.
fields › next_step
Not provided
Missing description. Explain what this value means and how to supply it.
fields › build_answers › what_it_does
Not provided
Missing description. Explain what this value means and how to supply it.
fields › build_answers › how_built
Not provided
Missing description. Explain what this value means and how to supply it.
fields › build_answers › what_changed
Not provided
Missing description. Explain what this value means and how to supply it.
fields › build_answers › whats_next
Not provided
Missing description. Explain what this value means and how to supply it.
Annotations100/100
All four behavior hints are declared.
{
"title": "Add or change my VCB project",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": true
}
Output schema0/100
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "manage_my_project",
"title": "Add or change my VCB project",
"description": "create adds a new project to the signed-in member's Vibe Coding Builders page. A new project is not public until the VCB team reviews it; the answer says review: waiting. A create makes the member's builder page public in the Builders list when the page has a name and 1 or more areas of expertise. update changes the standout fact and its source link (standout_source_url), next step and 4 build answers of one of the member's own projects; these changes are live at once. The name, tagline and link change only on the project's edit page (edit_url). A 409 result on create means the link is already listed. Limits: 3 new projects a day; 10 project changes in 10 minutes and 40 a day.",
"inputSchema": {
"type": "object",
"required": [
"action"
],
"properties": {
"id": {
"type": "string",
"format": "uuid",
"maxLength": 36,
"description": "For update: the id of one of the member's own projects, as the member's page lists it."
},
"action": {
"enum": [
"create",
"update"
],
"type": "string"
},
"fields": {
"type": "object",
"properties": {
"next_step": {
"type": [
"string",
"null"
],
"maxLength": 200
},
"build_answers": {
"type": [
"object",
"null"
],
"properties": {
"how_built": {
"type": [
"string",
"null"
],
"maxLength": 2000
},
"whats_next": {
"type": [
"string",
"null"
],
"maxLength": 2000
},
"what_changed": {
"type": [
"string",
"null"
],
"maxLength": 2000
},
"what_it_does": {
"type": [
"string",
"null"
],
"maxLength": 2000
}
},
"description": "All 4 answers as a whole; an empty answer is left out, and all empty clears them.",
"additionalProperties": false
},
"standout_fact": {
"type": [
"string",
"null"
],
"maxLength": 400
},
"standout_source_url": {
"type": [
"string",
"null"
],
"maxLength": 2000,
"description": "A full http(s) link, or null to clear it."
}
},
"description": "For update: the project story fields to change. Only the fields sent change.",
"additionalProperties": false
},
"project": {
"type": "object",
"required": [
"name",
"category",
"lifecycle_stage"
],
"properties": {
"name": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "The project name."
},
"tags": {
"type": "array",
"items": {
"type": "string",
"maxLength": 30
},
"maxItems": 10,
"description": "Short tags."
},
"tagline": {
"type": "string",
"maxLength": 200,
"description": "One line that says what it does."
},
"ai_tools": {
"type": "array",
"items": {
"type": "string",
"maxLength": 50
},
"maxItems": 15,
"description": "The AI tools used to build it, for example Claude Code, Cursor."
},
"category": {
"type": "string",
"maxLength": 50,
"minLength": 1,
"description": "For example Productivity, Developer Tools, Education."
},
"tech_stack": {
"type": "array",
"items": {
"type": "string",
"maxLength": 50
},
"maxItems": 20,
"description": "Languages, frameworks and services."
},
"description": {
"type": "string",
"maxLength": 1000
},
"launch_date": {
"type": "string",
"description": "YYYY-MM-DD, if launched."
},
"website_url": {
"type": "string",
"maxLength": 2000,
"description": "A public http(s) link to the project."
},
"infrastructure": {
"type": "array",
"items": {
"type": "string",
"maxLength": 50
},
"maxItems": 15,
"description": "Hosting and data, for example Vercel, Supabase."
},
"lifecycle_stage": {
"enum": [
"ideating",
"building",
"launching",
"launched",
"early_growth",
"scaling",
"sold",
"discontinued"
],
"type": "string"
}
},
"description": "For create: the new project.",
"additionalProperties": false
}
},
"additionalProperties": false
},
"annotations": {
"title": "Add or change my VCB project",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description87/100
Sends private feedback about the Vibe Coding Builders site to the VCB team, as the signed-in member: a bug, an idea, or anything else. Only VCB admins read it; it is not public. The same message within 24 hours returns the first one (replayed: true). Limits: 5 in 10 minutes, 20 a day.
Describe the returned information so the agent knows whether it will answer the request.
Inputs83/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
message
The feedback, in the member's words.
Clear enough to supply this argument.
category
Default: other.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
page_url
The vibecoding.builders page it is about, if any (full https link).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
Annotations100/100
All four behavior hints are declared.
{
"title": "Send feedback to the VCB team",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
Output schema0/100
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "submit_feedback",
"title": "Send feedback to the VCB team",
"description": "Sends private feedback about the Vibe Coding Builders site to the VCB team, as the signed-in member: a bug, an idea, or anything else. Only VCB admins read it; it is not public. The same message within 24 hours returns the first one (replayed: true). Limits: 5 in 10 minutes, 20 a day.",
"inputSchema": {
"type": "object",
"required": [
"message"
],
"properties": {
"message": {
"type": "string",
"maxLength": 4000,
"minLength": 1,
"description": "The feedback, in the member's words."
},
"category": {
"enum": [
"bug",
"idea",
"other"
],
"type": "string",
"description": "Default: other."
},
"page_url": {
"type": "string",
"maxLength": 2000,
"description": "The vibecoding.builders page it is about, if any (full https link)."
}
},
"additionalProperties": false
},
"annotations": {
"title": "Send feedback to the VCB team",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}
Loading score analytics…
Put your MCP to the test
A few tasks worth trying with this server, chosen from its reviewed tools. These have not been run.
01Search VCB launchesLists the public, approved projects on Vibe Coding Builders, newest listing first.
02Search VCB buildersLists public builders on Vibe Coding Builders, the builder with the newest launch first.
03Get a VCB projectReturns one public, approved project on Vibe Coding Builders: name, tagline, description, link, stage, launch date, its VCB page and the builder with their n…
04Get a VCB builderReturns one public builder on Vibe Coding Builders: name, one line about them, their newsletter or site link, their VCB page, their latest launch and their a…
05Get my VCB pageReturns the signed-in member's own Vibe Coding Builders page: the builder profile, the story fields and every project with its review state and ids.
Want to run these tasks against your MCP server with us?
How do I add Vibe Coding Builders to Claude, ChatGPT, or Cursor?
Add Vibe Coding Builders to Claude, ChatGPT, or Cursor by connecting its remote MCP URL in each client's MCP settings. In Claude, add a custom connector. In ChatGPT, add an MCP app. In Cursor, add an MCP server under Settings. The MCP URL is https://www.vibecoding.builders/api/mcp.
Is Vibe Coding Builders MCP ready for ChatGPT and Claude?
As of November 21, 2026, Vibe Coding Builders scores 100/100 on Manufact's MCP publishing checklist. The scan meets ChatGPT publishing checks and meets Claude publishing checks. Passing these checks does not guarantee marketplace approval.
How clear is Vibe Coding Builders's MCP tool documentation?
As of November 21, 2026, Vibe Coding Builders scores 72/100 in Manufact's review of tool titles, descriptions, input and output schemas, and behavior annotations. The review covers 8 of 8 discovered tools. The quality score measures documentation clarity; runtime behavior and marketplace readiness require separate checks.
How can Vibe Coding Builders improve its MCP documentation?
search_builders is the lowest-scoring reviewed tool at 63/100. No output schema is declared. Add one for structured results so clients can interpret returned fields. Open its review for feedback and a copyable fix prompt, then rerun the documentation review after updating your tool metadata.
Not your MCP?
Review any public or OAuth MCP server for protocol compatibility, tool documentation, and ChatGPT and Claude publishing readiness. No account required.