Skip to content

TRDEFI Liquidity MCP server

io.github.TRDEFI/liquidityTRDEFIstreamable-httpv1.0.1Scanned

Live non-custodial stablecoin liquidity: open positions, volume, and an on-chain swap quote.

10 tools: 1 can delete or cancel things and 9 change things.

Tools: 1 delete, 0 irreversible, 9 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 10
  • Can send data out · 0
  • 4 findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 TRDEFI Liquidity MCP server can do

The TRDEFI Liquidity MCP server is published by the GitHub account TRDEFI. It has 10 tools. It can delete or cancel things (1 tool: trdefi_fusion_submit) and create or change data (9 tools: trdefi_stats, trdefi_chains, trdefi_positions, trdefi_position_detail and 5 more). None of its tools only reads.

10 tools bring in text other people can write (trdefi_stats, trdefi_chains, trdefi_positions and 7 more).

The fixed checks matched 4 findings (credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 19, 2026, version 1.0.1.

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.

10 tools

Deletes or cancels 1Claude Code: deny
  • trdefi_fusion_submitForward an already-signed Fusion order to 1inch's relayer.Reads text others writeNo findings

    Why it is in this group

    • The name "trdefi_fusion_submit" says "submit": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Forward an already-signed Fusion order to 1inch's relayer. The signature is the user's authorization; this server never signs and never holds a key. Pass the `order`, `signature`, `extension` and `quoteId` returned by trdefi_fusion_prepare. A resolver fills the order later; submission does not guarantee a fill.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Changes things 9Claude Code: ask
  • trdefi_badgeA shields.io endpoint payload for the catalogue metrics, so a README can show live figures.Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    A shields.io endpoint payload for the catalogue metrics, so a README can show live figures. Metrics: volume30, volume7, volume1, strategies, makers, pairs, chains.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • trdefi_chainsThe networks where liquidity is live right now, with each network's settlement engine address and the tokens a position can be built from.Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    The networks where liquidity is live right now, with each network's settlement engine address and the tokens a position can be built from. Use this instead of hardcoding chain or token identifiers.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • trdefi_fusion_prepareQuote and build an EIP-712 Fusion order.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Quote and build an EIP-712 Fusion order. Returns `typedData` (sign with eth_signTypedData_v4), the `order` object, `extension`, `quoteId` and `orderHash`. Nothing is signed or submitted. After signing, call trdefi_fusion_submit with the same order, the signature, extension and quote id. This is the gated-liquidity path: the user/agent does not need an Aqua NFT; a 1inch resolver fills the order (best-effort, not guaranteed).

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • trdefi_fusion_quoteA 1inch Fusion quote for a token pair.Reads text others write1 finding

    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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...NFT, because a 1inch resolver with the credential fills the order. Returns the expected o..."

      What this check looks for
    Description, as the server wrote it
    A 1inch Fusion quote for a token pair. Use this when a position answers "Strategy is gated": the user/agent does not need an Aqua NFT, because a 1inch resolver with the credential fills the order. Returns the expected output, the Fusion resolver fee and a quote id. Free, read-only, nothing signed or moved. Chain, token addresses and base-unit amounts come from trdefi_positions / trdefi_chains. Note: a Fusion fill is best-effort, not guaranteed: the resolver chooses the venue, and a gated Aqua position is used only if that resolver holds the Aqua NFT.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • trdefi_position_detailOne position in full, by its 32-byte strategy hash.Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    One position in full, by its 32-byte strategy hash.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • trdefi_position_inventoryWhether one position can actually be filled right now: the balance sitting in the strategy, the maker wallet balance behind it, and the remaining allowance, read from the chain.Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Whether one position can actually be filled right now: the balance sitting in the strategy, the maker wallet balance behind it, and the remaining allowance, read from the chain. An Aqua virtual balance is a bookkeeping ceiling, not a reserve, so a position can answer a quote while the wallet behind it is empty - and the swap then reverts at the pull. Check this before signing a swap against a position that matters: fillable=false means the quote is real but the fill is not. Read-only, free, no key, and no dependency on 1inch rate limits.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • trdefi_positionsLive non-custodial liquidity, as positions an agent can actually trade against.Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Live non-custodial liquidity, as positions an agent can actually trade against. Each row carries the strategy hash, network, pair, tokens, settled volume and a `quote_eligible` flag, meaning the position is router-attached and its network has a quote route. It does NOT mean the position will quote: a maker can still gate it. Use this before a swap to find a real on-chain counterparty, or to survey where liquidity sits. Filter by network and by pair. Free, no key, no custody.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • trdefi_quotePrice a swap against one position, on-chain, at the current block — no custody, nothing signed, nothing moved.Reads text others write3 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...e swap. A caller that holds the maker's credential gets a real price; anyone else gets an..."

      What this check looks for
    • Info

      The input schema at properties.from.description mentions "credential".

      Matched text

      inputSchema.properties.from.description: "...he caller might hold the maker's access credential: the gate is checked on tx.origin, so w..."

      What this check looks for
    • Info

      The input schema at properties.wallet.description mentions "credential".

      Matched text

      inputSchema.properties.wallet.description: "...fills the order, so the wallet needs no credential, and the answer is executable rather th..."

      What this check looks for
    Description, as the server wrote it
    Price a swap against one position, on-chain, at the current block — no custody, nothing signed, nothing moved. Works on any pair the position trades, not only stablecoins. Use this to check liquidity and get the output amount before preparing a swap. If a position answers "Strategy is gated", the maker embedded an access-licence check in the order: the CALLER must hold the 1inch Aqua access token. That check reads tx.origin, so the revert depends on whether a caller was supplied: without one it is 0x89c62b64 ("the caller holds none"), with one it is 0x39c4052c (the tx-origin balance check). Pass `from` with the address that will actually sign the swap. A caller that holds the maker's credential gets a real price; anyone else gets an accurate "you do not hold it" instead of the least specific answer available. This is a property of the strategy, not a bug — and it is strongly per-network. Measured 2026-10-19: on Ethereum 58 of 60 sampled positions are gated, and across 17 networks the network-balanced split is about 62 percent gated and 17 percent priced. The credential contract itself is only deployed on the 13 Aqua chains, so Arc, Monad, Cronos and HyperEVM have no such gate. The response also decodes the fee from the signed order: `fee_decoding` is decoded/none/unsupported, `maker_fee_percent` is the maker commission (for example 0.00025), `maker_fee_receiver` is its receiver, and `fees` lists every fee instruction. Quotes are simulated on 17 networks: ethereum, base, arbitrum, optimism, polygon, arc, bnb-chain, gnosis, avalanche, sonic, linea, zksync-era, monad, unichain, hyperevm, cronos and robinhood-chain. This list is the set the quote path actually serves; if a network is not on it, do not promise a quote for it.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • trdefi_statsAggregate statistics for the live TRDEFI non-custodial stablecoin liquidity catalogue: how many open maker positions exist, how many distinct makers, how many pairs, across how man…Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Aggregate statistics for the live TRDEFI non-custodial stablecoin liquidity catalogue: how many open maker positions exist, how many distinct makers, how many pairs, across how many networks, plus settled volume over 1, 7 and 30 days, and the deepest pairs by volume and by position count. Free, no key.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

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 outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write10
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.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:00 UTC, unchanged since Nov 6, 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
10
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
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 10 tools that change things (1 destructive, 9 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://yield.trdefi.com/mcp: tools/list returned 10 tools to an anonymous client, including trdefi_fusion_submit (destructive), trdefi_stats (write), trdefi_chains (write), trdefi_positions (write), trdefi_position_detail (write) and 5 more

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Tools that change things, listed without credentials: 9 to 10
  2. Oct 29, 2026
    • Tools that change things, listed without credentials: 6 to 9

Findings

Matches of fixed checks, with the text they matched.

4 info
  • The description mentions "credential".

    Matched text

    description: "...e swap. A caller that holds the maker's credential gets a real price; anyone else gets an..."

    What this check looks for
  • The input schema at properties.from.description mentions "credential".

    Matched text

    inputSchema.properties.from.description: "...he caller might hold the maker's access credential: the gate is checked on tx.origin, so w..."

    What this check looks for
  • The input schema at properties.wallet.description mentions "credential".

    Matched text

    inputSchema.properties.wallet.description: "...fills the order, so the wallet needs no credential, and the answer is executable rather th..."

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "...NFT, because a 1inch resolver with the credential fills the order. Returns the expected o..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 9 -> 10.View diff
    • Tools that change things, listed without credentials: 9 to 10
  3. Tools4 added, 1 changed.+4 added~1 changedView diff
  4. PostureRemote posture changed. Tools that change things, listed without credentials: 6 -> 9.View diff
    • Tools that change things, listed without credentials: 6 to 9

Install

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

claude mcp add --transport http liquidity https://yield.trdefi.com/mcp
claude mcp add --transport http liquidity https://yield.trdefi.com/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": [],
    "ask": [
      "mcp__liquidity__trdefi_stats",
      "mcp__liquidity__trdefi_chains",
      "mcp__liquidity__trdefi_positions",
      "mcp__liquidity__trdefi_position_detail",
      "mcp__liquidity__trdefi_position_inventory",
      "mcp__liquidity__trdefi_quote",
      "mcp__liquidity__trdefi_fusion_quote",
      "mcp__liquidity__trdefi_fusion_prepare",
      "mcp__liquidity__trdefi_badge"
    ],
    "deny": [
      "mcp__liquidity__trdefi_fusion_submit"
    ]
  }
}

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 liquidity. Review it before you use it.

