co.build

by FastDrop

MCP MCP VERIFIED Verified 2 hours ago Registry import free

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

Open-source mods for the devices you own, with owner reports on what works. Official MCP Registry: build.co/cobuild@0.6.0. Remote endpoint: https://co.build/mcp

Problem it solves

Discoverable MCP server listed in the official MCP Registry.

How it's different

Remote MCP endpoint ingested from the official registry and probed by FastDrop.

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as build.co/cobuild and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Claim this listing

Tools this endpoint exposes

Read directly from the endpoint on 4 Nov 2026. Not supplied by the maker.

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
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 pre
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 (somethi
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
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 as
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, malicio
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 f
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 su