Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SiliconBridge

REMOTE · SILICONBRIDGE.XYZ · SCANNED AUG 17

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

Available components

remote · siliconbridge.xyz 0
0 this week 0 Trust /100

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.

Trust breakdown (7 categories)

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 Security14
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.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.Unverified
Tool Safety–

Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.

Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 4 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.

Install

How do I install the SiliconBridge MCP server?

SiliconBridge is a hosted endpoint at https://siliconbridge.xyz/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 · siliconbridge.xyz

# add to Claude Code
claude mcp add --transport http aataqi-boop-siliconbridge 'https://siliconbridge.xyz/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "aataqi-boop-siliconbridge": {
      "url": "https://siliconbridge.xyz/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "aataqi-boop-siliconbridge": {
      "type": "http",
      "url": "https://siliconbridge.xyz/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.aataqi-boop-siliconbridge]
url = "https://siliconbridge.xyz/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "aataqi-boop-siliconbridge": {
      "type": "remote",
      "url": "https://siliconbridge.xyz/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add aataqi-boop-siliconbridge --url 'https://siliconbridge.xyz/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  aataqi-boop-siliconbridge:
    url: "https://siliconbridge.xyz/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "aataqi-boop-siliconbridge": {
      "Transport": "http",
      "Url": "https://siliconbridge.xyz/mcp"
    }
  }
}
# add to Vellum
assistant mcp add aataqi-boop-siliconbridge -t streamable-http -u 'https://siliconbridge.xyz/mcp'
// mcp.json
{
  "mcpServers": {
    "aataqi-boop-siliconbridge": {
      "type": "http",
      "url": "https://siliconbridge.xyz/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 15 Aug 26 0
    • DNSSEC: fail → pass ▲ security
  • 14 Aug 26 0
    • DNSSEC: pass → fail ▼ security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Aug 26 0
    • DNSSEC: unverified → pass ▲ security
  • 4 Aug 26 0
    • DNSSEC: pass → unverified ▼ security
  • 2 Aug 26 0
    • DNSSEC: pass → unverified ▼ security
    • Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 17 Aug 2026 · Probed https://siliconbridge.xyz/mcp

TLS invalid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Chain error: hostname_mismatch

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.up.railway.app CN=YE1,O=Let's Encrypt,C=US 29 Jul 2026 27 Oct 2026 ECDSA 256 ECDSA-SHA384 6da79bb561da3efeb0e751ca21abd3999fe
SANs: *.up.railway.app, up.railway.app
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of siliconbridge.xyz. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
xyz. present 3599, 18130 8, 8 Verified
siliconbridge.xyz. present 1134 13 Verified
siliconbridge.xyz. Verified address RRset verified with the apex keys
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://siliconbridge.xyz/mcp TLS failed
http (plaintext) http://siliconbridge.xyz/mcp HTTPS enforced 301 https://siliconbridge.xyz/mcp
MCP tools

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 →

No tool schema has been captured from this endpoint yet.

Common questions

What is the SiliconBridge MCP server?

SiliconBridge is an MCP server listed in the public MCP registry as io.github.aataqi-boop/siliconbridge. Human-in-the-loop API for AI agents. CAPTCHA, OTP, KYC, and approvals by real humans. This page covers its hosted endpoint (https://siliconbridge.xyz/mcp).

Does the SiliconBridge MCP server require authentication?

Its publisher declares no required credentials for SiliconBridge. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the SiliconBridge MCP server still maintained?

SiliconBridge has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.