Trust Me Bro
REMOTE · TRUSTMEBRO.TO
Fact-check receipts: search published claim verdicts with cited evidence, or verify a new claim.
Available components
Last scanned (2 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Search and Retrieval
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (verify_public_claim). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 415 tokens (~83/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 17 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 16 Oct 26 62
First indexed and scored.
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 18 Oct 2026 · Probed https://trustmebro.to/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=trustmebro.to | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 853e52f5e7a67d850eb8a86c40fa391b |
| SANs: trustmebro.to, *.trustmebro.to | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of trustmebro.to. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| to. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | object-src 'none'; base-uri 'self' |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=(), accelerometer=(), gyroscope=(), magnetometer=(), usb=(), midi=(), bluetooth=(), display-capture=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://trustmebro.to/mcp | Verified | 200 | |
| http (plaintext) | http://trustmebro.to/mcp | HTTPS enforced | 301 | https://trustmebro.to/mcp |
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 →
analyze_argument ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
get_receipt ~47
Read an existing public receipt by its server-issued ID, including availability and stored evidence. Free and anonymous; never reconstructs missing verdicts or sources.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt_id | string | yes | – |
No output schema declared.
No examples provided.
search_receipts ~53
Search existing public Trust Me Bro receipts and their stored citations. Free, anonymous, stored data only; does not run verification.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
verify_public_claim ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | – |
| publish_publicly | boolean | yes | – |
| request_id | string | yes | – |
No output schema declared.
No examples provided.
verify_quote ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
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.
remote · trustmebro.to
claude mcp add --transport http to-trustmebro-trust-me-bro 'https://trustmebro.to/mcp'
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.