# Trnch on Elysium (remote · trnch.fun)

Free, no key: Elysium token facts, wallet scan, top by volume, stats, quotes. Trade with a key.

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `trnch.fun`: 73/100 (this document), [markdown](https://verifymcp.io/servers/fun-trnch-trnch-elysium/elysium-api-mcp.md), [page](https://verifymcp.io/servers/fun-trnch-trnch-elysium/elysium-api-mcp)

## Channel facts

- Endpoint: `https://trnch.fun/elysium/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3914 tokens (~326/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Trnch on Elysium MCP server?

Trnch on Elysium is a hosted endpoint at https://trnch.fun/elysium/api/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.

### Claude

```bash
claude mcp add --transport http fun-trnch-trnch-elysium 'https://trnch.fun/elysium/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "fun-trnch-trnch-elysium": {
      "url": "https://trnch.fun/elysium/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "fun-trnch-trnch-elysium": {
      "type": "http",
      "url": "https://trnch.fun/elysium/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.fun-trnch-trnch-elysium]
url = "https://trnch.fun/elysium/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fun-trnch-trnch-elysium": {
      "type": "remote",
      "url": "https://trnch.fun/elysium/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add fun-trnch-trnch-elysium --url 'https://trnch.fun/elysium/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  fun-trnch-trnch-elysium:
    url: "https://trnch.fun/elysium/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "fun-trnch-trnch-elysium": {
      "Transport": "http",
      "Url": "https://trnch.fun/elysium/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add fun-trnch-trnch-elysium -t streamable-http -u 'https://trnch.fun/elysium/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "fun-trnch-trnch-elysium": {
      "type": "http",
      "url": "https://trnch.fun/elysium/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 73, +1)

- [cosmetic] “trnch_quote” added an optional parameter “slippageBps”
- [cosmetic] “trnch_quote” reworded the description of “slippage”

### 2026-11-19 (score 72, 0)

- [security] Tool “trnch_buy” rewrote its description, which is the text the model reads
- [security] Tool “trnch_quote” rewrote its description, which is the text the model reads
- [security] Tool “trnch_sell” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 287 → 323
- [functional] New tool “trnch_partner_fee_get”
- [functional] New tool “trnch_partner_fee_set”
- [cosmetic] “trnch_buy” added an optional parameter “integratorFeeBps”
- [cosmetic] “trnch_quote” added an optional parameter “integratorFeeBps”
- [cosmetic] “trnch_sell” added an optional parameter “integratorFeeBps”

### 2026-11-17 (score 72, +1)

- [security] Tool “trnch_register” rewrote its description, which is the text the model reads
- [functional] Server version: 1.1.0 → 1.1.1

### 2026-11-15 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 70, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “trnch_check” rewrote its description, which is the text the model reads
- [security] Tool “trnch_quote” rewrote its description, which is the text the model reads
- [security] Tool “trnch_register_message” rewrote its description, which is the text the model reads
- [security] Tool “trnch_stats” rewrote its description, which is the text the model reads
- [security] Tool “trnch_top_volume” rewrote its description, which is the text the model reads
- [security] Tool “trnch_scan_wallet” rewrote its description, which is the text the model reads
- [functional] Server version: 1.0.0 → 1.1.0
- [cosmetic] “trnch_quote” reworded the description of “tokenIn”
- [cosmetic] “trnch_quote” reworded the description of “tokenOut”

### 2026-11-13 (score 70, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “trnch_buy” rewrote its description, which is the text the model reads
- [security] Tool “trnch_quote” rewrote its description, which is the text the model reads
- [security] Tool “trnch_sell” rewrote its description, which is the text the model reads
- [security] Tool “trnch_stats” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 69)

First indexed and scored.

## MCP tools (12)

### `trnch_check` (~776 tokens)

Token facts read on chain

Free, no key, no wallet: read on-chain facts about any Elysium token before you trade it. Returns { token, chainId, screened: false, sellTest, hookFee, liquidity, creator, launchpad, template, forcedTransfer, meaning }: sellTest { class, result, blockedAt, complete, variantsRun, variantsSkipped, lossPct, method, sizes [{ amount, result, lossPct }], extraLossPctAtLargerSize, buyTaxPct, transfer { ok, backOk, taxPct }, sellLossPct, logsMatchBalances, delayed { clockAdvancedMinutes, result }, note }: a simulation at the time of the read that tries to buy, approve, transfer wallet to wallet and back, and sell from both wallets, as separate transactions, through the pools Trnch would route through (the proven launch pool, the deepest and the oldest qualifying pool; the worst result decides: decidingPool, poolTested, checkedAt), at two sizes and again with the clock advanced 5 minutes in simulation; note says in words what actually ran, complete, variantsRun and variantsSkipped say what did not and why, and a partial result reads "(partial check)"; class sold (bought, transferred and sold in a simulation, every step that ran succeeded), taxed, blocked (blockedAt says whether the approval or the sell failed in the simulation), transfer-failed (the tokens could not be moved between wallets in the simulation) or not-checked; buy tax, transfer tax and sell loss are reported apart, and token logs that do not match balances are reported. A simulation now: the token may behave differently later or towards other wallets, and an upgradeable or owner-controlled token can change; sizes 0.25 HYPE and, when the pool is deep enough, 1.5 HYPE; poolTested { id, feeBps, hook, launchpad, poolThinForSize, depthLowerBound }; decidingPool { id, roles, why }; poolsTested; poolsTruncated; checkedAt; hookFee { buyBps, sellBps } when the pool has a launch hook; liquidity { found, usdEstimate }; creator { launches }: how many tokens the same creator launched before this one; launchpad { result, h…

Input parameters:

- `token` (string, required): Token contract address on Elysium (chainId 99901).

### `trnch_scan_wallet` (~178 tokens)

List a wallet's tokens with on-chain facts

Free, no key: list the tokens an Elysium wallet holds in one call. Returns { wallet, truncated, partial, checked, tokens }: each token has address, symbol, name, balance { raw, decimals }, valueUsd when known, majorAsset, factsStatus and facts { sellTest, hookFee, liquidity, creator, launchpad, template, forcedTransfer } as in trnch_check, read for the 8 largest holdings that are not HYPE, WHYPE or USDC (others: factsStatus over_limit, call trnch_check). At most 100 tokens, largest first. Cached 60 s per wallet. Facts, not a verdict: Trnch runs no rug screen on this chain.

Input parameters:

- `wallet` (string, required): Wallet address on Elysium (chainId 99901).

### `trnch_top_volume` (~135 tokens)

Top Elysium tokens by 24-hour volume

Free, no key: the tokens of the Elysium pools with the most trading volume over the last 24 hours, in the order GeckoTerminal lists them (the Top volume list of Trade on Trnch), with a link to trade each. HYPE, WHYPE and USDC are left out. Returns { tokens [{ rank, address, symbol, name, logoUrl, trade }] }, no volume figures. A volume ranking, not a screen, a verdict or a recommendation: Trnch runs no rug screen on this chain.

Input parameters:

- `limit` (integer): How many tokens (default 10).

### `trnch_stats` (~133 tokens)

Trnch on Elysium: chain, routers, fees and activity

Free, no key: read the facts of trnch on Elysium: chainId 99901, gas HYPE, reference stable USDC, the five routers (Uniswap, KyberSwap, LI.FI, Nordstern and 0x), the bot fee grid in percent, and activity { windows [{ window (24h, 7d, 30d), volumeUsd, swaps, traders }] } counted from swaps made through Trnch on this chain (null while hidden or unavailable). No Heat and no rug counts: Trnch runs no rug screen on this chain.

### `trnch_quote` (~563 tokens)

Quote a swap

Free, no key, no wallet: quote any pair on Elysium across five routers (Uniswap, KyberSwap, LI.FI, Nordstern and 0x) without building a transaction. Returns the best amount out, already net of the Trnch fee, the router and the fee rate in basis points (feeBps). Native HYPE is the zero address. A transaction (trnch_buy, trnch_sell) needs an API key. A partner's integrator fee (integratorFeeBps, or the partner's default fee when the request carries X-Trnch-Partner-Key) is added to the Trnch fee and taken by the same router fee on every router; a router whose maximum fee is below the total is left out of the quote. The integrator fee is paid to the partner through the Trnch partner program after the swap is confirmed on chain. fees in the response: { side, token, trnch { bps, amount }, integrator { bps, amount, partner } or null, minAmountOut }, amounts in the smallest unit; minAmountOut is net of both fees and of slippage.

Input parameters:

- `amountIn` (string, required): Amount of tokenIn in its smallest unit (wei-style integer string).
- `decimalsIn` (integer): Decimals of tokenIn. Default 18: set it for USDC (6) and other non-18 tokens.
- `decimalsOut` (integer): Decimals of tokenOut. Default 18: set it for USDC (6) and other non-18 tokens.
- `fast` (boolean): Return the first clean quote after about 250 ms instead of waiting for the best price. Default false.
- `integratorFeeBps` (integer): Integrator fee in basis points, 0 to 100, for a partner identified by X-Trnch-Partner-Key or by the partner ref of the API key. Overrides the partner's default fee; the default fee applies only with…
- `slippage` (number): Legacy: max slippage as a fraction (0.01 = 1%). Send slippageBps or slippage, not both.
- `slippageBps` (integer): Max slippage in basis points (100 = 1%). Default 100.
- `tokenIn` (string, required): Token sold: an Elysium token address, or the zero address for HYPE.
- `tokenOut` (string, required): Token bought: an Elysium token address, or the zero address for HYPE.

### `trnch_register_message` (~84 tokens)

Get the message to sign

Step 1 of 2 to get an API key for trading, no browser. Returns { message }: the exact text your wallet must sign with personal_sign (EIP-191). It is valid for 10 minutes and moves no funds.

Input parameters:

- `wallet` (string, required): The agent wallet that will trade (EOA or EIP-1271 smart wallet).

### `trnch_register` (~144 tokens)

Create an API key

Step 2 of 2: send the message returned in step 1 and its signature; returns { key, prefix, wallet } with status 201. The key is shown once, store it. 3 keys max per wallet (409); 400 if the message expired or was altered, 401 if the signature does not match.

Input parameters:

- `label` (string): Optional name for the key, e.g. the agent name.
- `message` (string, required): The message returned in step 1, unchanged.
- `signature` (string, required): personal_sign signature of message by wallet.
- `wallet` (string, required): Same wallet as in trnch_register_message.

### `trnch_buy` (~527 tokens)

Buy a token

Build a buy in one call: quotes five routers and returns the best route as a transaction for the key's wallet to sign. Give token, and amountUsd (paid in USDC) or amountIn with tokenIn (the zero address pays in HYPE). The Trnch fee is already deducted from the quote; the rate applied is returned as feeBps. Returns { router, feeBps, quote, approval, tx, chainId, from }: approval, when not null, has to be sent before tx, from the same wallet (chainId 99901). Nothing is sent by Trnch. Errors: 503 while the fee recipient is not configured on this chain (nothing is built), 404 no route, 429 rate or build limit (retry-after). A partner's integrator fee (integratorFeeBps, or the partner's default fee when the request carries X-Trnch-Partner-Key) is added to the Trnch fee and taken by the same router fee on every router; a router whose maximum fee is below the total is left out of the quote. The integrator fee is paid to the partner through the Trnch partner program after the swap is confirmed on chain. fees in the response: { side, token, trnch { bps, amount }, integrator { bps, amount, partner } or null, minAmountOut }, amounts in the smallest unit; minAmountOut is net of both fees and of slippage. Requires an API key (created by wallet signature), sent as Authorization: Bearer <key>.

Input parameters:

- `amountIn` (string): Amount of tokenIn to spend, smallest unit. Use this or amountUsd.
- `amountUsd` (number): Amount to spend in US dollars, paid in USDC. Use this or amountIn.
- `integratorFeeBps` (integer): Integrator fee in basis points, 0 to 100, for a partner identified by X-Trnch-Partner-Key or by the partner ref of the API key. Overrides the partner's default fee; the default fee applies only with…
- `slippageBps` (integer): Max slippage in basis points (100 = 1%). Default 100.
- `token` (string, required): Token to buy, as an address.
- `tokenIn` (string): Token paid with amountIn. Default USDC.

### `trnch_sell` (~508 tokens)

Sell a token

Build a sell for USDC in one call: give token, and percent of the wallet balance (read on chain) or an exact amount. Quotes five routers and returns the best route as a transaction to sign. The Trnch fee is already deducted from the quote; the rate applied is returned as feeBps. Returns { router, feeBps, quote, approval, tx, chainId, from }: approval, when not null, has to be sent before tx, from the same wallet (chainId 99901). Nothing is sent by Trnch. Errors: 503 while the fee recipient is not configured on this chain (nothing is built), 404 no route, 429 rate or build limit (retry-after). A partner's integrator fee (integratorFeeBps, or the partner's default fee when the request carries X-Trnch-Partner-Key) is added to the Trnch fee and taken by the same router fee on every router; a router whose maximum fee is below the total is left out of the quote. The integrator fee is paid to the partner through the Trnch partner program after the swap is confirmed on chain. fees in the response: { side, token, trnch { bps, amount }, integrator { bps, amount, partner } or null, minAmountOut }, amounts in the smallest unit; minAmountOut is net of both fees and of slippage. Requires an API key (created by wallet signature), sent as Authorization: Bearer <key>.

Input parameters:

- `amount` (string): Exact amount in token units, e.g. 1234.5. Capped at the balance. Use this or percent.
- `integratorFeeBps` (integer): Integrator fee in basis points, 0 to 100, for a partner identified by X-Trnch-Partner-Key or by the partner ref of the API key. Overrides the partner's default fee; the default fee applies only with…
- `percent` (number): Share of the wallet balance to sell, 100 = all. Use this or amount.
- `slippageBps` (integer): Max slippage in basis points (100 = 1%). Default 100.
- `token` (string, required): Token to sell, as an address.

### `trnch_confirm` (~255 tokens)

Report a sent swap

Optional, after sending a swap built by trnch_buy or trnch_sell on Elysium (chainId 99901): report its hash. Returns { ok, txHash, chainId, status: "pending", meaning }, an acknowledgement only: it does not send, cancel or change the transaction. Nothing is credited on the call. A scheduled pass (every 2 minutes) reads the transaction on Elysium: sent by the key's wallet, a swap Trnch built for it, and the Trnch fee paid to the Trnch fee recipient in that same transaction. Only then is its volume counted in the swap stats of Elysium; there are no points or rewards on this chain. A hash that does not prove all of this counts nothing. Calling it twice with the same hash changes nothing. 10 calls per minute per key; 20 hashes at most awaiting settlement per wallet (429). 409 if the wallet has no Trnch account (sign in once on the site). Requires an API key (created by wallet signature), sent as Authorization: Bearer <key>.

Input parameters:

- `txHash` (string, required): Hash of the Elysium transaction you sent.

### `trnch_partner_fee_get` (~168 tokens)

Read the partner integrator fee

Read the default integrator fee of a Trnch partner. Returns { partner, bps, maxBps }: partner is the partner code, bps the default fee in basis points (0 to maxBps, 100). The default fee is added to the Trnch fee on swaps attributed to the partner and paid to the partner through the partner program; integratorFeeBps on a quote, buy or sell overrides it for that request; the default applies only to requests that carry X-Trnch-Partner-Key. Authentication: header X-Trnch-Partner-Key linked to a Trnch partner, or Authorization: Bearer <API key> of the partner payout wallet; 401 otherwise. 20 calls per minute per IP (429).

### `trnch_partner_fee_set` (~137 tokens)

Set the partner integrator fee

Set the default integrator fee of a Trnch partner, an integer from 0 to 100 basis points. Returns { partner, bps, maxBps, previousBps }. Each change is recorded with its channel. 400 for a value out of range. Authentication: header X-Trnch-Partner-Key linked to a Trnch partner, or Authorization: Bearer <API key> of the partner payout wallet; 401 otherwise. 20 calls per minute per IP (429).

Input parameters:

- `bps` (integer, required): New default integrator fee in basis points (100 = 1%).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/fun-trnch-trnch-elysium/elysium-api-mcp#diagnostics

## Score history

- 2026-11-21: 73
- 2026-11-20: 73
- 2026-11-19: 72
- 2026-11-18: 72
- 2026-11-17: 72
- 2026-11-16: 71
- 2026-11-15: 71
- 2026-11-14: 70
- 2026-11-13: 70
- 2026-11-12: 69

## Common questions

### What is the Trnch on Elysium MCP server?

Trnch on Elysium is an MCP server listed in the public MCP registry as fun.trnch/trnch-elysium. Free, no key: Elysium token facts, wallet scan, top by volume, stats, quotes. Trade with a key. This page covers its hosted endpoint (https://trnch.fun/elysium/api/mcp).

### Is the Trnch on Elysium MCP server safe to use?

Trnch on Elysium scores 73 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 Trnch on Elysium MCP server expose?

Trnch on Elysium exposes 12 tools: trnch_check, trnch_scan_wallet, trnch_top_volume, trnch_stats, trnch_quote, and 7 more. Their descriptions and schemas cost roughly 3,608 tokens of context every time the server is loaded.

### Does the Trnch on Elysium MCP server require authentication?

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

### Is the Trnch on Elysium MCP server still maintained?

Trnch on Elysium 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 Trnch on Elysium MCP server?

VerifyMCP ran 13 checks on Trnch on Elysium, 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.

## Links

- Remote endpoint: https://trnch.fun/elysium/api/mcp
- Website: https://trnch.fun/elysium/mcp
- Changelog RSS feed: https://verifymcp.io/servers/fun-trnch-trnch-elysium/elysium-api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/fun-trnch-trnch-elysium/elysium-api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/fun-trnch-trnch-elysium/elysium-api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/fun-trnch-trnch-elysium/elysium-api-mcp
