TRDEFI Liquidity
REMOTE · YIELD.TRDEFI.COM · SCANNED SEP 29
Live non-custodial stablecoin liquidity: open positions, volume, and an on-chain swap quote.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 541 tokens (~90/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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
claude mcp add --transport http trdefi-liquidity 'https://yield.trdefi.com/mcp'
{
"mcpServers": {
"trdefi-liquidity": {
"url": "https://yield.trdefi.com/mcp"
}
}
} {
"servers": {
"trdefi-liquidity": {
"type": "http",
"url": "https://yield.trdefi.com/mcp"
}
}
} [mcp_servers.trdefi-liquidity] url = "https://yield.trdefi.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"trdefi-liquidity": {
"type": "remote",
"url": "https://yield.trdefi.com/mcp",
"enabled": true
}
}
} openclaw mcp add trdefi-liquidity --url 'https://yield.trdefi.com/mcp' --transport streamable-http
mcp_servers:
trdefi-liquidity:
url: "https://yield.trdefi.com/mcp" {
"McpServers": {
"trdefi-liquidity": {
"Transport": "http",
"Url": "https://yield.trdefi.com/mcp"
}
}
} assistant mcp add trdefi-liquidity -t streamable-http -u 'https://yield.trdefi.com/mcp'
{
"mcpServers": {
"trdefi-liquidity": {
"type": "http",
"url": "https://yield.trdefi.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- Tool “trdefi_positions” rewrote its description, which is the text the model reads security
- Tool “trdefi_quote” rewrote its description, which is the text the model reads security
- Schema quality: 78 → 90 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- 26 Sept 26 65
First indexed and scored.
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 29 Sept 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=yield.trdefi.com | CN=YE1,O=Let's Encrypt,C=US | 15 Aug 2026 | 13 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 63ba34c984e11f908e8d4ab12d886193381 |
| SANs: yield.trdefi.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
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. | present | 19718 | 13 | Verified |
| trdefi.com. | absent | 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 |
| 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 |
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| metric | string | – | – |
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_position_detail ~38
One position in full, by its 32-byte strategy hash.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | Strategy hash, 64 hex characters. |
No output schema declared.
No examples provided.
trdefi_positions ~151
Live non-custodial stablecoin liquidity, as positions an agent can actually trade against. Earn-worthy USDC/USDT maker positions: each row carries the strategy hash, network, pair, tokens and settled volume. Use this before a stablecoin swap to find a real on-chain counterparty, or to survey where stablecoin liquidity sits. Filter by network and by pair. Free, no key, no custody.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Network key, e.g. "base" or "ethereum". Defaults to every network. |
| limit | integer | – | Rows to return. |
| pair | string | – | Pair filter. Currently only the USDC/USDT stable pair is selectable. |
No output schema declared.
No examples provided.
trdefi_quote ~170
Price a stablecoin swap against one position, on-chain, at the current block — no custody, nothing signed, nothing moved. Use this to check USDC/USDT liquidity and get the output amount before preparing a swap. Note that a maker may gate a position on the caller holding an access licence token, and roughly four in five do — those answer with a clear reason instead of a price, which is a property of the maker's strategy rather than an error.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Input amount in token base units, as an integer string. e.g. "1000000" for 1 USDC. |
| chain | string | – | Network key. Defaults to "ethereum". |
| direction | string | – | – |
| hash | string | yes | Strategy hash to quote against. |
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.
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 66 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 6 tools: trdefi_stats, trdefi_chains, trdefi_positions, trdefi_position_detail, trdefi_quote, trdefi_badge. Their descriptions and schemas cost roughly 541 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 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.