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.

Layer

REMOTE · USELAYER.SH

Find the same prediction market on Kalshi and Polymarket, with live prices and profit after fees.

Available components

+1 this week 72 Trust /100

Last scanned (19 hours ago)

Scores higher than 57% 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 Security80
  • 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 is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 255 tokens (~127/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 Management0
  • Stability check failed: schema churn in the 9 days we've observed: 3 tool removals, 0 breaking changes, 0 auth/transport breaks, 2 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).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 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

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

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.

  • 18 Nov 26 −1
    • Stability: 0.17 → fail ▼ security
    • Tool “check_profit” was removed ▼ security
    • Tool “find_matches” was removed ▼ security
    • Tool “lookup_match” was removed ▼ security
    • Tool “sandbox_find_markets” was removed ▼ security
    • Tool “sandbox_list_orders” was removed ▼ security
    • Tool “sandbox_place_order” was removed ▼ security
    • Tool “sandbox_preview_order” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “sandbox_account” rewrote its description, which is the text the model reads security
    • Schema quality: fail → pass ▲ functional
    • Server version: 0.2.0 → 0.3.0 functional
    • New tool “get_started” functional
  • 17 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 708 → 1747 ▼ functional
    • Tool coverage: 80% → 91% ▲ functional
    • Server version: 0.1.0 → 0.2.0 functional
    • New tool “sandbox_account” functional
    • New tool “sandbox_find_markets” functional
    • New tool “sandbox_list_orders” functional
    • New tool “sandbox_place_order” functional
    • New tool “sandbox_preview_order” functional
  • 16 Nov 26 +1

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

  • 14 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • “find_matches” reworded the description of “q” cosmetic
  • 13 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
    • “find_matches” reworded the description of “from” cosmetic
  • 12 Nov 26 70

    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://uselayer.sh/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.uselayer.sh CN=YR1,O=Let's Encrypt,C=US 12 Oct 2026 10 Jan 2027 RSA 2048 SHA256-RSA 6cd4bf3e670a9b553658b78e6f4d8cf6f30
SANs: *.uselayer.sh, uselayer.sh
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of uselayer.sh. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
sh. DS published 34349 8 Verified
uselayer.sh. 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
Header Value
strict-transport-security max-age=63072000

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://uselayer.sh/mcp Verified 200
http (plaintext) http://uselayer.sh/mcp HTTPS enforced 308 https://uselayer.sh/mcp
MCP tools · 2 exposed · ~137 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
get_started ~69

How to work with Layer over its REST API and websocket: the base URL, how to send your key, the exact calls to find markets, place, watch and cancel paper orders, the live stream, and the docs. Use those calls directly from here on: they're faster than tools and can stream.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

sandbox_account ~68

Your paper-trading account: simulated cash, each position valued at the best bid now, and profit or loss since the start ($10,000). Positions whose market has settled are paid out first. Use it to check your key and account are set up; trade over the API (get_started).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Layer MCP server?

Layer is a hosted endpoint at https://uselayer.sh/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 · uselayer.sh

# add to Claude Code
claude mcp add --transport http sh-uselayer-layer 'https://uselayer.sh/mcp'
Common questions

What is the Layer MCP server?

Layer is an MCP server listed in the public MCP registry as sh.uselayer/layer. Find the same prediction market on Kalshi and Polymarket, with live prices and profit after fees. This page covers its hosted endpoint (https://uselayer.sh/mcp).

Is the Layer MCP server safe to use?

Layer scores 72 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 Layer MCP server expose?

Layer exposes 2 tools: get_started, sandbox_account. Their descriptions and schemas cost roughly 137 tokens of context every time the server is loaded.

Does the Layer MCP server require authentication?

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

Is the Layer MCP server still maintained?

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

VerifyMCP ran 13 checks on Layer, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.