Skip to content

EchoLedger MCP server

io.github.icmoore/echoledger-mcpicmoorestreamable-httpv0.2.3Scanned

Live LP analytics — Uniswap V2/V3, Balancer, Curve stableswap: PnL, health, slippage, depeg risk.

11 tools: 6 change things and 5 only read.

Tools: 0 delete, 0 irreversible, 6 write, 5 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

6 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the EchoLedger MCP server can do

The EchoLedger MCP server is published by the GitHub account icmoore. It has 11 tools. It can create or change data (6 tools: SimulatePriceMove, SimulateBalancerMove, SimulateStableswapMove, DetectRugSignals and 2 more), but cannot delete data. 5 tools only read.

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.

Last scanned Oct 21, 2026, version 0.2.3.

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.

11 tools

Changes things 6Claude Code: ask
  • AssessDepegRiskQuantify a 2-asset Curve-style Stableswap LP position's exposure to a stablecoin depeg.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
    Quantify a 2-asset Curve-style Stableswap LP position's exposure to a stablecoin depeg. Computes IL at multiple depeg levels (default 2%, 5%, 10%, 20%, 50%) via the closed-form stableswap-invariant expansion, with an optional V2 constant-product benchmark at each level. Some depeg levels are physically unreachable at high A — unreachable scenarios return null on il_pct, lp_value_at_depeg, and hold_value_at_depeg; the V2 benchmark stays populated.
  • CalculateSlippageCalculate slippage and price-impact decomposition for a proposed swap on a Uniswap V2 or V3 pool.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
    Calculate slippage and price-impact decomposition for a proposed swap on a Uniswap V2 or V3 pool. Returns spot vs execution price, slippage percentage, slippage cost in output-token units, and price impact. Also returns the maximum trade size that stays within 1% slippage for V2 pools; V3 returns null for that field because tick-crossing math has not yet been inverted.
  • DetectRugSignalsDetect rug-pull signals on a Uniswap V2 or V3 pool via three threshold checks: suspiciously low TVL, top-LP concentration above a limit, and inactive-pool-with-liquidity.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
    Detect rug-pull signals on a Uniswap V2 or V3 pool via three threshold checks: suspiciously low TVL, top-LP concentration above a limit, and inactive-pool-with-liquidity. Composes over CheckPoolHealth and returns per-signal booleans plus a count-based risk level (low/medium/high/critical). The inactive-with-liquidity signal is V2-only; V3 pools report False for it with a note in details.
  • SimulateBalancerMoveProject a 2-asset Balancer weighted-pool LP position's value at a hypothetical price change from the CURRENT pool state.No findings

    Why it is in this group

    • The name "SimulateBalancerMove" says "move": a word for a change.
    Description, as the server wrote it
    Project a 2-asset Balancer weighted-pool LP position's value at a hypothetical price change from the CURRENT pool state. The shock is applied to the base-token price in opp units; IL depends on both the shock magnitude and the pool's weights. Returns new value in opp-numeraire, IL at the simulated price, and percentage change.
  • SimulatePriceMoveProject a Uniswap V2 or V3 LP position's value at a hypothetical price change from the CURRENT pool state (not from entry).No findings

    Why it is in this group

    • The name "SimulatePriceMove" says "move": a word for a change.
    Description, as the server wrote it
    Project a Uniswap V2 or V3 LP position's value at a hypothetical price change from the CURRENT pool state (not from entry). A price_change_pct of -0.30 asks 'what if price drops 30% from here'. Returns new value, IL at the simulated price, and percentage change in position value. Fee projection is not modeled (always null).
  • SimulateStableswapMoveProject a 2-asset Curve-style Stableswap LP position's value at a hypothetical depeg from the CURRENT pool state.No findings

    Why it is in this group

    • The name "SimulateStableswapMove" says "move": a word for a change.
    Description, as the server wrote it
    Project a 2-asset Curve-style Stableswap LP position's value at a hypothetical depeg from the CURRENT pool state. The shock multiplies the pool's current alpha by (1 + price_change_pct); at high A, large shocks may be physically unreachable and in that case new_value, il_at_new_price, and value_change_pct are returned as null. Values are in peg-numeraire.
