SiliconBridge

io.github.aataqi-boopPublished by GitHub account aataqi-boopv1.0.0Updated Oct 24, 2026

Human-in-the-loop API for AI agents. CAPTCHA, OTP, KYC, and approvals by real humans.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowSecurity & Monitoring

Overview

AI-generated overview

SiliconBridge is a remote MCP endpoint that lets an assistant route CAPTCHA, OTP, KYC and approval steps to real humans for completion.

What you can do
Hand off human-in-the-loop steps to real people: CAPTCHA solving, one-time passcodes, KYC checks and approval requests, as described by the provider. No individual tools are listed in the manifest, so the exact operations an assistant can call are not documented here.
When to use it
Consider it when an agent workflow stalls on a step that only a person can complete, such as a CAPTCHA, an OTP, an identity check or a sign-off, and you want that step handled by a human rather than abandoned.
Requirements
A remote streamable HTTP endpoint at the provider's address; no local package, environment variables or headers are declared. The manifest declares no authentication, so how accounts or access are handled is not stated.
Before you install
The service involves real people handling verification steps, so data passed along may include personal or identity information for KYC and OTP flows; check what is sent and to whom. No authentication is declared, and no tool list or documentation is provided, so review the provider's terms before relying on it.

Installation

In SourceWeft

  1. Open SiliconBridge 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/io.github.aataqi-boop%2Fsiliconbridge/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": {
    "siliconbridge": {
      "type": "http",
      "url": "https://siliconbridge.xyz/mcp"
    }
  }
}

Tools

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

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

28% 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
  • 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.