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.

TRDEFI Liquidity

REMOTE · YIELD.TRDEFI.COM

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

Available components

0 this week 77 Trust /100

Last scanned (22 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Recent critical change

Authorization (24 Oct 2026). See the changelog before you install this server.

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 Security63
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1941 tokens (~194/item across 10 items; 10 tools + 0 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 94% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

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

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.

  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 7 Nov 26 0
    • “trdefi_quote” added an optional parameter “wallet” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Oct 26 0
    • Schema quality: 1695 → 1871 ▼ functional
    • Schema quality: good → excellent functional
    • New tool “trdefi_position_inventory” functional
  • 26 Oct 26 0
    • Stability: 0.97 → pass security
  • 25 Oct 26 +1
    • Tool “trdefi_quote” rewrote its description, which is the text the model reads security
  • 24 Oct 26 −7
    • Authorization: partial → fail ▼ critical
    • New tool “trdefi_fusion_submit”, which the server declares destructive security
    • Schema quality: 1000 → 1635 ▼ functional
    • Tool coverage: 82% → 93% ▲ functional
    • New tool “trdefi_fusion_prepare” functional
    • New tool “trdefi_fusion_quote” functional
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://yield.trdefi.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=trdefi.com CN=WE1,O=Google Trust Services,C=US 29 Oct 2026 27 Jan 2027 ECDSA 256 ECDSA-SHA256 3e6694099df593e1330025317ac8681
SANs: trdefi.com, *.trdefi.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of yield.trdefi.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
trdefi.com. 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://yield.trdefi.com/mcp Verified 200
http (plaintext) http://yield.trdefi.com/mcp HTTPS enforced 301 https://yield.trdefi.com/mcp
MCP tools · 10 exposed · ~1,941 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
trdefi_badge ~55

A shields.io endpoint payload for the catalogue metrics, so a README can show live figures. Metrics: volume30, volume7, volume1, strategies, makers, pairs, chains.

NameTypeReqDescription
metricstring––

No output schema declared.

No examples provided.

trdefi_chains ~48

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

trdefi_fusion_prepare ~212

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

NameTypeReqDescription
amountstringyesInput amount in token base units, as an integer string.
chainstringyesNetwork key, e.g. "ethereum", "base", "arc".
fromTokenstringyesInput token address.
presetstring–Auction preset. Defaults to the quote recommendation.
toTokenstringyesOutput token address.
walletstringyesThe address that will sign the Fusion order.

No output schema declared.

No examples provided.

trdefi_fusion_quote ~229

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.

NameTypeReqDescription
amountstringyesInput amount in token base units, as an integer string.
chainstringyesNetwork key, e.g. "ethereum", "base", "arc".
fromTokenstringyesInput token address.
presetstring–Auction preset. Defaults to the quote recommendation.
toTokenstringyesOutput token address.
walletstringyesThe address that will sign the Fusion order.

No output schema declared.

No examples provided.

trdefi_fusion_submit ~194

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.

NameTypeReqDescription
chainstringyesNetwork key, e.g. "ethereum", "base", "arc".
extensionstring–The `extension` returned by trdefi_fusion_prepare. Defaults to 0x.
orderobjectyesThe signed Fusion order object returned by trdefi_fusion_prepare (`order`).
quoteIdstring–The `quoteId` returned by trdefi_fusion_prepare.
signaturestringyesEIP-712 signature from the wallet (0x-prefixed hex).

No output schema declared.

No examples provided.

trdefi_position_detail ~38

One position in full, by its 32-byte strategy hash.

NameTypeReqDescription
hashstringyesStrategy hash, 64 hex characters.

No output schema declared.

No examples provided.

trdefi_position_inventory ~176

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.

NameTypeReqDescription
hashstringyesStrategy hash, 64 hex characters.
overviewboolean–Also fetch 1inch's overview (status, openedAt, price range). Costs the upstream rate limit, so it is off by default.

No output schema declared.

No examples provided.

trdefi_positions ~280

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.

NameTypeReqDescription
chainstring–Network key, e.g. "base" or "ethereum". Defaults to every network.
limitinteger–Rows to return.
pairstring–Pair filter. Either an exact pair such as "USDC/USDT", or a substring such as "USDC" or "WETH" which matches any pair containing it, or a network name, or part of a strategy hash.
quote_readyboolean–True returns positions on a network that has a quote route, which is the quote_eligible set. False returns the positions that do not, which are usually on networks with no quote RPC. Neither guarante…

No output schema declared.

No examples provided.

trdefi_quote ~630

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.

NameTypeReqDescription
amountstringyesInput amount in token base units, as an integer string. e.g. "1000000" for 1 USDC.
chainstring–Network key. Defaults to "ethereum".
directionstring––
fromstring–The address that will sign the swap, simulated as msg.sender. Supply it whenever the caller might hold the maker's access credential: the gate is checked on tx.origin, so with an address the answer i…
hashstringyesStrategy hash to quote against.
walletstring–The wallet that would trade. When a position is gated, this asks for a Fusion price instead: a 1inch resolver fills the order, so the wallet needs no credential, and the answer is executable rather t…

No output schema declared.

No examples provided.

trdefi_stats ~79

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the TRDEFI Liquidity MCP server?

TRDEFI Liquidity is a hosted endpoint at https://yield.trdefi.com/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 · yield.trdefi.com

# add to Claude Code
claude mcp add --transport http trdefi-liquidity 'https://yield.trdefi.com/mcp'
Common questions

What is the TRDEFI Liquidity MCP server?

TRDEFI Liquidity is an MCP server listed in the public MCP registry as io.github.TRDEFI/liquidity. Live non-custodial stablecoin liquidity: open positions, volume, and an on-chain swap quote. This page covers its hosted endpoint (https://yield.trdefi.com/mcp).

Is the TRDEFI Liquidity MCP server safe to use?

TRDEFI Liquidity scores 77 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 TRDEFI Liquidity MCP server expose?

TRDEFI Liquidity exposes 10 tools: trdefi_stats, trdefi_chains, trdefi_positions, trdefi_position_detail, trdefi_position_inventory, and 5 more. Their descriptions and schemas cost roughly 1,941 tokens of context every time the server is loaded.

Does the TRDEFI Liquidity MCP server require authentication?

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

Is the TRDEFI Liquidity MCP server still maintained?

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

VerifyMCP ran 13 checks on TRDEFI Liquidity, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.