co.build

MCP server · hosted · v0.6.0 · build.co/cobuild

Online · tested 1h agoNEW · 2h agoSeen in the registry 1h ago

Open-source mods for the devices you own, with owner reports on what works.

What it does

co.build is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES

Local installNO

Live checkOnline · 23 tools

Version0.6.0

PriceNot in the registry

First seen04 Nov 2026

Last checked1h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1h ago (live check)

Hosted endpoint

https://co.build/mcp streamable-http

In Claude Code: claude mcp add --transport http co-build https://co.build/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "co-build": {
      "url": "https://co.build/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 1h ago

ONLINE co.build answered an MCP connection on 04 Nov 2026 and introduced itself as cobuild 0.6.0 (MCP protocol 2025-06-18).

23 tools offered to AI assistants

prepare_installation_report · After setup, ask the owner whether they want to share before preparing a sanitized draft. Include high-value notes for the next owner: actual setup time, prerequisites the README omits (required keys or accounts, cables, OS versions), steps
publish_installation_report · Publish the saved installation report preview under the connected user's public co.build account. Updating an existing report replaces its public text. Requires explicit user approval of the exact preview and public attribution. Pass the dr
prepare_feedback · After the owner has actually used a mod and agreed to leave feedback, prepare a private preview of a public post on its co.build page. kind: comment (praise, a bug, friction), feature_request (something it can't do yet), reply (to parentId,
publish_feedback · Post the saved feedback preview under the connected user's public co.build account. The mod's maintainer is notified as for a comment on the website. Requires explicit approval of the exact action and public text. Pass the draftId from prep
get_review_task · Defenders: a volunteer malware check of one whole mod co.build lists. Only when the user asked you to spend their quota on it; never start on your own. A standing schedule the user set up counts as asking. Returns one task as data, or task:
submit_review · Submit your check of a get_review_task task before its lease expires. verdict: no_issues_found (you read every readingPlan group, readingPlan.unread aside, and nothing crosses the bar), risky, malicious, or could_not_review with a reason. r
report_review_usage · After the main session submits one whole-mod review, report exact usage summed across its reviewing subagents: taskId, inputTokens (uncached), outputTokens, cacheReadTokens and cacheWriteTokens. All four counts are required together. totalT
release_review_task · Ends your own unsubmitted get_review_task lease now, without a verdict, so the mod goes back in the pool. When you stop early (the user says stop, an error, a limit), release every task you haven't submitted, then delete its folder. Only yo
submit_install_check · Every install reads the code first. Before running anything from a mod you're setting up for the user, download the exact commit you'll install from GitHub (get_mod's safety.setup.install.sha by default, or the newer commit the user chose)
get_my_devices · Read the connected user's private saved devices, including typed-in devices, together with devices from their approved installation reports. Use when the user asks what they own. Only the connected account is returned; this does not publish
get_my_installations · Read the connected user's current, public installation reports for follow-up or correction, and to recognize mods they use. Entries include newerRelease (version, url, publishedAt) or null, and lastFeedbackAt: when they last posted other fe
withdraw_installation_report · After the user explicitly asks to withdraw this report, remove its public feedback and installation count and cancel pending email follow-ups. Requires ownership. The withdrawn text is not restored; the user can later approve a new report f

Show 11 more

schedule_installation_followup · Schedule one installation check-in email for 1–72 hours from now, only after the user explicitly requests or agrees to that email. Delivery is to the connected account's verified email address. Scheduling authorizes that email, not publicat
cancel_installation_followup · Permanently cancel the connected user's pending installation check-in email at their explicit request. Leaves the installation report unchanged. Its one check-in cannot be restored or scheduled again. An email already sent or being sent can
get_installation_stats · Public distinct-owner counts for a catalog mod. Counts are user reports, not verified installations or success rates. An installation can be complete while functionality remains untested.
search · Find devices and public-source mods by device name, model, feature, or project name. Use concise keywords, e.g. 'WHOOP', 'Kindle', or 'sleep export'. Returns descriptions and up to 20 matches per page. Pass nextOffset as offset with the sam
get_top_mods · Answer what's most popular or rising, as co.build/top ranks it: across all devices, for one kind of device (categoryId, from the returned categories) or for the user's devices (deviceIds). Top is what's most used and trusted, weighing real
fetch · Read a device or mod found by search. Pass its exact prefixed ID, such as device:whoop or mod:open-health. Returns source text and a citation URL. Device results contain the first 20 mods; use get_device for further pages.
get_device · List a device's models, available and requested features, curated picks and public mods. Each goal's picks explain which mod suits whom and its caveat; mod goalIds connect projects to features. Accepts a device slug or device: ID. Optional
get_mod · Get a mod's source, license, maintenance status, model and platform support, caveats, subscription needs and documented setup. Then call get_feedback with the same modId for community reviews, reports and upvotes before recommending. Accept
get_feedback · Check real community experience before recommending a mod. Returns its co.build upvotes and paginated public comments, feature requests (featureRequest), replies and works/partly/broken reports with dates, helpful votes, model and firmware
prepare_report_link · After the user reports a setup outcome, prepare a co.build form link for them to review and submit. Does not post a comment, publish a result or change an account. Use only the outcome, model and firmware supplied or verified with the user;
compare_mods · Compare up to four shortlisted mods in one call. Includes the same details as get_mod and three newest get_feedback entries per mod, plus optional device/model/platform fit. This replaces those separate reads when feedbackStatus is availabl

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.

Fact	Value	Evidence	Source	Last confirmed
Hosted endpoint	https://co.build/mcp	DECLARED	SRC-001 Official MCP Registry	1h ago
Local install (package)	no	DECLARED	SRC-001 Official MCP Registry	1h ago
Remote access (hosted)	yes	DECLARED	SRC-001 Official MCP Registry	1h ago
Website	https://co.build	DECLARED	SRC-001 Official MCP Registry	1h ago
Registry status	active	DECLARED	SRC-001 Official MCP Registry	1h ago
Version	0.6.0	DECLARED	SRC-001 Official MCP Registry	1h ago
MCP server	yes	DECLARED	SRC-001 Official MCP Registry	1h ago

Change history

NEW04 Nov 2026
first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Is co.build still online?

Free alerts · no account▲ 0

Do you run co.build? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor co.buildLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Questions about co.build

How do I connect co.build?

Use the hosted endpoint https://co.build/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does co.build offer?

When Electra Index connected on 04 Nov 2026, it listed 23 tools: prepare_installation_report, publish_installation_report, prepare_feedback, publish_feedback, get_review_task, submit_review, report_review_usage, release_review_task and more. The full list is in "Live check" above.

Is co.build online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1h ago.