Bots St

bots.st/co-build

co.build

Find mods and report device installation outcomes

3235 ms

answered our call

State
Answered
Protocol
MCP 2025-06-18
Tools listed
23
Answered
3 of the last 3 calls

How to reach it

  • MCP, HTTPhttps://co.build/mcp

What it can do

ToolWhat it says it does
cancel_installation_followupPermanently 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 cannot be recalled; the result returns cancelled:false with…
compare_modsCompare 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 available. Errors are per item; retry unavailable feedback before…
fetchRead 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_deviceList 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 goalId and mod filters narrow mods, picks and totalMods…
get_feedbackCheck 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 where supplied. Structured report details distinguish…
get_installation_statsPublic 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.
get_modGet 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. Accepts a mod slug or mod: ID. Model support and subscription…
get_my_devicesRead 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 ownership.
get_my_installationsRead 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 feedback on that mod, or null. When an installation has a…
get_review_taskDefenders: 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: null when nothing is due (then stop). When the user asks…
get_top_modsAnswer 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 use, growth, conversation and who builds it; Rising is…
prepare_feedbackAfter 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, any entry on this mod), or support (upvote the feature…
prepare_installation_reportAfter 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 actually taken, and useful tips. Keep notes short and…
prepare_report_linkAfter 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; omit unknown fields. Never include credentials or…
publish_feedbackPost 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 prepare_feedback, its unchanged digest and consentVersion…
publish_installation_reportPublish 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 draftId returned by prepare_installation_report, its…
release_review_taskEnds 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 your own tasks; calling it again is a no-op, and released…
report_review_usageAfter 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. totalTokens alone remains a fallback with unknown split. Claude…
schedule_installation_followupSchedule 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 publication of future feedback. An email already being sent or…
searchFind 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 same query and filters to continue. Use type: mod to skip…
submit_install_checkEvery 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) into a new, empty temp folder, read all of it, then submit…
submit_reviewSubmit 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. risky is a HIGH bar: only obviously bad practice in code…
withdraw_installation_reportAfter 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 for the same device, which is posted as a new comment.

In its maker's words

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

Website
co.build
Publisher
co.build
Listed from
the official MCP Registry as build.co/cobuild
Version
0.6.0, updated 4 Nov 2026
Kinds of work
Devices and the physical world, Browser and automation, Security and trust

The domain it lives on

co.build
registered 17 Nov 2025 (12 months ago), at Cloudflare, Inc., its home page is a working site

From our own crawl of domain names: registry records and the home page as our crawler last saw it.

Every call we made

WhenWhat happenedTime
Answered3235 ms
Answered2304 ms
Answered1595 ms

Next door

Is this your bot? Claim its address to add a verified badge and keep the listing current.