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.

Syndicate

REMOTE · GATEWAY.SYNDICATE.TRADE

Read-only market data: tokens, stocks, Hyperliquid perps, Polymarket, and public trader books.

+3 this week 71 Trust /100

Last scanned (12 hours ago)

Scores higher than 56% 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 Security74
  • 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
  • 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
Schema Quality & AI Usability41
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2537 tokens (~158/item across 16 items; 15 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 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 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 17 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
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

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

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 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 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 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

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

  • 14 Nov 26 +1

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

  • 12 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
  • 10 Nov 26 +1

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

  • 9 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
    • “get_syndicate” reworded the description of “limit” cosmetic
    • “get_trader_portfolio” reworded the description of “limit” cosmetic
  • 8 Nov 26 65

    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://gateway.syndicate.trade/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=gateway.syndicate.trade CN=Amazon RSA 2048 M04,O=Amazon,C=US 22 Aug 2026 7 Mar 2027 RSA 2048 SHA256-RSA 70729e52b26352faf961dde8c265fad
SANs: gateway.syndicate.trade
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of gateway.syndicate.trade. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
trade. DS published 64969 8 Verified
syndicate.trade. 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://gateway.syndicate.trade/mcp Verified 200
http (plaintext) http://gateway.syndicate.trade/mcp HTTPS enforced 301 https://gateway.syndicate.trade/mcp
MCP tools · 15 exposed · ~2,157 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
discover ~448

Browse or filter the Discover index across spot tokens, tokenised stocks, perps and prediction markets; each row carries its venues, chains, outcomes and 24h stats. Filter by kind, venue, chain, class, tag or feed; sort by volume_24h, change_24h, market_cap, trending, ends_soon and more; page with cursor. For movers use kind=perp: spot change_24h is noise from illiquid pools unless filtered by liquidity. Prediction rows carry every outcome, so keep limit small (<=5).

NameTypeReqDescription
chainstring|null–Comma-separated chains, e.g. ethereum, solana, base.
classstring|null–Comma-separated asset classes: crypto, tradfi, prediction.
cursorstring|null–`next_cursor` from the previous page, same filters and sort.
feedstring|null–Only one screener feed's members: trending, new or crypto.
kindstring|null–Comma-separated: spot, tokenised_stock, perp, prediction.
limitinteger|null–1-100 (default 25).
max_outcomesinteger|null–Prediction rows: top N outcomes by price, 1-50. Priceless drop first.
min_liquidity_usdnumber|null–USD floor, >= 0: pool liquidity (spot, stock, prediction) or open interest (perp). Rows without the figure are dropped.
min_volume_24h_usdnumber|null–USD floor on 24h volume, >= 0. Rows without one are dropped.
orderstring|null–asc or desc.
qstring|null–Text query; omit to browse.
sortstring|null–volume_24h, change_24h, market_cap, new, trending, relevance, ends_soon or name.
tagstring|null–Comma-separated Polymarket tag slugs (see discover_categories), e.g. politics.
venuestring|null–Comma-separated venues, e.g. hyperliquid, polymarket.

No output schema declared.

No examples provided.

discover_categories ~30

List the Discover categories (prediction-market tags and their slugs) usable as discover's `tag` filter.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_perp_candles ~234

Hyperliquid perp candles for one coin as parallel arrays t/o/h/l/c/v. `coin` is the bare Hyperliquid coin (BTC, not BTC-PERP; HIP-3 coins are dex-prefixed, e.g. xyz:NVDA). `interval` sets the bar size (default 1h). `from`/`to` are unix MILLISECONDS (default the last 7 days); returned `t` is unix seconds.

NameTypeReqDescription
coinstringyesBare Hyperliquid coin (BTC, kPEPE) or Discover's perp id (BTC-PERP); HIP-3 coins are dex-prefixed, e.g. xyz:NVDA.
frominteger|null–Window start, unix MILLISECONDS, not seconds (default 7 days before `to`).
intervalstring|null–e.g. 1m, 15m, 1h, 4h, 1d. Default 1h.
tointeger|null–Window end, unix MILLISECONDS, not seconds (default now).

No output schema declared.

No examples provided.

get_prediction_event ~183

One Polymarket event (all its outcomes) by event slug, event id, market slug or condition_id: each outcome's price, bid/ask and price history, plus live game state for sports. Prices are YES probabilities 0..1. `interval` is the history's lookback window (1h, 6h, 1d, 1w, 1m, max), not a bar size; keep it short (default 1d) on many-outcome events.

NameTypeReqDescription
include_no_historyboolean–Add binary outcomes' NO-side series (default false). It is always `1 - p` of `history`, so it only doubles the payload.
interval––Price-history window (default 1d).
keystringyesEvent slug, Gamma event id, market slug or condition id.

No output schema declared.

No examples provided.

get_syndicate ~169

One syndicate by id: its public page (name, pitch, operators, terms, members) under `syndicate` and its book (holdings, closed positions, balance curve) under `book`.

NameTypeReqDescription
idstringyesSyndicate id (UUID), from list_syndicates.
includestring|null–Same `include` as a trader book: comma-separated section names, omitted = all. Passed only on the book request.
include_dustboolean|null–Include dust-sized holdings (default false).
limitinteger|null–Caps holdings and closed positions each, 1-200 (default all); above 200 is read as 200.
sort––Order of the book's holdings and closed positions (default newest).

No output schema declared.

No examples provided.

get_token ~97

One token by chain and contract address: identity, mark price, liquidity and listings under `token`; per-window price change and 24h trading activity (volume, buys, sells, traders) under `stats`.

NameTypeReqDescription
addressstringyesToken contract address (0x… on EVM, base58 mint on Solana).
chainstringyesChain slug, e.g. ethereum, base, solana, robinhood.

No output schema declared.

No examples provided.

get_token_candles ~195

OHLCV candles for one token by chain slug and contract address. `tf` sets the resolution; `from`/`to` are unix SECONDS. Always pass tf and from: with no window the answer runs to over a thousand bars. Use a coarse tf (60, 1D) for long windows.

NameTypeReqDescription
addressstringyesToken contract address (0x… on EVM, base58 mint on Solana).
chainstringyesChain slug, e.g. ethereum, base, solana, robinhood.
frominteger|null–Window start, unix seconds.
tfstring|null–Resolution: 1S, 5S, 1, 5, 15, 60, 240 (minutes) or 1D. Default 1.
tointeger|null–Window end, unix seconds (default now).

No output schema declared.

No examples provided.

get_trader ~54

A trader's public profile by handle: user id, bio, avatar, follower and following counts, join date. Private and followers-only profiles answer not found.

NameTypeReqDescription
handlestringyesTrader handle, without the @.

No output schema declared.

No examples provided.

get_trader_activity ~94

A public trader's ledger activity by handle, newest first: swaps, deposits, withdrawals, transfers and fees. Narrow with `filter`, page with `cursor`.

NameTypeReqDescription
cursorstring|null–`next_cursor` from the previous page.
filter––Default all.
handlestringyesTrader handle, without the @.
limitinteger|null–1-200 (default 50).

No output schema declared.

No examples provided.

get_trader_portfolio ~184

A public trader's book by handle: open holdings and perps with value and PnL, closed positions, cash, realized PnL and the balance curve. Dust is hidden unless include_dust is true.

NameTypeReqDescription
handlestringyesTrader handle, without the @.
includestring|null–Comma-separated sections (`holdings`, `closed`, `activity`, `realized_history`, `balance_history`, `perps`, `cash_rows`). Omitted returns every section. An unknown name is a 400.
include_dustboolean|null–Include dust-sized holdings (default false).
limitinteger|null–Caps holdings and closed positions each, 1-200 (default 50); above 200 is read as 200.
sort––Order of holdings and closed positions (default newest).

No output schema declared.

No examples provided.

leaderboard ~58

The points leaderboard's top rows: rank, handle, score and referrals. Points, not trading performance; use list_traders for PnL.

NameTypeReqDescription
headinteger|null–Rows from the top, 1-100 (default 10).

No output schema declared.

No examples provided.

list_perp_markets ~77

Raw Hyperliquid metaAndAssetCtxs (large): a universe array and a per-asset context array, parallel and joined by index, delisted coins included. Funding is the hourly rate as a fraction; open interest is in coin units. Use only for raw funding; screen perps with discover kind=perp.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_syndicates ~77

Browse public syndicates (shared trading books run by operators), newest first: id, name, pitch, emblem, status, operators and member count. Page with `cursor`.

NameTypeReqDescription
cursorstring|null–`next_cursor` from the previous page.
limitinteger|null–1-50 (default 20).

No output schema declared.

No examples provided.

list_traders ~143

The trading ranking: public traders by realized PnL, return or hit rate over a rolling window, with open value and balance per row. Few traders qualify; raise min_sales (default 5) to drop lucky one-sale records, and always show each row's `sales` beside its rank.

NameTypeReqDescription
limitinteger|null–1-50 (default 20).
min_salesinteger|null–Priced sales in the window needed to be ranked, 1-100 (default 5).
sort––realized PnL (default), return, or hit_rate.
window––Rolling window (default 30d).

No output schema declared.

No examples provided.

search_assets ~114

Search everything by text: tokens, perps, prediction markets and traders matching a ticker, name, address or handle. Start here to turn a name into the chain+address, coin or condition_id the other tools take. `limit` caps token hits only. Names are often ambiguous (many TRUMPs): pick by kind and liquidity.

NameTypeReqDescription
limitinteger|null–Max token hits, 1-50 (default 12).
qstringyesTicker, name, contract address or trader handle.

No output schema declared.

No examples provided.

Install

How do I install the Syndicate MCP server?

Syndicate is a hosted endpoint at https://gateway.syndicate.trade/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 · gateway.syndicate.trade

# add to Claude Code
claude mcp add --transport http trade-syndicate-markets 'https://gateway.syndicate.trade/mcp'
Common questions

What is the Syndicate MCP server?

Syndicate is an MCP server listed in the public MCP registry as trade.syndicate/markets. Read-only market data: tokens, stocks, Hyperliquid perps, Polymarket, and public trader books. This page covers its hosted endpoint (https://gateway.syndicate.trade/mcp).

Is the Syndicate MCP server safe to use?

Syndicate scores 71 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 Syndicate MCP server expose?

Syndicate exposes 15 tools: discover, discover_categories, get_perp_candles, get_prediction_event, get_syndicate, and 10 more. Their descriptions and schemas cost roughly 2,157 tokens of context every time the server is loaded.

Does the Syndicate MCP server require authentication?

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

Is the Syndicate MCP server still maintained?

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

VerifyMCP ran 14 checks on Syndicate, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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.