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.

Garden: Free Binance SOLUSDT Trade Sample

REMOTE · GARDEN-MPP-TEST.BIMEIXISHUAI.WORKERS.DEV

Free Binance SOLUSDT trades: 30-row partial sample; no key or wallet. Not a complete minute.

0 this week 67 Trust /100

Last scanned (13 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Education and Research

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 Security46
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 295 tokens (~59/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 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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "read_paid_product" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • 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 (11)

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

Checks we could not complete (2)

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.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  • 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 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
  • 7 Nov 26 0
    • 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 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
  • 23 Oct 26 67
    • Tool “list_products” rewrote its description, which is the text the model reads security
    • Tool “preview_product” rewrote its description, which is the text the model reads security
    • Tool “read_free_product” rewrote its description, which is the text the model reads security
    • Tool “search_products” rewrote its description, which is the text the model reads security
    • Schema quality: 33 → 59 ▼ functional
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://garden-mpp-test.bimeixishuai.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=bimeixishuai.workers.dev CN=WE1,O=Google Trust Services,C=US 22 Oct 2026 20 Jan 2027 ECDSA 256 ECDSA-SHA256 40374be1b2babc630e78caa7a17dee76
SANs: bimeixishuai.workers.dev, *.bimeixishuai.workers.dev
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 garden-mpp-test.bimeixishuai.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://garden-mpp-test.bimeixishuai.workers.dev/mcp Verified 200
http (plaintext) http://garden-mpp-test.bimeixishuai.workers.dev/mcp Inconclusive 406
MCP tools · 5 exposed · ~295 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
list_products ~41

List public product metadata, including a free Binance SOLUSDT 30-row partial trade sample. No API key or wallet is needed; paid content is not returned.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

preview_product ~65

Read one product's public metadata, summary, version hash, price, and license without an API key or wallet. The free Binance SOLUSDT 30-row sample is partial, not a complete minute; its upstream redistribution rights are unconfirmed.

NameTypeReqDescription
product_idstringyes–

No output schema declared.

No examples provided.

read_free_product ~87

Read one free product in the current public snapshot without an API key or wallet. Includes a Binance SOLUSDT 30-row partial trade sample, not a complete minute or real-time data; market type, quantity units, and upstream redistribution rights are unverified. Check preview_product and pin expected_hash before reading.

NameTypeReqDescription
expected_hashstring––
product_idstringyes–

No output schema declared.

No examples provided.

read_paid_product ~46

Pay exactly 0.01 USDT0 on the configured Tempo network, then read one paid product.

NameTypeReqDescription
expected_hashstring––
product_idstringyes–

No output schema declared.

No examples provided.

search_products ~56

Search product IDs, titles, and human-written summaries, including the free Binance SOLUSDT trade sample (30 rows, not a complete minute). No API key or wallet; paid content is not returned.

NameTypeReqDescription
querystringyes–

No output schema declared.

No examples provided.

Install

How do I install the Garden: Free Binance SOLUSDT Trade Sample MCP server?

Garden: Free Binance SOLUSDT Trade Sample is a hosted endpoint at https://garden-mpp-test.bimeixishuai.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 · garden-mpp-test.bimeixishuai.workers.dev

# add to Claude Code
claude mcp add --transport http uncooe-garden-agent-platform 'https://garden-mpp-test.bimeixishuai.workers.dev/mcp'
Common questions

What is the Garden: Free Binance SOLUSDT Trade Sample MCP server?

Garden: Free Binance SOLUSDT Trade Sample is an MCP server listed in the public MCP registry as io.github.UnCooe/garden-agent-platform. Free Binance SOLUSDT trades: 30-row partial sample; no key or wallet. Not a complete minute. This page covers its hosted endpoint (https://garden-mpp-test.bimeixishuai.workers.dev/mcp).

Is the Garden: Free Binance SOLUSDT Trade Sample MCP server safe to use?

Garden: Free Binance SOLUSDT Trade Sample scores 67 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 Garden: Free Binance SOLUSDT Trade Sample MCP server expose?

Garden: Free Binance SOLUSDT Trade Sample exposes 5 tools: list_products, search_products, preview_product, read_free_product, read_paid_product. Their descriptions and schemas cost roughly 295 tokens of context every time the server is loaded.

Does the Garden: Free Binance SOLUSDT Trade Sample MCP server require authentication?

No. We connected to Garden: Free Binance SOLUSDT Trade Sample without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Garden: Free Binance SOLUSDT Trade Sample MCP server still maintained?

Garden: Free Binance SOLUSDT Trade Sample 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 Garden: Free Binance SOLUSDT Trade Sample MCP server?

VerifyMCP ran 11 checks on Garden: Free Binance SOLUSDT Trade Sample, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Garden: Free Binance SOLUSDT Trade Sample: Authorization and 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.