Trust Check
REMOTE · TRUST-CHECK.GM-TOOLS.WORKERS.DEV · SCANNED SEP 28
Crypto safety for agents on Base: token honeypot/tax test and safe-to-send address poisoning check.
Available components
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 251 tokens (~125/item across 2 items; 2 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 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
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
claude mcp add --transport http gmahar82-stack-trust-check 'https://trust-check.gm-tools.workers.dev/mcp'
{
"mcpServers": {
"gmahar82-stack-trust-check": {
"url": "https://trust-check.gm-tools.workers.dev/mcp"
}
}
} {
"servers": {
"gmahar82-stack-trust-check": {
"type": "http",
"url": "https://trust-check.gm-tools.workers.dev/mcp"
}
}
} [mcp_servers.gmahar82-stack-trust-check] url = "https://trust-check.gm-tools.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"gmahar82-stack-trust-check": {
"type": "remote",
"url": "https://trust-check.gm-tools.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add gmahar82-stack-trust-check --url 'https://trust-check.gm-tools.workers.dev/mcp' --transport streamable-http
mcp_servers:
gmahar82-stack-trust-check:
url: "https://trust-check.gm-tools.workers.dev/mcp" {
"McpServers": {
"gmahar82-stack-trust-check": {
"Transport": "http",
"Url": "https://trust-check.gm-tools.workers.dev/mcp"
}
}
} assistant mcp add gmahar82-stack-trust-check -t streamable-http -u 'https://trust-check.gm-tools.workers.dev/mcp'
{
"mcpServers": {
"gmahar82-stack-trust-check": {
"type": "http",
"url": "https://trust-check.gm-tools.workers.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 +8
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 26 Sept 26 61
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 28 Sept 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. | present | 60074 | 8 | Verified |
| workers.dev. | 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 |
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 |
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 →
check_address_safety Check if an address is safe to send funds to (Base) ~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).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Destination address |
| from | string | – | Your sending wallet, to detect look-alikes of addresses you recently used |
| known | array | – | Addresses you trust, for the look-alike check |
No output schema declared.
No examples provided.
check_token_safety Check if a token is safe to buy (Base) ~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.003 per check via x402 (USDC on Base).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Token contract address on Base |
No output schema declared.
No examples provided.
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. Crypto safety for agents on Base: token honeypot/tax test and safe-to-send address poisoning check. 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 69 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 2 tools: check_token_safety, check_address_safety. Their descriptions and schemas cost roughly 251 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 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.