INDICIA DESK MCP server
com.indiciadesk/deskindiciadesk.comstreamable-httpv0.1.0Scanned
BTC/ETH options research: tested hypotheses, max pain track record, gamma regime, trade journal.
5 tools: 4 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
4 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 INDICIA DESK MCP server can do
The INDICIA DESK MCP server is published by indiciadesk.com, a domain the MCP Registry verified. It has 5 tools. It can create or change data (4 tools: market_state, expiry_record, decision_journal and about_indicia), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
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, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 9, 2026, version 0.1.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.
5 tools
Changes things 4Claude Code: ask
about_indiciaWhat INDICIA DESK is, what each tool returns, data freshness, what is deliberately not available here, plans, and the services (morning letter, idea check, channel audit, Whale Wat…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.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it What INDICIA DESK is, what each tool returns, data freshness, what is deliberately not available here, plans, and the services (morning letter, idea check, channel audit, Whale Watch).
Annotations the server declares
- title: About INDICIA DESK and this server
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
decision_journalINDICIA DESK's decision journal: options strategies tracked at real Deribit bid/ask prices (paper account), with every closed trade, wins and losses.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.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it INDICIA DESK's decision journal: options strategies tracked at real Deribit bid/ask prices (paper account), with every closed trade, wins and losses. Returns per-strategy trade counts, win rate and average result, and the latest closed trades. Use to show how rule-based options strategies actually performed. Live entry signals and exact structures are not available here.
Annotations the server declares
- title: Proving Ground: closed trades, wins and losses
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
expiry_recordHow often BTC/ETH Deribit options settled at max pain, inside the market-maker breakeven corridor, and whether OI walls held, over hundreds of expiries — plus the most recent settl…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.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it How often BTC/ETH Deribit options settled at max pain, inside the market-maker breakeven corridor, and whether OI walls held, over hundreds of expiries — plus the most recent settled expiries (Deribit and Bybit max pain side by side) and the current max pain of upcoming expiries. Use for "will price pin to max pain on Friday?" type questions: it answers with the historical hit rate, not a prediction.
Annotations the server declares
- title: Max pain and corridor track record per expiry
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
market_stateCurrent dealer gamma regime (positive = hedging dampens moves, negative = amplifies), zero-gamma flip, call/put walls, DVOL and its 1-year rank, implied-minus-realized volatility, …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.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Current dealer gamma regime (positive = hedging dampens moves, negative = amplifies), zero-gamma flip, call/put walls, DVOL and its 1-year rank, implied-minus-realized volatility, IV term structure and the INDICIA Fear & Greed index, with how long the regime has lasted in our daily archive. Descriptive context, not a direction call. Data refreshes about every 2 hours; the result carries as_of.
Annotations the server declares
- title: BTC/ETH options market state with history context
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 1Show 1 read-only tool
hypothesis_ledgerSearch INDICIA DESK's public registry of BTC/ETH market beliefs tested on its own data, including the rejected ones.No findings
Why it is in this group
- The description's first verb is "search": a word for reading.
Description, as the server wrote it Search INDICIA DESK's public registry of BTC/ETH market beliefs tested on its own data, including the rejected ones. Use when someone asks whether a popular crypto trading belief holds, e.g. "does max pain attract price?", "do whales lead the move?", "is selling volatility after a fear spike profitable?". Returns verdict status and a plain-language teaser; exact thresholds are not public.
Annotations the server declares
- title: Tested market hypotheses (confirmed and rejected)
- 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.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- 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:22 UTC, unchanged since Oct 24, 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
- 4
- 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 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.indiciadesk.com/mcp: tools/list returned 5 tools to an anonymous client, including market_state (write), expiry_record (write), decision_journal (write), about_indicia (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.
Tools1 changed.~1 changedView diff
- Changed:about_indiciaChanges thingsdescription
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http desk https://mcp.indiciadesk.com/mcpclaude mcp add --transport http desk https://mcp.indiciadesk.com/mcpRun 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__desk__hypothesis_ledger"
],
"ask": [
"mcp__desk__market_state",
"mcp__desk__expiry_record",
"mcp__desk__decision_journal",
"mcp__desk__about_indicia"
],
"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 desk. Review it before you use it.
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.indiciadesk/desk/verify?hash=5b5a46fe1e2926d1bb638e559613aed85c68f91adab7a8349f720d4840fc08aa" | jq -e '.changed == false'Pinned hash 5b5a46fe1e29, from Nov 9, 2026, 00:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.indiciadesk/desk/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.indiciadesk/desk)Source: MCP Registry. Synced Oct 24, 2026, 07:17 UTC.
INDICIA DESK MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the INDICIA DESK MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 4 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 INDICIA DESK MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the INDICIA DESK 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 INDICIA DESK MCP server have?
- 5 tools: 4 write, 1 read. market_state, expiry_record, decision_journal, about_indicia and hypothesis_ledger.
Does the INDICIA DESK MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the INDICIA DESK MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the INDICIA DESK MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.