BioRobot
REMOTE · BIOROBOT-MCP.BIOROBOT.WORKERS.DEV
Human for hire by AI agents: ground-truth checks, photo evidence, errands near Crystal Lake, IL
Available components
Last scanned (13 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 15 Oct 2026.
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 −4
The score moved with no change recorded against any check. We would rather say so than guess.
- 21 Oct 26 −3
The score moved with no change recorded against any check. We would rather say so than guess.
- 20 Oct 26 −4
The score moved with no change recorded against any check. We would rather say so than guess.
- 19 Oct 26 −3
The score moved with no change recorded against any check. We would rather say so than guess.
- 18 Oct 26 −4
The score moved with no change recorded against any check. We would rather say so than guess.
- 16 Oct 26 0
- Endpoint reachability: not serving MCP → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HTTPS: unverified → pass ▲ security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- 14 Oct 26 −43
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 13 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Oct 2026 · Probed https://biorobot-mcp.biorobot.workers.dev/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of biorobot-mcp.biorobot.workers.dev. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| biorobot-mcp.biorobot.workers.dev. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://biorobot-mcp.biorobot.workers.dev/mcp | Unreachable | ||
| http (plaintext) | http://biorobot-mcp.biorobot.workers.dev/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_service_area ~50
Check whether a US ZIP code is inside BioRobot's 50-mile service area around Crystal Lake, IL 60014.
| Name | Type | Req | Description |
|---|---|---|---|
| zip_code | string | yes | 5-digit US ZIP code to check |
No output schema declared.
No examples provided.
get_estimate ~94
Price estimate for a BioRobot task from distance and time. Formula: $25 base + $100/hr (15-min increments) + $0.70/mile round trip from ZIP 60014, $40 minimum.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | number | yes | Estimated on-site hours (billed in 15-minute increments) |
| miles_one_way | number | yes | One-way miles from ZIP 60014 to the task location |
No output schema declared.
No examples provided.
get_service_info ~30
What BioRobot does, the service area, transparent pricing, and how to order. Call this first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
submit_task ~168
Submit a task order to BioRobot. A human reviews every request before acceptance — no work starts until scope, price, and proof requirements are agreed. Use get_estimate and check_service_area first when unsure.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_notes | string | – | Budget constraints or pricing notes |
| contact_email | string | yes | Requester's email for the quote and follow-up |
| contact_name | string | yes | Requester's name |
| location | string | yes | Where the task happens (address, ZIP, or landmark) |
| proof_requirements | string | – | What evidence to return (photos, timestamps, GPS, video, etc.) |
| task_description | string | yes | What the human should do, in detail |
| timing | string | yes | When it needs to happen (date/time window, deadline, flexibility) |
No output schema declared.
No examples provided.
How do I install the BioRobot MCP server?
BioRobot is a hosted endpoint at https://biorobot-mcp.biorobot.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · biorobot-mcp.biorobot.workers.dev
claude mcp add --transport http help-biorobot-biorobot 'https://biorobot-mcp.biorobot.workers.dev/mcp'
What is the BioRobot MCP server?
BioRobot is an MCP server listed in the public MCP registry as help.biorobot/biorobot. Human for hire by AI agents: ground-truth checks, photo evidence, errands near Crystal Lake, IL. This page covers its hosted endpoint (https://biorobot-mcp.biorobot.workers.dev/mcp).
Is the BioRobot MCP server safe to use?
BioRobot scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the BioRobot MCP server expose?
BioRobot exposes 4 tools: get_service_info, get_estimate, check_service_area, submit_task. Their descriptions and schemas cost roughly 342 tokens of context every time the server is loaded.
Does the BioRobot MCP server require authentication?
Its publisher declares no required credentials for BioRobot. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the BioRobot MCP server still maintained?
BioRobot has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 15 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.