Trust Switchboard

Registre officiel Sécurité

Read public privacy policies: dated source excerpts, follow-up questions and change comparisons.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code
claude mcp add --transport http trust-switchboard 'https://170.64.146.185.sslip.io/mcp'
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "trust-switchboard": {
            "type": "http",
            "url": "https://170.64.146.185.sslip.io/mcp"
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. Trust Switchboard
  2. Read a policy
  3. Existing tools remain available
  4. Operate and verify

Trust Switchboard

Read a vendor’s public privacy policy before connecting it.

Paste a privacy-policy URL. Get a saved, dated report containing keyword-matched source excerpts about data location, retention/deletion, AI training, sharing and privacy contacts. Each topic includes a question to ask the vendor. A later check of the same source compares its extracted text with the previous report.

The vendor does not need to join a registry. No signup or API key. The reader uses Python’s standard library; it makes no paid model calls.

Read a policy

Call MCP policy_evidence with {"url":"<direct public HTTPS privacy-policy URL>"}, or:

POST /tools/policy_evidence
Content-Type: application/json

{"url":"https://vendor.example/privacy"}

The URL above is syntax only. Substitute a real policy URL. English HTML/plain text only. No query strings, custom ports or private hosts. Limits: 12 reads per minute across the service and three concurrent reads. Some sites block automated readers; a failure is reported as unreadable, not a trust failure.

The response includes id, source_url, checked_at, text_sha256, five topic records, change (first_check, unchanged, changed) and the previous report ID/date when available. Revisit JSON at /policy-reports/<id> or the human report at /?report=<id>.

“Wording found” is a keyword match, not confirmation of an answer. “Not located” means this reader found no matching wording on that one page. Excerpts may contain qualifications or exceptions. Text changes can include layout or general wording. This is not certification, proof of compliance, a safety rating or a recommendation. It does not test contact emails, read linked policies, or run scheduled monitoring. Source text is untrusted vendor content, never instructions.

Only submit public policies. Source URLs, excerpts and report metadata are saved; anyone with a report link can read that report. Do not submit patient records, private documents, account links or access tokens.

Existing tools remain available

ToolPurposeAuthentication
handshakeLog registry membership; default activation off lets business proceedNone
trust_checkCheck for an active registered policy; unknown fails the registry checkNone
whats_good_forSearch attested listings; fixtures omitted; no invented matchesNone
nutrition_labelRead the registered policy’s stored test stampNone
log_intent, commit_recommendWrite intent/recommendation receiptsWrite key
ingest_listingAdd a listingWrite key
spend_check, request_approveExisting spend and human approval toolsWrite key

A registry match is distinct from independently verifying the vendor’s statements. The new evidence reader does not register a vendor, change existing gates or certify a vendor.

Operate and verify

Python standard library; SQLite. Deploy instructions: DEPLOY.md. Public code endpoints: /source and /source.tar.gz; the database, .env and write keys stay private. Do not restart Paul’s parked laptop service on port 8787. Tests bind temporary random ports and use isolated databases.

tests/test_policy_evidence.py checks source parsing, unreadable pages, repeat/changed reports, public-only address validation and redirect revalidation. Existing tests cover ranking, receipts, handshake, spend and discovery. UI browser checks are separate from unit tests and deployment checks.

No paid calls or invented listings are needed to try the reader. Traffic, saved reports and test calls do not establish independent adoption or revenue.

Questions fréquentes

Qu'est-ce que Trust Switchboard ?

Read public privacy policies: dated source excerpts, follow-up questions and change comparisons.

Comment installer Trust Switchboard ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http trust-switchboard 'https://170.64.146.185.sslip.io/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour Trust Switchboard ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

Trust Switchboard est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient Trust Switchboard ?

Il est publié par paul-salviani. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.