Only reads 5Show 5 read-only tools
  • AnalyzeBalancerLPAnalyze a 2-asset Balancer weighted-pool LP position's PnL.No findings

    Why it is in this group

    • The name "AnalyzeBalancerLP" says "analyze": a word for reading.
    Description, as the server wrote it
    Analyze a 2-asset Balancer weighted-pool LP position's PnL. Decomposes impermanent loss using the weighted-pool formula where the base token's weight affects IL magnitude. Values are denominated in opp-token units per BalancerImpLoss's convention; fee income is not attributed in v1 because Balancer pools only expose vault-level fees with no per-LP attribution.
  • AnalyzePositionAnalyze why a Uniswap V2 or V3 LP position is gaining or losing money.No findings

    Why it is in this group

    • The name "AnalyzePosition" says "analyze": a word for reading.
    Description, as the server wrote it
    Analyze why a Uniswap V2 or V3 LP position is gaining or losing money. Decomposes PnL into impermanent loss, accumulated fees, and net result, with optional real APR if a holding period is supplied. Returns current value, hold value, IL percentage, fee income, net PnL, real APR, and a diagnosis label.
  • AnalyzeStableswapLPAnalyze a 2-asset Curve-style Stableswap LP position's PnL using the amplified-invariant IL formula where small depegs can produce surprisingly large IL at high A.No findings

    Why it is in this group

    • The name "AnalyzeStableswapLP" says "analyze": a word for reading.
    Description, as the server wrote it
    Analyze a 2-asset Curve-style Stableswap LP position's PnL using the amplified-invariant IL formula where small depegs can produce surprisingly large IL at high A. Values are in peg-numeraire (tokens valued 1:1); fee income is not attributed in v1 (pool-global only); positions whose implied alpha is in the unreachable regime return None on il_percentage, net_pnl, and real_apr.
  • BuildStateTwinRead a pool's on-chain state once and return it as a serialized State Twin (JSON): the protocol-specific snapshot plus a content_hash, in the wire form a client rehydrates locally.No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    Read a pool's on-chain state once and return it as a serialized State Twin (JSON): the protocol-specific snapshot plus a content_hash, in the wire form a client rehydrates locally. Use this to pull a single managed-RPC twin, then run any number of counterfactuals (price moves, IL, slippage) client-side, off this server. Covers Uniswap V2/V3, Balancer 2-asset weighted, and Curve 2-asset plain stableswap pools. The endpoint stores and logs nothing — your rpc_url is never persisted.
  • CheckPoolHealthSnapshot pool-level health metrics for a Uniswap V2 or V3 pool: TVL in token0 numeraire, reserves, accumulated fees, LP concentration, and swap activity.No findings

    Why it is in this group

    • The description's first verb is "snapshot": a word for reading.
    Description, as the server wrote it
    Snapshot pool-level health metrics for a Uniswap V2 or V3 pool: TVL in token0 numeraire, reserves, accumulated fees, LP concentration, and swap activity. Answers 'is this a pool I would deposit into?' at the pool level (not position level). num_swaps and fee_accrual_rate_recent are V2-only; V3 returns null for these because V3 has no per-swap history array. A single-block live snapshot also returns null for the LP-concentration and swap metrics (unrecoverable from state alone).

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.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 19:05 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
404
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
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

The probe stopped: initialize answered HTTP 404.

Posture changes

  1. Oct 29, 2026
    • HTTP status of an anonymous initialize: 200 to 404
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 6 to 0
    • Protocol version: 2025-06-18 to none

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.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 404; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 6 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 404
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 6 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 0.2.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http echoledger https://mcp.echoledger.ai/mcp
claude mcp add --transport http echoledger https://mcp.echoledger.ai/mcp

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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__echoledger__AnalyzePosition",
      "mcp__echoledger__AnalyzeBalancerLP",
      "mcp__echoledger__AnalyzeStableswapLP",
      "mcp__echoledger__CheckPoolHealth",
      "mcp__echoledger__BuildStateTwin"
    ],
    "ask": [
      "mcp__echoledger__SimulatePriceMove",
      "mcp__echoledger__SimulateBalancerMove",
      "mcp__echoledger__SimulateStableswapMove",
      "mcp__echoledger__DetectRugSignals",
      "mcp__echoledger__CalculateSlippage",
      "mcp__echoledger__AssessDepegRisk"
    ],
    "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 echoledger. 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/io.github.icmoore/echoledger-mcp/verify?hash=77676fd1fe898932a1db095b7dccd65dd6d252d7c18d1d8710cab5fa650854ce" | jq -e '.changed == false'

Pinned hash 77676fd1fe89, from Oct 21, 2026, 19:23 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.icmoore/echoledger-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.icmoore/echoledger-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.icmoore/echoledger-mcp.svg)](https://radar.anlyon.com/servers/io.github.icmoore/echoledger-mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:36 UTC.

EchoLedger MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the EchoLedger MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 6 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 EchoLedger MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the EchoLedger 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 EchoLedger MCP server have?

11 tools: 6 write, 5 read. SimulatePriceMove, SimulateBalancerMove, SimulateStableswapMove, DetectRugSignals, CalculateSlippage, AssessDepegRisk, AnalyzePosition, AnalyzeBalancerLP and 3 more.

Does the EchoLedger MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the EchoLedger MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the EchoLedger MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.