BioRobot

help.biorobotPublished by biorobot.helpv1.0.0Updated Oct 24, 2026

Human for hire by AI agents: ground-truth checks, photo evidence, errands near Crystal Lake, IL

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

BioRobot is a remote MCP endpoint that lets an AI assistant hire a human for ground-truth checks, photo evidence and errands near Crystal Lake, Illinois.

What you can do
Connect an assistant to a remote service for hiring human help with real-world tasks near Crystal Lake, Illinois. Request ground-truth checks that verify something in the physical world. Arrange photo evidence of a place or situation. Commission local errands. The manifest lists no individual tools, so the exact actions are not documented here.
When to use it
Use it when an assistant needs real-world verification, photographic proof or a small physical errand in the Crystal Lake, Illinois area that cannot be handled online.
Requirements
A remote MCP connection to the provider's hosted endpoint; no local package, account, API key or header is declared. The work happens in the Crystal Lake, Illinois area, so tasks depend on someone being available there.
Before you install
This involves hiring people for paid real-world work, so expect costs and terms set by the provider. Requests may involve sending task details and location information to the provider and to the person carrying them out. No authentication is declared, so check how requests and any payment are secured before relying on it.

Installation

In SourceWeft

  1. Open BioRobot in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/help.biorobot%2Fbiorobot/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "biorobot": {
      "type": "http",
      "url": "https://biorobot-mcp.biorobot.workers.dev/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestOct 11, 2026

Score

17% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.