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 Check

REMOTE · TRUST-CHECK.GM-TOOLS.WORKERS.DEV

Base crypto safety for agents: honeypot/tax test, address poisoning, rug feed, creator record.

0 this week 82 Trust /100

Last scanned (15 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

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 Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 585 tokens (~117/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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
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 5 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
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
  • 4 Nov 26 −1
    • Tool “deep_token_safety_report” rewrote its description, which is the text the model reads security
    • Stability: pass → 0.97 functional
  • 26 Oct 26 +1
    • Stability: 0.97 → pass security
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 21 Nov 2026 · Probed https://trust-check.gm-tools.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=gm-tools.workers.dev CN=YE1,O=Let's Encrypt,C=US 25 Sept 2026 24 Dec 2026 ECDSA 256 ECDSA-SHA384 606470fbbdc430388b58780c4bc65424568
SANs: *.gm-tools.workers.dev, gm-tools.workers.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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 trust-check.gm-tools.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. No DS 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://trust-check.gm-tools.workers.dev/mcp Verified 200
http (plaintext) http://trust-check.gm-tools.workers.dev/mcp Inconclusive 406
MCP tools · 5 exposed · ~585 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
check_address_safety ~136

Before sending crypto on Base, check the destination: scam blacklists, address poisoning (a look-alike of an address you really use; pass `from` = your wallet), token contracts and burn addresses where funds are lost, never-used addresses. Returns a verdict with reasons. 5 free checks per day, then $0.002 per check via x402 (USDC on Base).

NameTypeReqDescription
addressstringyesDestination address
fromstring–Your sending wallet, to detect look-alikes of addresses you recently used
knownarray–Addresses you trust, for the look-alike check

No output schema declared.

No examples provided.

check_token_creator ~99

Before buying a newly launched Base token, check the wallet that deployed it: how many of its earlier tokens Rug Watch followed, and how many collapsed (rug pull or dump). Verdict: serial_collapser / collapsed_before / no_collapses_seen / unknown. 5 free calls per day, then $0.002 per call via x402 (USDC on Base).

NameTypeReqDescription
addressstringyesCreator (deployer) wallet on Base

No output schema declared.

No examples provided.

check_token_safety ~115

Before buying a token on Base, check it: simulates a real buy and sell (honeypot and hidden-tax test), reads owner powers (mint, blacklist, fee changes, pause), whale concentration, liquidity lock and scam lists. Returns a verdict (scam / high_risk / caution / low_risk) with plain-language reasons. 5 free checks per day, then $0.002 per check via x402 (USDC on Base).

NameTypeReqDescription
addressstringyesToken contract address on Base

No output schema declared.

No examples provided.

deep_token_safety_report ~126

Full due diligence before a bigger buy of a Base token: the token check (buy/sell simulation, taxes, owner powers, whales, liquidity, scam lists) plus the creator's Rug Watch record, wallet check and first funder, the owner wallet, the token's liquidity history, website domain age, how often new Base tokens collapse, an AI summary and a what-to-do list. $0.10 per report via x402 (USDC on Base), no free calls; failures are not charged.

NameTypeReqDescription
addressstringyesToken contract address on Base

No output schema declared.

No examples provided.

recent_liquidity_collapses ~109

New Base tokens whose pool liquidity collapsed (fell 90%+ from its peak: a rug pull or a heavy dump) in the last hours, newest first, with peak and remaining liquidity, hours from launch and the creator wallet. Use it to exit positions and blocklist serial creators. 5 free calls per day, then $0.002 per call via x402 (USDC on Base).

NameTypeReqDescription
hoursinteger–Look-back window in hours (default 24)

No output schema declared.

No examples provided.

Install

How do I install the Trust Check MCP server?

Trust Check is a hosted endpoint at https://trust-check.gm-tools.workers.dev/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 · trust-check.gm-tools.workers.dev

# add to Claude Code
claude mcp add --transport http gmahar82-stack-trust-check 'https://trust-check.gm-tools.workers.dev/mcp'
Common questions

What is the Trust Check MCP server?

Trust Check is an MCP server listed in the public MCP registry as io.github.gmahar82-stack/trust-check. Base crypto safety for agents: honeypot/tax test, address poisoning, rug feed, creator record. This page covers its hosted endpoint (https://trust-check.gm-tools.workers.dev/mcp).

Is the Trust Check MCP server safe to use?

Trust Check scores 82 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 Check MCP server expose?

Trust Check exposes 5 tools: check_token_safety, check_address_safety, recent_liquidity_collapses, check_token_creator, deep_token_safety_report. Their descriptions and schemas cost roughly 585 tokens of context every time the server is loaded.

Does the Trust Check MCP server require authentication?

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

Is the Trust Check MCP server still maintained?

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

What did VerifyMCP test on the Trust Check MCP server?

VerifyMCP ran 12 checks on Trust Check, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Trust Check: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.