L2WS MCP server
com.l2ws/l2wsl2ws.comstreamable-httpv1.0.0Scanned
Binance order book (L2), trades, SQL, backtests and AI price levels for BTC, ETH and SOL.
13 tools: 5 change things and 8 only read.
- Reads private data · 2
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the L2WS MCP server can do
The L2WS MCP server is published by l2ws.com, a domain the MCP Registry verified. It has 13 tools. It can create or change data (5 tools: sql_query, save_strategy, run_backtest, backtest_status and 1 more), but cannot delete data. 8 tools only read.
2 tools read private data (sql_query and get_contract_docs).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 15, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
13 tools
Changes things 5Claude Code: ask
backtest_reportFull report of a finished run: FARM, PnL, WR, DD, regimes, trades.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Full report of a finished run: FARM, PnL, WR, DD, regimes, trades.
backtest_statusRun status: queued | running (+progress) | done | failed.No findings
Why it is in this group
- The name "backtest_status" says "status": a word for reading.
- The description's first verb is "run": a word for a change.
Description, as the server wrote it Run status: queued | running (+progress) | done | failed.
run_backtestQueue a backtest.No findings
Why it is in this group
- The name "run_backtest" says "run": a word for a change.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
Description, as the server wrote it Queue a backtest. Needs strategy_id OR code (a one-off strategy). Minutes are charged at queue time.
save_strategySave a strategy (the contract is in get_contract_docs).No findings
Why it is in this group
- The name "save_strategy" says "save": a word for a change.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
Description, as the server wrote it Save a strategy (the contract is in get_contract_docs). Returns strategy_id, version and the lint result.
sql_querySELECT/WITH over the streams (the day is a virtual column `day`).Reads private dataNo findings
Why it is in this group
- The name "sql_query" says "query": a word for reading.
- The description's first verb is "select": a word for a change.
What it can reach
- private-dataThe name "sql_query" says "query" and "sql": it reads databases.
Description, as the server wrote it SELECT/WITH over the streams (the day is a virtual column `day`). The result holds at most min(limit, 50000) rows.
Only reads 8Show 8 read-only tools
catalog_streamsList of data streams: name, tier, kind, day range, description.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it List of data streams: name, tier, kind, day range, description. all=True also lists streams outside your plan, marked `available_on`.
get_ai_levelsRecorded AI levels, prediction history and observed outcomes.No findings
Why it is in this group
- The name "get_ai_levels" says "get": a word for reading.
Description, as the server wrote it Recorded AI levels, prediction history and observed outcomes. Free access is delayed.
get_ai_traderOur AI trader: training status, latest exam on held-out weeks after fees, released decisions (free: 24 h delay).No findings
Why it is in this group
- The name "get_ai_trader" says "get": a word for reading.
Description, as the server wrote it Our AI trader: training status, latest exam on held-out weeks after fees, released decisions (free: 24 h delay).
get_contract_docsStrategy contract and sandbox rules (the same text as on /docs-contract).Reads private dataNo findings
Why it is in this group
- The name "get_contract_docs" says "get": a word for reading.
What it can reach
- private-dataThe name "get_contract_docs" says "get" and "doc": it reads documents.
- private-dataThe description's first sentence says "doc": it reads documents.
Description, as the server wrote it Strategy contract and sandbox rules (the same text as on /docs-contract).
get_qualityQ index and data-quality metrics of a day (day as YYYY-MM-DD).No findings
Why it is in this group
- The name "get_quality" says "get": a word for reading.
Description, as the server wrote it Q index and data-quality metrics of a day (day as YYYY-MM-DD).
get_schemaColumns and types of a stream.No findings
Why it is in this group
- The name "get_schema" says "get": a word for reading.
Description, as the server wrote it Columns and types of a stream.
list_runsLatest runs: id, status, FARM, parameters, queue time.No findings
Why it is in this group
- The name "list_runs" says "list": a word for reading.
Description, as the server wrote it Latest runs: id, status, FARM, parameters, queue time.
list_strategiesMy strategies: id, name, version, latest FARM.No findings
Why it is in this group
- The name "list_strategies" says "list": a word for reading.
Description, as the server wrote it My strategies: id, name, version, latest FARM.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 15, 2026, 13:18 UTC, unchanged since Nov 15, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.l2ws.com/mcp: tools/list returned 13 tools to an anonymous client, including sql_query (write), save_strategy (write), run_backtest (write), backtest_status (write), backtest_report (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http l2ws https://mcp.l2ws.com/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http l2ws https://mcp.l2ws.com/mcp --header 'Authorization: <your-authorization>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__l2ws__catalog_streams",
"mcp__l2ws__get_schema",
"mcp__l2ws__get_quality",
"mcp__l2ws__list_strategies",
"mcp__l2ws__list_runs",
"mcp__l2ws__get_contract_docs",
"mcp__l2ws__get_ai_levels",
"mcp__l2ws__get_ai_trader"
],
"ask": [
"mcp__l2ws__sql_query",
"mcp__l2ws__save_strategy",
"mcp__l2ws__run_backtest",
"mcp__l2ws__backtest_status",
"mcp__l2ws__backtest_report"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as l2ws. Review it before you use it.
Capability tags behind 2 rules
- mcp__l2ws__sql_query private-data
- mcp__l2ws__get_contract_docs private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.l2ws/l2ws/verify?hash=0814cef4845dce57b241fd00661c1a663b81be3fb347b1317e4651b242ecd41a" | jq -e '.changed == false'Pinned hash 0814cef4845d, from Nov 15, 2026, 03:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.l2ws/l2ws/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.l2ws/l2ws)Source: MCP Registry. Synced Nov 15, 2026, 03:17 UTC.
L2WS MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the L2WS MCP server safe?
- No scan can promise that. What its definitions show: 13 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the L2WS MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the L2WS MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the L2WS MCP server have?
- 13 tools: 5 write, 8 read. sql_query, save_strategy, run_backtest, backtest_status, backtest_report, catalog_streams, get_schema, get_quality and 5 more.
Does the L2WS MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the L2WS MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the L2WS MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.