# Trust Me Bro (remote · trustmebro.to)

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

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `trustmebro.to`: 63/100 (this document), [markdown](https://verifymcp.io/servers/to-trustmebro-trust-me-bro/trustmebro.md), [page](https://verifymcp.io/servers/to-trustmebro-trust-me-bro/trustmebro)

## Channel facts

- Endpoint: `https://trustmebro.to/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.30.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (verify_public_claim).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 415 tokens (~83/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Trust Me Bro MCP server?

Trust Me Bro is a hosted endpoint at https://trustmebro.to/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.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "to-trustmebro-trust-me-bro": {
      "url": "https://trustmebro.to/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "to-trustmebro-trust-me-bro": {
      "type": "http",
      "url": "https://trustmebro.to/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.to-trustmebro-trust-me-bro]
url = "https://trustmebro.to/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "to-trustmebro-trust-me-bro": {
      "type": "remote",
      "url": "https://trustmebro.to/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add to-trustmebro-trust-me-bro --url 'https://trustmebro.to/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  to-trustmebro-trust-me-bro:
    url: "https://trustmebro.to/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "to-trustmebro-trust-me-bro": {
      "Transport": "http",
      "Url": "https://trustmebro.to/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add to-trustmebro-trust-me-bro -t streamable-http -u 'https://trustmebro.to/mcp'
```

### Other

```json
{
  "mcpServers": {
    "to-trustmebro-trust-me-bro": {
      "type": "http",
      "url": "https://trustmebro.to/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-16 (score 62)

First indexed and scored.

## MCP tools (5)

### `search_receipts` (~53 tokens)

Search existing public Trust Me Bro receipts and their stored citations. Free, anonymous, stored data only; does not run verification.

Input parameters:

- `cursor`
- `limit` (integer)
- `query` (string, required)

### `get_receipt` (~47 tokens)

Read an existing public receipt by its server-issued ID, including availability and stored evidence. Free and anonymous; never reconstructs missing verdicts or sources.

Input parameters:

- `receipt_id` (string, required)

### `verify_public_claim` (~95 tokens)

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.

Input parameters:

- `claim` (string, required)
- `publish_publicly` (boolean, required)
- `request_id` (string, required)

### `verify_quote` (~71 tokens)

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.

Input parameters:

- `request_id` (string, required)
- `text` (string, required)

### `analyze_argument` (~77 tokens)

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.

Input parameters:

- `request_id` (string, required)
- `text` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/to-trustmebro-trust-me-bro/trustmebro#diagnostics

## Score history

- 2026-10-18: 63
- 2026-10-17: 63
- 2026-10-16: 62

## Common questions

### What is the Trust Me Bro MCP server?

Trust Me Bro is an MCP server listed in the public MCP registry as to.trustmebro/trust-me-bro. Fact-check receipts: search published claim verdicts with cited evidence, or verify a new claim. This page covers its hosted endpoint (https://trustmebro.to/mcp).

### Is the Trust Me Bro MCP server safe to use?

Trust Me Bro scores 63 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 Me Bro MCP server expose?

Trust Me Bro exposes 5 tools: search_receipts, get_receipt, verify_public_claim, verify_quote, analyze_argument. Their descriptions and schemas cost roughly 343 tokens of context every time the server is loaded.

### Does the Trust Me Bro MCP server require authentication?

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

### Is the Trust Me Bro MCP server still maintained?

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

## Links

- Remote endpoint: https://trustmebro.to/mcp
- Website: https://trustmebro.to/
- Changelog RSS feed: https://verifymcp.io/servers/to-trustmebro-trust-me-bro/trustmebro.xml
- Changelog JSON feed: https://verifymcp.io/servers/to-trustmebro-trust-me-bro/trustmebro.json
- HTML version of this page: https://verifymcp.io/servers/to-trustmebro-trust-me-bro/trustmebro