Capability tags behind 10 rules
  • mcp__liquidity__trdefi_stats untrusted-input
  • mcp__liquidity__trdefi_chains untrusted-input
  • mcp__liquidity__trdefi_positions untrusted-input
  • mcp__liquidity__trdefi_position_detail untrusted-input
  • mcp__liquidity__trdefi_position_inventory untrusted-input
  • mcp__liquidity__trdefi_quote untrusted-input
  • mcp__liquidity__trdefi_fusion_quote untrusted-input
  • mcp__liquidity__trdefi_fusion_prepare untrusted-input
  • mcp__liquidity__trdefi_fusion_submit untrusted-input
  • mcp__liquidity__trdefi_badge 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.TRDEFI/liquidity/verify?hash=8a2e8b0ad5e3a744878bb397ff94bb9eabacfd86b1644e7934c1e6f2e2878c9a" | jq -e '.changed == false'

Pinned hash 8a2e8b0ad5e3, from Nov 19, 2026, 10: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.TRDEFI/liquidity/changes.xml

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

Badge

Anlyon Radar badge for io.github.TRDEFI/liquidity
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.TRDEFI/liquidity.svg)](https://radar.anlyon.com/servers/io.github.TRDEFI/liquidity)

Source: MCP Registry · repository. Synced Nov 19, 2026, 10:17 UTC.

TRDEFI Liquidity MCP server: questions and answers

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

Is the TRDEFI Liquidity MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 10 of which can change, send or delete something, and 4 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 TRDEFI Liquidity MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: trdefi_fusion_submit.

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

10 tools: 1 destructive, 9 write. trdefi_fusion_submit, trdefi_stats, trdefi_chains, trdefi_positions, trdefi_position_detail, trdefi_position_inventory, trdefi_quote, trdefi_fusion_quote and 2 more.

Does the TRDEFI Liquidity MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the TRDEFI Liquidity MCP server send data to outside services?

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

Has the TRDEFI Liquidity MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.