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.

L2WS

REMOTE · MCP.L2WS.COM

Binance order book (L2), trades, SQL, backtests and AI price levels for BTC, ETH and SOL.

Available components

65 Trust /100

Last scanned (19 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

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 Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation not fully verified: no authorisation is required to call this server, and 13 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability57
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 497 tokens (~38/item across 13 items; 13 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 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
  • Structured output schemas are declared (31% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 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
  • HTTPS
  • 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.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 13 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 15 Nov 26 62

    First indexed and scored.

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://mcp.l2ws.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=l2ws.com CN=YE2,O=Let's Encrypt,C=US 14 Nov 2026 12 Feb 2027 ECDSA 256 ECDSA-SHA384 67d37bdf37f20c8ef201e7dcf8ce83b01eb
SANs: *.l2ws.com, l2ws.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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 secure

Validation of mcp.l2ws.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
l2ws.com. DS published 2371 13 Verified
mcp.l2ws.com. Verified address RRset verified with the apex keys
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 default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self'; connect-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.l2ws.com/mcp Verified 200
http (plaintext) http://mcp.l2ws.com/mcp HTTPS enforced 301 https://mcp.l2ws.com/mcp
MCP tools · 13 exposed · ~497 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
backtest_report ~38

Full report of a finished run: FARM, PnL, WR, DD, regimes, trades.

NameTypeReqDescription
run_idintegeryes–

No output schema declared.

No examples provided.

backtest_status ~31

Run status: queued | running (+progress) | done | failed.

NameTypeReqDescription
run_idintegeryes–

No output schema declared.

No examples provided.

catalog_streams ~47

List of data streams: name, tier, kind, day range, description. all=True also lists streams outside your plan, marked `available_on`.

NameTypeReqDescription
allboolean––
NameTypeReqDescription
resultarrayyes–

No examples provided.

get_ai_levels ~36

Recorded AI levels, prediction history and observed outcomes. Free access is delayed.

NameTypeReqDescription
model–––
symbolstring––

No output schema declared.

No examples provided.

get_ai_trader ~36

Our AI trader: training status, latest exam on held-out weeks after fees, released decisions (free: 24 h delay).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_contract_docs ~24

Strategy contract and sandbox rules (the same text as on /docs-contract).

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_quality ~31

Q index and data-quality metrics of a day (day as YYYY-MM-DD).

NameTypeReqDescription
daystringyes–

No output schema declared.

No examples provided.

get_schema ~22

Columns and types of a stream.

NameTypeReqDescription
streamstringyes–

No output schema declared.

No examples provided.

list_runs ~29

Latest runs: id, status, FARM, parameters, queue time.

NameTypeReqDescription
limitinteger––
NameTypeReqDescription
resultarrayyes–

No examples provided.

list_strategies ~22

My strategies: id, name, version, latest FARM.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

run_backtest ~82

Queue a backtest. Needs strategy_id OR code (a one-off strategy). Minutes are charged at queue time.

NameTypeReqDescription
capitalnumber––
code–––
date_fromstringyes–
date_tostringyes–
regime_reportboolean––
strategy_id–––
symbolsarrayyes–

No output schema declared.

No examples provided.

save_strategy ~45

Save a strategy (the contract is in get_contract_docs). Returns strategy_id, version and the lint result.

NameTypeReqDescription
codestringyes–
namestringyes–

No output schema declared.

No examples provided.

sql_query ~54

SELECT/WITH over the streams (the day is a virtual column `day`). The result holds at most min(limit, 50000) rows.

NameTypeReqDescription
limitinteger––
querystringyes–

No output schema declared.

No examples provided.

Install

How do I install the L2WS MCP server?

L2WS is a hosted endpoint at https://mcp.l2ws.com/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 · mcp.l2ws.com

# add to Claude Code
claude mcp add --transport http com-l2ws-l2ws 'https://mcp.l2ws.com/mcp'
Common questions

What is the L2WS MCP server?

L2WS is an MCP server listed in the public MCP registry as com.l2ws/l2ws. Binance order book (L2), trades, SQL, backtests and AI price levels for BTC, ETH and SOL. This page covers its hosted endpoint (https://mcp.l2ws.com/mcp).

Is the L2WS MCP server safe to use?

L2WS scores 65 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 L2WS MCP server expose?

L2WS exposes 13 tools: catalog_streams, get_schema, get_quality, sql_query, save_strategy, and 8 more. Their descriptions and schemas cost roughly 497 tokens of context every time the server is loaded.

Does the L2WS MCP server require authentication?

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

Is the L2WS MCP server still maintained?

L2WS 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 L2WS MCP server?

VerifyMCP ran 12 checks on L2WS, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about L2WS: Authorization. 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.