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.

Trust Switchboard

REMOTE · 170.64.146.185.SSLIP.IO · SCANNED SEP 20

Ask "Are you on Trust Switch?" before your agent deals with another agent. Free. Never blocks.

+4 this week 67 Trust /100
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 Security57
Transport & Reachability100
Schema Quality & AI Usability53
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 582 tokens (~52/item across 11 items; 11 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
  • Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Trust Switchboard MCP server?

Trust Switchboard is a hosted endpoint at https://170.64.146.185.sslip.io/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 · 170.64.146.185.sslip.io

# add to Claude Code
claude mcp add --transport http paul-salviani-trust-switchboard 'https://170.64.146.185.sslip.io/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "paul-salviani-trust-switchboard": {
      "url": "https://170.64.146.185.sslip.io/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "paul-salviani-trust-switchboard": {
      "type": "http",
      "url": "https://170.64.146.185.sslip.io/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.paul-salviani-trust-switchboard]
url = "https://170.64.146.185.sslip.io/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "paul-salviani-trust-switchboard": {
      "type": "remote",
      "url": "https://170.64.146.185.sslip.io/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add paul-salviani-trust-switchboard --url 'https://170.64.146.185.sslip.io/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  paul-salviani-trust-switchboard:
    url: "https://170.64.146.185.sslip.io/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "paul-salviani-trust-switchboard": {
      "Transport": "http",
      "Url": "https://170.64.146.185.sslip.io/mcp"
    }
  }
}
# add to Vellum
assistant mcp add paul-salviani-trust-switchboard -t streamable-http -u 'https://170.64.146.185.sslip.io/mcp'
// mcp.json
{
  "mcpServers": {
    "paul-salviani-trust-switchboard": {
      "type": "http",
      "url": "https://170.64.146.185.sslip.io/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.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 0
    • Schema quality: 492 → 582 functional
    • New tool “handshake” functional
  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

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 20 Sept 2026 · Probed https://170.64.146.185.sslip.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=170.64.146.185.sslip.io CN=YE2,O=Let's Encrypt,C=US 29 Aug 2026 27 Nov 2026 ECDSA 256 ECDSA-SHA384 5b7a11935866c6a8f2e4db47bb29ea16b6d
SANs: 170.64.146.185.sslip.io
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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 insecure

Validation of 170.64.146.185.sslip.io. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
sslip.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://170.64.146.185.sslip.io/mcp Verified 200
http (plaintext) http://170.64.146.185.sslip.io/mcp HTTPS enforced 308 https://170.64.146.185.sslip.io/mcp
MCP tools · 11 exposed · ~582 tokens

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 →

Tool Tokens
commit_recommend ~63

Call BEFORE every recommend. Runs trust_check, logs pass/fail, returns speak + receipt. Needs a write key.

NameTypeReqDescription
actionstringyes
policy_idstring
querystringyes
target_urlstringyes

No output schema declared.

No examples provided.

decide_approve ~38

Human tap. Public so the desk can approve without the org key.

NameTypeReqDescription
approval_idstringyes
decisionstringyes

No output schema declared.

No examples provided.

handshake ~90

Bot meets bot: ask 'Are you on Trust Switch?' before dealing with another agent or vendor. Records yes/no. While activation is off (default) business proceeds either way. Not a recommend gate; use trust_check for that.

NameTypeReqDescription
activationstring
askerstring
contextstring
their_answerstring
urlstringyes

No output schema declared.

No examples provided.

ingest_listing ~69

Ingest a listing and score uniqueness inside one pond. Needs a write key.

NameTypeReqDescription
namestringyes
one_linerstring
org_idstring
pondstring
summarystring
urlstringyes

No output schema declared.

No examples provided.

log_click ~45

Record that a human clicked an item after a receipt. Public.

NameTypeReqDescription
item_idstring
item_urlstringyes
receipt_idstring

No output schema declared.

No examples provided.

log_intent ~64

Log that you intend to recommend or act. Needs a write key. Returns receipt_id.

NameTypeReqDescription
actionstringyes
policy_idstring
querystringyes
resultstring
target_urlstringyes

No output schema declared.

No examples provided.

nutrition_label ~24

Stamp of what it is + last test.

NameTypeReqDescription
urlstringyes

No output schema declared.

No examples provided.

request_approve ~56

HITL pause. Agent waits; human taps yes. Needs a write key.

NameTypeReqDescription
actionstringyes
amount_usdnumber
querystringyes
target_urlstringyes

No output schema declared.

No examples provided.

spend_check ~48

Hard cap + allowlist; cannot override. Fail closed. Needs a write key.

NameTypeReqDescription
actionstringyes
amount_usdnumberyes
urlstringyes

No output schema declared.

No examples provided.

trust_check ~34

Pass/fail a URL against the live policy before recommending it to a human. Fail closed.

NameTypeReqDescription
urlstringyes

No output schema declared.

No examples provided.

whats_good_for ~51

Call before recommending. Attested only, unique-in-pond first, never invent. Empty if none.

NameTypeReqDescription
limitinteger
pondstring
querystringyes

No output schema declared.

No examples provided.

Common questions

What is the Trust Switchboard MCP server?

Trust Switchboard is an MCP server listed in the public MCP registry as io.github.paul-salviani/trust-switchboard. Ask "Are you on Trust Switch?" before your agent deals with another agent. Free. Never blocks. This page covers its hosted endpoint (https://170.64.146.185.sslip.io/mcp).

Is the Trust Switchboard MCP server safe to use?

Trust Switchboard scores 67 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 Trust Switchboard MCP server expose?

Trust Switchboard exposes 11 tools: whats_good_for, trust_check, handshake, log_intent, commit_recommend, and 6 more. Their descriptions and schemas cost roughly 582 tokens of context every time the server is loaded.

Does the Trust Switchboard MCP server require authentication?

No. We connected to Trust Switchboard without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Trust Switchboard MCP server still maintained?

Trust Switchboard is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.