TronRelic
● Activecom.tronrelic/mcp
TRON energy rental prices and market activity from TronRelic. Free account unlocks more tools.
Connect this server
One click to install, or copy the config below. Suits: Cursor · HTTP clients.
Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):
{
"mcpServers": {
"mcp": {
"url": "https://tronrelic.com/mcp"
}
}
}claude mcp add --transport http mcp https://tronrelic.com/mcpcode --add-mcp '{"name":"mcp","type":"http","url":"https://tronrelic.com/mcp"}'Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.
A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.
- Category
- Food, Home & Lifestyle
- Version
- 1.2.1
- Registry
- active
- Published
- 11/16/2026
Live check
checked Nov 21, 2026, 04:09 UTCThe endpoint answered the MCP handshake as "TronRelic" and listed 8 tools. Answering since Nov 18, 2026.
Context cost ≈ 6.1k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 8 tools.
Tools (8)
tool list changed Nov 21, 2026, 04:09 UTCresource-markets-get-activity2 paramsReport what TronRelic's tracked energy rental markets did, as recorded on chain by each market's examiner: TRX paid by renters, energy delivered, the blended price paid in SUN per energy per day, how many sampled payments were served or never served, how fast deliveries followed payments, and how concentrated the suppliers are, plus one row of totals per UTC day. Use it first for any question about volume, revenue, prices paid, or which markets are busy or have gone quiet, over a day or a few weeks. Do not use it to check individual rentals (use resource-markets-list-rentals), for how a market is set up (use resource-markets-get-config), or for what a market advertises, its rate card, or what it pays holders (use resource-markets-get-prices; this tool reports prices renters actually paid). Read-only. Parameters: "slug" (optional), a market slug such as "catfee" or "tron-max-io", to report one market in full; "days" (optional), how many UTC days of daily totals to return, ending today, default 7, up to 14 for every market or 30 for one. Without "slug", returns { success, asOf, days, pageUrl, markets: [{ slug, displayName, pageUrl, observed, storefront, summary, daily }] }. "storefront" is null for most markets. For a market that, in TronRelic's reading of the chain data, appears to be another tracked market's storefront, it is { operatorSlug, figuresIncludedInOperator }. When "figuresIncludedInOperator" is true, the storefront's figures are a subset of the operator's and are already inside the operator's totals: never add a storefront's figures to its operator's, or the same rentals are counted twice. Describe the link as TronRelic's reading of the data, not as a fact about who owns either business. The top-level "pageUrl" is TronRelic's page comparing every market, and each market's "pageUrl" is its TronRelic page with these figures; when you cite a figure, link the matching page so the reader can check it there. Either is null when the site address is unknown. "sum
Show parametersHide parameters
slugstringMarket slug such as "catfee". Omit to report every market.daysintegerUTC days of daily totals, ending today. Omit for 7. Up to 14 for every market, 30 for one.
resource-markets-get-prices5 paramsReport what TronRelic's tracked energy rental markets advertise, as captured from each market's own rate card on a schedule an admin sets, which can change at any time, so read the spacing between captures from the "capturedAt" times returned rather than assuming one: which market is cheapest for a given order, every market's advertised price range and open orderbook, one market's full rate card and price history, and what each market pays TRX holders who supply it energy. Use it first for "which market is cheapest for N transfers", "what does this market charge", "how has its advertised price moved", or "which market pays holders the most". Prices here are what markets advertise; for what renters actually paid, use resource-markets-get-activity, and compare the two to see whether a market charges what it advertises. Do not use it for how a market is set up (use resource-markets-get-config). Read-only. Parameters: "slug" (optional), a market slug such as "catfee", to report one market in full; "transfers" (optional), how many USDT transfers the order must cover, 1 to 100000, default 1; "periodMinutes" (optional), the minutes within which they are sent, 1 to 129600, default 60; "usage" (optional), for a period longer than a day, "flexible" when the transfers may be sent at any time, which only a rental of a day or longer can serve, or "batched" when each day's transfers are sent together inside one rental that may last only minutes, default "flexible"; "historyDays" (optional), days back from now to look over past capture runs, 1 to 30: with "slug" it sets that market's history, default 7; without "slug" it adds a "history" summary to the ranking and is left out by default. Use "historyDays" without "slug" for "which market was cheapest for this order over the week": it prices the order on the rate card each market showed at every capture run in the window, not on the newest one. Every answer carries "pageUrl", TronRelic's page comparing every market, and every marke
Show parametersHide parameters
slugstringMarket slug such as "catfee". Omit to price the order on every market and rank them.transfersintegerUSDT transfers the order must cover, 1 to 100000. Omit for 1.periodMinutesintegerMinutes within which the transfers are sent, 1 to 129600. Omit for 60.usagestringFor a period longer than a day: "flexible" (sent at any time) or "batched" (each day's transfers sent together in one rental). Omit for "flexible".historyDaysintegerDays back over past capture runs, 1 to 30. With "slug": the market's history, default 7. Without "slug": adds the "history" summary of every market's lowest and
get-blog-post1 paramNeeds a free TronRelic account: calling it makes your app ask the user to sign in, then the call runs. Fetch one PUBLISHED blog post by its id, including the full markdown body. Use after list-blog-posts to read a specific post in full (e.g. to summarise or quote it). The "id" is the value list-blog-posts returns on each row (a UUID). Read-only; never mutates. Returns { success: true, post: { id, slug, title, tags, bodyMarkdown, publishedAt, updatedAt } }, or { success: true, post: null } when no PUBLISHED post owns that id (an unpublished draft or unknown id both return null — this is a normal result, not an error). Never returns unpublished drafts.
Show parametersHide parameters
idstringrequiredThe post id (a UUID) from a list-blog-posts row.
list-blog-posts2 paramsNeeds a free TronRelic account: calling it makes your app ask the user to sign in, then the call runs. List PUBLISHED blog posts, newest first, as lightweight summaries (no body). Use to discover what posts exist, find a recent post, or gather posts to summarise (each row carries "publishedAt", so you can select posts within a time window such as the last 48 hours yourself). Read-only; never mutates. Parameters: "page" (optional, 1-based, default 1) and "limit" (optional, default 20, clamped to 50). Returns { success, posts: [{ id, slug, title, tags, excerpt, publishedAt }], total, page, limit }, where "total" is the full published count for paging, "excerpt" is a short plain-text opening of the body you can read to pick the relevant post without fetching it, and each "id" can be passed to get-blog-post to read the full markdown body. Only published posts are ever returned.
Show parametersHide parameters
pageinteger1-based page number (optional, default 1). Values below 1 are treated as 1.limitintegerPage size (optional, default 20); clamped to the range 1-50.
pages-get1 paramNeeds a free TronRelic account: calling it makes your app ask the user to sign in, then the call runs. Read one or more published site pages in full, including the markdown body. Use after pages-list or pages-search to read the pages you picked, or directly when you already know a page's path or link. Parameters: pages (required, 1 to 5 entries). Each entry is a page id from a list or search result (a UUID), a slug starting with / such as "/about", or a full URL to a page on the site, which is reduced to its path. A slug the page used to have still finds it, at its current slug. Returns pages[], one per entry in the order given, of { requested, found, page }. page is { id, slug, title, description, keywords, ogImage, updatedAt, markdown, truncated, totalCharacters } or null when no published page answers to the entry; null is a normal result, not an error. markdown is the body without its frontmatter, cut to 20000 characters, with truncated true and totalCharacters set when it was cut. Pages are TronRelic's admin-written site pages (guides, explainers, policies, announcements) served at paths such as /about. These tools return only published pages exactly as visitors see them; drafts and edits waiting for review are never returned. Blog posts are separate and are not pages. Read-only; never changes a page.
Show parametersHide parameters
pagesarrayrequired1 to 5 pages to read, by id, slug, or URL.
pages-list2 paramsNeeds a free TronRelic account: calling it makes your app ask the user to sign in, then the call runs. List the published site pages, most recently changed first, as short summaries without the body. Use to see which pages exist or to browse them; use pages-search instead to find pages about a topic. Parameters: page (optional, 1-based, default 1); limit (optional, default 20, at most 50). Returns total (every published page), page, limit, hasMore, and pages[] of { id, slug, title, description, keywords, updatedAt, excerpt }, where excerpt is a short plain-text opening of the body. Pass an id or slug to pages-get to read a page in full. Pages are TronRelic's admin-written site pages (guides, explainers, policies, announcements) served at paths such as /about. These tools return only published pages exactly as visitors see them; drafts and edits waiting for review are never returned. Blog posts are separate and are not pages. Read-only; never changes a page.
Show parametersHide parameters
pageinteger1-based page number. Default 1.limitintegerPages per call. Default 20, at most 50.
pages-search3 paramsNeeds a free TronRelic account: calling it makes your app ask the user to sign in, then the call runs. Search the published site pages for a text, most recently changed first, as short summaries without the body. The query is matched case-insensitively as a literal substring of each page's title, slug, description, keywords, and body. It is not a boolean or fuzzy search, so use a distinctive word or short phrase such as "energy rental", not a whole question. Use to find pages about a topic; use pages-list to browse everything. Parameters: query (required, 1 to 100 characters); page (optional, 1-based, default 1); limit (optional, default 20, at most 50). Returns query, total (every match), page, limit, hasMore, and pages[] of { id, slug, title, description, keywords, updatedAt, excerpt }. No matches returns an empty list, not an error. Pass an id or slug to pages-get to read a page in full. Pages are TronRelic's admin-written site pages (guides, explainers, policies, announcements) served at paths such as /about. These tools return only published pages exactly as visitors see them; drafts and edits waiting for review are never returned. Blog posts are separate and are not pages. Read-only; never changes a page.
Show parametersHide parameters
querystringrequiredText to find (1 to 100 characters), matched case-insensitively as a literal substring.pageinteger1-based page number. Default 1.limitintegerPages per call. Default 20, at most 50.
search-blog-posts3 paramsNeeds a free TronRelic account: calling it makes your app ask the user to sign in, then the call runs. Search PUBLISHED blog posts by free text, newest first, as lightweight summaries (no body). The query is a case-insensitive literal substring matched against each post's title, tags, and markdown body — not a boolean or fuzzy query, so search a distinctive word or phrase (e.g. "energy rental"), not a full question. Use when looking for posts about a specific topic; use list-blog-posts instead to browse everything or select by date. Read-only; never mutates. Parameters: "query" (required, 1-200 characters), "page" (optional, 1-based, default 1), "limit" (optional, default 20, clamped to 50). Returns { success, posts: [{ id, slug, title, tags, excerpt, publishedAt }], total, page, limit } — "total" counts every match for paging, and each "id" can be passed to get-blog-post to read the full markdown body. Only published posts are ever returned; zero matches returns an empty list (not an error).
Show parametersHide parameters
querystringrequiredThe text to find (required, 1-200 characters); matched case-insensitively as a literal substring of the title, tags, or body.pageinteger1-based page number (optional, default 1). Values below 1 are treated as 1.limitintegerPage size (optional, default 20); clamped to the range 1-50.
Checked by Serverdex with a plain initialize + tools/list call to tronrelic.com/mcp, no credentials, about once a day. A failed check is never a removal.
On GitHub
read Nov 16, 2026- Stars
- 1
- Forks
- 0
- Last push
- Nov 16, 2026
- License
- Other
TypeScriptcyrptotron-protocol
From the README
TronRelic Open-source TRON blockchain analytics platform with real-time monitoring, whale tracking, and extensible plugins. Quick Start URLs: Frontend http://localhost:3000 | API http://localhost:4000 | Admin http://localhost:3000/system Stop: Press Ctrl+C to stop dev servers. Run npm run stop to stop database containers. Requirements: Node.js 24+, Docker, TronGrid API keys License AGPL-3.0-or-later with a plugin exception, which means third-party plugins may use any license. See LICENSE for details. Documentation Read the linked documentation before working on any topic below. These documents record the architectural decisions, required patterns, and constraints the project works to. Skipping them leads to rejected code, security problems, and wasted effort. Core Backend (System Architecture) Everything under src/backend/: modules, blockchain sync, the scheduler, database access, the system API, and the admin dashboard. For the frontend, see Frontend Development below. Plugin Development Frontend Development TRON Blockchain Read the relevant documents before writing code. These patterns come from problems the project has already run into, so following them avoids repeating those problems.
Read the full README on GitHub →Remotes
- streamable-http
https://tronrelic.com/mcp
Alternatives to TronRelic
Best Food, Home & Lifestyle servers →The most-starred Food, Home & Lifestyle servers in the index, with their live-check result.
| Server | Stars | Last push | Live check |
|---|---|---|---|
| ShipSwift | 3,278 | Nov 2026 | Working |
| Anime Garden | 1,408 | Nov 2026 | Working |
| StyleKit | 876 | Nov 2026 | Working |
| HEARTH | 364 | Nov 2026 | Local / not checked |
| three.ws Home | 281 | Nov 2026 | Local / not checked |
TronRelic: questions people ask
- Is TronRelic a remote or a local MCP server?
- According to its entry in the official MCP registry, TronRelic ships as a hosted endpoint (streamable-http) that your client connects to by URL.
- Does TronRelic need an API key?
- Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 21, 2026. Individual tools may still ask for a key when called.
- Is TronRelic still maintained?
- Active: the repository's last commit 4 days ago. Last push Nov 16, 2026, 1 GitHub stars, Other licence. Read from GitHub on Nov 16, 2026.
- What tools does TronRelic expose?
- 8 tools as listed by the server itself during the live check, including resource-markets-get-activity, resource-markets-get-prices, get-blog-post, list-blog-posts, pages-get. The full list with parameters is in the Live check section above.
- How do I add TronRelic to Claude, Cursor or VS Code?
- Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
More Food, Home & Lifestyle servers
Browse all Food, Home & Lifestyle →Tu Lugar
JanKratochvil1
Search and manage Paraguay & LatAm real estate from any AI assistant.
Uncle Rental
OchaNomitsu
Search Hong Kong uncles and create a checkout link for a companionship booking.
Voya Homes public vacation-home search
r2nrswkypf-cmyk
Read-only Voya Homes search for date-bound availability, prices and property details.
Wedding Seat
naturalnet
Anonymous, no-login wedding planning: create a project, add guests, auto-generate a seating plan.
Site
joeetdev
Wedding Cost Checker: the site's own MCP server — dataset, enquiry (enquiry = a human handoff,...
Wedyesday — wedding planning
vritul
Plan a wedding in chat: search vendors, get regional costs, build a checklist and budget.
Add the badge to your site
Show visitors that TronRelic is listed here — it’s also the link we check for a free listing.
HTML — for your website
<a href="https://serverdex.io/server/com-tronrelic-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="TronRelic — listed on Serverdex" width="123" height="40" loading="lazy"></a>Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.
Markdown — for your README
[](https://serverdex.io/server/com-tronrelic-mcp?utm_source=badge)Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.
Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).