orderly-mcp server
io.github.OrderlyNetwork/orderly-mcpOrderlyNetworkstreamable-httpv1.5.10Scanned
MCP Server for Orderly Network - Documentation and SDK patterns
9 tools: 9 only read.
- Reads private data · 2
- Reads text others write · 5
- Can send data out · 4
- 8 findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- 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 orderly-mcp server can do
The orderly-mcp server is published by the GitHub account OrderlyNetwork. It has 9 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
2 tools read private data (search_orderly_docs and get_strategy_vault_api_info); 5 tools bring in text other people can write (get_api_info, get_indexer_api_info, get_orderly_one_api_info and 2 more); 4 tools can send data out of your system (get_api_info, get_indexer_api_info, get_orderly_one_api_info and 1 more). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 8 findings (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 10, 2026, version 1.5.10.
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.
9 tools
Only reads 9Show 9 read-only tools
explain_workflowGet a curated, step-by-step guide for a common Orderly development task such as wallet connection, deposits, SDK setup, or placing orders.1 finding
Why it is in this group
- The name "explain_workflow" says "explain": a word for reading.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...p from bundled data — no network calls, credentials, rate limits, or side effects. Use for..."
Description, as the server wrote it Get a curated, step-by-step guide for a common Orderly development task such as wallet connection, deposits, SDK setup, or placing orders. Returns exactly one best-matching workflow as Markdown with prerequisites, numbered steps, TypeScript examples, common issues, and related workflows; pass the task in natural language or a partial name, and a miss lists available workflows. Read-only lookup from bundled data — no network calls, credentials, rate limits, or side effects. Use for end-to-end tasks, not one-off lookups: get_component_guide for a known UI component, search_orderly_docs (scope 'sdk') for symbols, get_api_info for core endpoints, and the matching named tool for Indexer, Public Info, Orderly One, or Strategy Vault data.
Annotations the server declares
- title: Explain Orderly Workflow
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_api_infoGet reference documentation for the core Orderly trading API: REST endpoints, WebSocket streams, or authentication.Reads text others writeCan send data out1 finding
Why it is in this group
- The name "get_api_info" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "get" and "web": it reads web pages, which anyone can write.
- untrusted-inputThe input takes a URL (input.endpoint), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.endpoint): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...t does not call the API and requires no credentials, rate limits, or side effects. Use `typ..."
Description, as the server wrote it Get reference documentation for the core Orderly trading API: REST endpoints, WebSocket streams, or authentication. For `rest` or `websocket`, omitting `endpoint` lists every endpoint or stream with base URLs and auth requirements; supplying `endpoint` fuzzy-matches one item and returns its method/path or topic, auth, rate limits, parameters, message formats, and a TypeScript example. `type: 'auth'` returns the signing flow and ignores `endpoint`. Read-only bundled docs — it does not call the API and requires no credentials, rate limits, or side effects. Use `type` alone to discover valid names, then `endpoint` for detail; for historical analytics use get_indexer_api_info, for zero-auth public data use get_public_info_api_info, for DEX management use get_orderly_one_api_info, and for vault data use get_strategy_vault_api_info.
Annotations the server declares
- title: Get Orderly API Info
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_component_guideGet a curated build guide for a React UI component from the Orderly SDK, such as order-entry, orderbook, positions, or wallet-connector.1 finding
Why it is in this group
- The name "get_component_guide" says "get": a word for reading.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...nly static guidance — no network calls, credentials, rate limits, or side effects. Use for..."
Description, as the server wrote it Get a curated build guide for a React UI component from the Orderly SDK, such as order-entry, orderbook, positions, or wallet-connector. Returns Markdown with required packages, key hooks, a complete TSX example, tips, styling notes, common mistakes, and related components; `complexity` selects the example depth — 'minimal' for a scaffold, 'advanced' for production wiring — and falls back to 'standard'. Guides include full code and can be long; a miss lists available guides and points to search_orderly_docs. Read-only static guidance — no network calls, credentials, rate limits, or side effects. Use for a known UI component; for SDK hook/type signatures use search_orderly_docs (scope 'sdk'), for end-to-end steps use explain_workflow, and for backend endpoints use get_api_info or the matching domain API tool.
Annotations the server declares
- title: Get Orderly Component Guide
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_contract_addressesGet the deployed smart contract addresses for Orderly on a specific chain and network.1 finding
Why it is in this group
- The name "get_contract_addresses" says "get": a word for reading.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...p from bundled data — no network calls, credentials, or side effects. Use for deployment an..."
Description, as the server wrote it Get the deployed smart contract addresses for Orderly on a specific chain and network. `chain` is required; `contractType` filters to one contract (e.g. vault, usdc, usdt) or 'all'; `network` selects mainnet (default) or testnet. 'all' lists every contract with an address on the selected network; a specific type also returns its description and the address on the other network when available. Unknown chains or contract types return the valid options. Read-only lookup from bundled data — no network calls, credentials, or side effects. Use for deployment and wiring addresses only; for API details use get_api_info or the matching named API tool, for SDK symbols use search_orderly_docs, and for integration steps use explain_workflow.
Annotations the server declares
- title: Get Orderly Contract Addresses
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_indexer_api_infoGet reference documentation for the Orderly Indexer API, a read-only source of historical and aggregated trading data: volume and fee metrics, account events, trades, and rankings.Reads text others writeCan send data out1 finding
Why it is in this group
- The name "get_indexer_api_info" says "get": a word for reading.
What it can reach
- untrusted-inputThe input takes a URL (input.endpoint), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.endpoint): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...Bundled docs lookup only — no API call, credentials, or rate limits. Use for analytics, das..."
Description, as the server wrote it Get reference documentation for the Orderly Indexer API, a read-only source of historical and aggregated trading data: volume and fee metrics, account events, trades, and rankings. Omit both parameters for an overview with base URLs, categories, common errors, and usage tips; pass `category` to discover all endpoints in an area, or `endpoint` to fuzzy-match one endpoint and return its parameters, request/response schemas, and TypeScript example (category takes precedence if both are supplied). Bundled docs lookup only — no API call, credentials, or rate limits. Use for analytics, dashboards, account history, and leaderboards; for live trading operations use get_api_info, and for zero-auth market data use get_public_info_api_info.
Annotations the server declares
- title: Get Indexer API Info
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_orderly_one_api_infoGet reference documentation for the Orderly One API used to create, graduate, and manage a DEX, covering auth, DEX, graduation, theme, stats, leaderboard, and admin endpoints.Reads text others writeCan send data out1 finding
Why it is in this group
- The name "get_orderly_one_api_info" says "get": a word for reading.
What it can reach
- untrusted-inputThe input takes a URL (input.endpoint), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.endpoint): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...cs — it never calls the API or requires credentials. Use for Orderly One/DEX-builder tasks;..."
Description, as the server wrote it Get reference documentation for the Orderly One API used to create, graduate, and manage a DEX, covering auth, DEX, graduation, theme, stats, leaderboard, and admin endpoints. Omit both parameters for an overview; pass `category` to discover all endpoints in an area, or `endpoint` to fuzzy-match one endpoint and return its method, parameters, and examples (category takes precedence if both are supplied). Responses flag agent-blocked or conditional operations such as DEX creation, deployment, and deletion. Read-only bundled docs — it never calls the API or requires credentials. Use for Orderly One/DEX-builder tasks; for core trading use get_api_info, for vault data use get_strategy_vault_api_info, and for analytics use get_indexer_api_info or get_public_info_api_info.
Annotations the server declares
- title: Get Orderly One API Info
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_public_info_api_infoGet reference documentation for the Orderly Public Info API — a zero-auth single endpoint (POST /v1/public/query) for market, account, and platform data selected by a `type` field.Reads text others writeNo findings
Why it is in this group
- The name "get_public_info_api_info" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "get" and "post": it reads posts, which other people can write.
Description, as the server wrote it Get reference documentation for the Orderly Public Info API — a zero-auth single endpoint (POST /v1/public/query) for market, account, and platform data selected by a `type` field. Covers 24 query types (marketSummary, accountState, orderbook, candles, topAddresses, whaleContext, etc.); `queryType` accepts exact, partial, or fuzzy names and returns params, response fields, example, weight, and freshness; `category` lists a group (queryType wins if both are supplied); omit both for the overview and rate-limit rules. Read-only bundled docs — it does not call the endpoint. Use instead of get_api_info for zero-auth public data; use get_api_info for authenticated trading, get_indexer_api_info for historical analytics, and get_strategy_vault_api_info for vault data.
Annotations the server declares
- title: Get Public Info API Info
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_strategy_vault_api_infoGet reference documentation for the Orderly Strategy Vault REST API covering vault performance, strategy providers, fund management, liquidity providers, and user stats.Reads private dataReads text others writeCan send data out1 finding
Why it is in this group
- The name "get_strategy_vault_api_info" says "get": a word for reading.
What it can reach
- private-dataThe name "get_strategy_vault_api_info" says "get" and "vault": it reads secrets.
- private-dataThe description's first sentence says "get" and "vault": it reads secrets.
- untrusted-inputThe input takes a URL (input.endpoint), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.endpoint): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...t does not call the API and requires no credentials or rate limits. Use for vault/yield int..."
Description, as the server wrote it Get reference documentation for the Orderly Strategy Vault REST API covering vault performance, strategy providers, fund management, liquidity providers, and user stats. Omit both parameters for an overview with base URL and categories; pass `category` to discover all endpoints in an area, or `endpoint` to fuzzy-match one endpoint and return its full detail (category wins if both are supplied). Read-only bundled docs — it does not call the API and requires no credentials or rate limits. Use for vault/yield integrations; for core trading use get_api_info, for historical analytics use get_indexer_api_info, and for zero-auth market data use get_public_info_api_info.
Annotations the server declares
- title: Get Strategy Vault API Info
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_orderly_docsSearch bundled Orderly docs and SDK symbols by topic or question.Reads private data1 finding
Why it is in this group
- The name "search_orderly_docs" says "search": a word for reading.
What it can reach
- private-dataThe name "search_orderly_docs" says "search" and "doc": it reads documents.
- private-dataThe description's first sentence says "search" and "doc": it reads documents.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...d-only local search — no network calls, credentials, rate limits, or side effects. Use for..."
Description, as the server wrote it Search bundled Orderly docs and SDK symbols by topic or question. Returns up to `limit` ranked Markdown results with relevance scores: `scope: 'sdk'` returns hooks/components/types/functions with signatures, props, and source paths; `'docs'` returns prose; `'auto'` (default) picks the corpus from the query. Use `'sdk'` for exact symbol signatures and `detail: 'full'` only when the summary is insufficient, since it returns much longer text. Read-only local search — no network calls, credentials, rate limits, or side effects. Use for open-ended discovery when the component, workflow, or endpoint is unknown; for a known component use get_component_guide, for a task walkthrough use explain_workflow, for an endpoint use get_api_info, get_indexer_api_info, get_public_info_api_info, or get_strategy_vault_api_info, and for addresses use get_contract_addresses.
Annotations the server declares
- title: Search Orderly Documentation
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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.
40 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 private-data tools breaks every one.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write5
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out4
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__orderly__get_strategy_vault_api_info",
"mcp__orderly__search_orderly_docs"
]
}
}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 20, 2026, 18:24 UTC, unchanged since Oct 29, 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
- 0
- 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
Findings
Matches of fixed checks, with the text they matched.
The description mentions "credentials".
What this check looks forMatched text
description: "...d-only local search — no network calls, credentials, rate limits, or side effects. Use for..."
The description mentions "credentials".
What this check looks forMatched text
description: "...p from bundled data — no network calls, credentials, or side effects. Use for deployment an..."
- Infoexplain_workflow
The description mentions "credentials".
What this check looks forMatched text
description: "...p from bundled data — no network calls, credentials, rate limits, or side effects. Use for..."
- Infoget_api_info
The description mentions "credentials".
What this check looks forMatched text
description: "...t does not call the API and requires no credentials, rate limits, or side effects. Use `typ..."
The description mentions "credentials".
What this check looks forMatched text
description: "...Bundled docs lookup only — no API call, credentials, or rate limits. Use for analytics, das..."
The description mentions "credentials".
What this check looks forMatched text
description: "...nly static guidance — no network calls, credentials, rate limits, or side effects. Use for..."
Show 2 more findingsShow fewer
The description mentions "credentials".
What this check looks forMatched text
description: "...cs — it never calls the API or requires credentials. Use for Orderly One/DEX-builder tasks;..."
The description mentions "credentials".
What this check looks forMatched text
description: "...t does not call the API and requires no credentials or rate limits. Use for vault/yield int..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools9 changed.~9 changedView diff
- Changed:explain_workflowOnly readsdescriptionannotations
- Changed:get_api_infoOnly readsdescriptionannotations
- Changed:get_component_guideOnly readsdescriptionannotations
- Changed:get_contract_addressesOnly readsdescriptionannotations
- Changed:get_indexer_api_infoOnly readsdescriptionannotations
- Changed:get_orderly_one_api_infoOnly readsdescriptionannotations
- Changed:get_public_info_api_infoOnly readsdescriptionannotations
- Changed:get_strategy_vault_api_infoOnly readsdescriptionannotations
- Changed:search_orderly_docsOnly readsdescriptionannotations
Install
Pinned to version 1.5.10. Values in angle brackets are yours to fill in.
claude mcp add --transport http orderly https://mcp.orderly.network/claude mcp add --transport http orderly https://mcp.orderly.network/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__orderly__search_orderly_docs",
"mcp__orderly__get_contract_addresses",
"mcp__orderly__explain_workflow",
"mcp__orderly__get_component_guide",
"mcp__orderly__get_public_info_api_info"
],
"ask": [
"mcp__orderly__get_api_info",
"mcp__orderly__get_indexer_api_info",
"mcp__orderly__get_orderly_one_api_info",
"mcp__orderly__get_strategy_vault_api_info"
],
"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 orderly. Review it before you use it.
Capability tags behind 6 rules
- mcp__orderly__search_orderly_docs private-data
- mcp__orderly__get_api_info untrusted-input, outbound
- mcp__orderly__get_indexer_api_info untrusted-input, outbound
- mcp__orderly__get_orderly_one_api_info untrusted-input, outbound
- mcp__orderly__get_strategy_vault_api_info private-data, untrusted-input, outbound
- mcp__orderly__get_public_info_api_info untrusted-input
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/io.github.OrderlyNetwork/orderly-mcp/verify?hash=1558fb55cc69d009fb4007a39ff2c46b5a10cf4f78ff63652855db63bf0fb4f3" | jq -e '.changed == false'Pinned hash 1558fb55cc69, from Nov 10, 2026, 14:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.OrderlyNetwork/orderly-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.OrderlyNetwork/orderly-mcp)Source: MCP Registry · repository. Synced Nov 10, 2026, 14:17 UTC.
orderly-mcp server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the orderly-mcp server safe?
- No scan can promise that. What its definitions show: 9 tools, all of which only read, and 8 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the orderly-mcp server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the orderly-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 orderly-mcp server have?
- 9 tools: 9 read. search_orderly_docs, get_contract_addresses, explain_workflow, get_api_info, get_indexer_api_info, get_component_guide, get_orderly_one_api_info, get_strategy_vault_api_info and 1 more.
Does the orderly-mcp server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the orderly-mcp server send data to outside services?
- 4 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): get_api_info, get_indexer_api_info, get_orderly_one_api_info and get_strategy_vault_api_info.
Has the orderly-mcp server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 5, 2026. Every change is on this page and in its Atom feed.