Skip to content

Trust Me Bro MCP server

to.trustmebro/trust-me-brotrustmebro.tostreamable-httpv1.30.0Scanned

Fact-check receipts: search published claim verdicts with cited evidence, or verify a new claim.

5 tools: 1 can delete or cancel things, 2 change things and 2 only read.

Tools: 1 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Trust Me Bro MCP server can do

The Trust Me Bro MCP server is published by trustmebro.to, a domain the MCP Registry verified. It has 5 tools. It can delete or cancel things (1 tool: verify_public_claim) and create or change data (2 tools: verify_quote and analyze_argument). 2 tools only read.

3 tools bring in text other people can write (verify_public_claim, verify_quote and analyze_argument).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 19, 2026, version 1.30.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Deletes or cancels 1Claude Code: deny
  • verify_public_claimVerify one standalone public factual claim using the existing TMB engine and linked API wallet.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Verify one standalone public factual claim using the existing TMB engine and linked API wallet. The submitted claim and resulting receipt/evidence become public. Submit only a claim the user explicitly agrees to publish; never send private chat, document context or requester identity. Existing account balance required; request_id deduplicates retries.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
Changes things 2Claude Code: ask
  • analyze_argumentAnalyze reasoning in a private passage of at most 100 words with the existing TMB fallacy checker and linked daily account allowance.Reads text others write1 finding

    Why it is in this group

    • The name "analyze_argument" says "analyze": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "analyze_argument" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "analyze_argument" says "analyze": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Analyze reasoning in a private passage of at most 100 words with the existing TMB fallacy checker and linked daily account allowance. Findings are tied to submitted text and include charitable readings. Does not verify factual truth or publish the input. Reuse request_id on retry.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • verify_quoteCheck citations and supporting passages for a short quotation or attribution using the existing TMB cite service and linked citation allowance.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Check citations and supporting passages for a short quotation or attribution using the existing TMB cite service and linked citation allowance. Input and findings remain private. Citation matches alone cannot establish the original speaker; reports limitations. Reuse request_id on retry.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • get_receiptRead an existing public receipt by its server-issued ID, including availability and stored evidence.No findings

    Why it is in this group

    • The name "get_receipt" says "get": a word for reading.
    Description, as the server wrote it
    Read an existing public receipt by its server-issued ID, including availability and stored evidence. Free and anonymous; never reconstructs missing verdicts or sources.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_receiptsSearch existing public Trust Me Bro receipts and their stored citations.No findings

    Why it is in this group

    • The name "search_receipts" says "search": a word for reading.
    Description, as the server wrote it
    Search existing public Trust Me Bro receipts and their stored citations. Free, anonymous, stored data only; does not run verification.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:19 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://trustmebro.to/.well-known/oauth-protected-resource/mcp
Authorization servers
https://trustmebro.to
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://trustmebro.to/mcp: tools/list returned 5 tools to an anonymous client, including verify_public_claim (destructive), verify_quote (write), analyze_argument (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "analyze_argument" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "analyze_argument" says "analyze": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools5 changed.~5 changedView diff

Install

Pinned to version 1.30.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http trust-me-bro https://trustmebro.to/mcp
claude mcp add --transport http trust-me-bro https://trustmebro.to/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__trust-me-bro__search_receipts",
      "mcp__trust-me-bro__get_receipt"
    ],
    "ask": [
      "mcp__trust-me-bro__verify_quote",
      "mcp__trust-me-bro__analyze_argument"
    ],
    "deny": [
      "mcp__trust-me-bro__verify_public_claim"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as trust-me-bro. Review it before you use it.

Capability tags behind 3 rules
  • mcp__trust-me-bro__verify_public_claim untrusted-input
  • mcp__trust-me-bro__verify_quote untrusted-input
  • mcp__trust-me-bro__analyze_argument untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/to.trustmebro/trust-me-bro/verify?hash=cac63f953ac9066239fcb7bc85e50f502c4e975db8ec0fa6f01b9c2e8f8e92ac" | jq -e '.changed == false'

Pinned hash cac63f953ac9, from Nov 19, 2026, 07:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/to.trustmebro/trust-me-bro/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for to.trustmebro/trust-me-bro
[![Anlyon Radar](https://radar.anlyon.com/badge/to.trustmebro/trust-me-bro.svg)](https://radar.anlyon.com/servers/to.trustmebro/trust-me-bro)

Source: MCP Registry. Synced Oct 21, 2026, 18:55 UTC.

Trust Me Bro MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Trust Me Bro MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Trust Me Bro MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: verify_public_claim.

Can the Trust Me Bro MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Trust Me Bro MCP server have?

5 tools: 1 destructive, 2 write, 2 read. verify_public_claim, verify_quote, analyze_argument, search_receipts and get_receipt.

Does the Trust Me Bro MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Trust Me Bro MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Trust Me Bro MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 5, 2026. Every change is on this page and in its Atom feed.