TronRelic MCP server
com.tronrelic/mcptronrelic.comstreamable-httpv1.2.1Scanned
TRON energy rental prices and market activity from TronRelic. Free account unlocks more tools.
8 tools: 8 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 TronRelic MCP server can do
The TronRelic MCP server is published by tronrelic.com, a domain the MCP Registry verified. It has 8 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
3 tools bring in text other people can write (get-blog-post, list-blog-posts and search-blog-posts).
The fixed checks matched 2 findings (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 16, 2026, version 1.2.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.
8 tools
Only reads 8Show 8 read-only tools
get-blog-postNeeds a free TronRelic account: calling it makes your app ask the user to sign in, then the call runs.Reads text others writeNo findings
Why it is in this group
- The name "get-blog-post" says "get": a word for reading.
What it can reach
- untrusted-inputThe name "get-blog-post" says "get" and "post": it reads posts, which other people can write.
Description, as the server wrote it Needs 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.
Annotations the server declares
- title: Read a blog post
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list-blog-postsNeeds a free TronRelic account: calling it makes your app ask the user to sign in, then the call runs.Reads text others writeNo findings
Why it is in this group
- The name "list-blog-posts" says "list": a word for reading.
What it can reach
- untrusted-inputThe name "list-blog-posts" says "list" and "post": it reads posts, which other people can write.
Description, as the server wrote it Needs 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.
Annotations the server declares
- title: List blog posts
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
pages-getNeeds a free TronRelic account: calling it makes your app ask the user to sign in, then the call runs.No findings
Why it is in this group
- The name "pages-get" says "get": a word for reading.
Description, as the server wrote it Needs 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.
Annotations the server declares
- title: Read site pages
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
pages-listNeeds a free TronRelic account: calling it makes your app ask the user to sign in, then the call runs.No findings
Why it is in this group
- The name "pages-list" says "list": a word for reading.
Description, as the server wrote it Needs 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.
Annotations the server declares
- title: List site pages
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
pages-searchNeeds a free TronRelic account: calling it makes your app ask the user to sign in, then the call runs.No findings
Why it is in this group
- The name "pages-search" says "search": a word for reading.
Description, as the server wrote it Needs 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.
Annotations the server declares
- title: Search site pages
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
resource-markets-get-activityReport 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 …1 finding
Why it is in this group
- The name "resource-markets-get-activity" says "get": a word for reading.
Findings
- Info
The description is 4,196 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...mark). An unknown slug returns { success: false, error } listing the known slugs."
Description, as the server wrote it Report 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, summary, daily }] }. 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. "summary" is null for a market with no rental figures, and otherwise { windowDays, firstObservedAt, lastObservedAt, paymentTRX, energyDelivered, blendedSunPerEnergyPerDay, blendedPriceDay, sampledRentals, sampledServed, sampledUnserved, sampleCapped, medianFulfillmentMs, participantCount, topParticipantShare }. "paymentTRX" and "energyDelivered" in the summary cover the whole "windowDays" and are exact. The "sampled" counts and the other per-rental figures come from at most the newest 5000 rentals in that window; "sampleCapped" true means the sample did not reach back through the whole window, so those counts are not totals. "lastObservedAt" is the chain time of the newest rental activity recorded; a time hours before "asOf" on a normally busy market means it has gone quiet or its examiner has stopped. "daily" is [{ day (YYYY-MM-DD, UTC), paymentTRX, energyDelivered, sunPerEnergyPerDay, rentalCount, deliveredRentalCount }], oldest first, with no row for a day nothing was recorded. "rentalCount" is every rental that started that day, delivered or not, exact and not sampled; "deliveredRentalCount" is how many of those have a delivery, so the difference is rentals paid for but not (yet) delivered; resource-markets-get-errata lists them. Both leave out records a market's own figures treat as internal, such as CatFee paying itself or SoHu's collector loans, and both are absent from a row when the count could not be taken. For SoHu and Tronex a rental is a delivery, so the two counts are equal. EnergyFather's summary and "daily" rows cover only the deliveries paid in TRX at its payment address, a small share of its sales; its API buyers pay from prepaid balances the chain does not show, so read its full delivery figures from "reports" with its slug. Today's row is partial, covering only up to the last time the figures were stored, normally less than an hour ago. "paymentTRX" counts what the examiner recorded as renter payments; how a market records prepaid-balance top-ups or unserved payments differs by market, so compare a market's days with each other rather than one market's TRX with another's. With "slug", returns { success, asOf, days, pageUrl, market } with the same fields plus "priceBuckets" (the price paid by rental length: bucket, label, rentalCount, median, min and max SUN per energy per day), "p90FulfillmentMs", "usdtTransferEnergy" (energy one USDT transfer costs, to convert SUN per energy into TRX per transfer), "reports" (figures from other analyses of the market), "advertisedPrice" (the cheapest and dearest advertised price per USDT transfer at the newest capture, or null), and "completeBefore" (the repair watermark). An unknown slug returns { success: false, error } listing the known slugs.
Annotations the server declares
- title: Show energy market activity
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
resource-markets-get-pricesReport 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…1 finding
Why it is in this group
- The name "resource-markets-get-prices" says "get": a word for reading.
Findings
- Info
The description is 7,057 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...iling. An unknown slug returns { success: false, error } listing the known slugs."
Description, as the server wrote it Report 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 market entry carries its own "pageUrl", its TronRelic page with its rate card and prices paid; when you cite a price, link the matching page so the reader can check it there. Either is null when the site address is unknown. Without "slug", returns { success, asOf, order, pageUrl, current, outdated, unpriced, history? }. "current" is the markets priced in the newest capture run, cheapest first: those whose rate card can price the order come first by total cost, then the rest by lowest advertised rate. Markets equal to the SUN are tied, and their order is a daily rotation by the capture's UTC day of the month, not a price difference: report them as tied. "outdated" is markets missing from the newest capture run, so their capture is older than the freshest; their prices stopped updating and they are not ranked. Each is { slug, displayName, pageUrl, capturedAt, cheapest, dearest, usdtTransferEnergy, hasRateCard, quote, orderbook, supplyYield }. "cheapest" and "dearest" are the market's advertised extremes as { trxPerTransfer, transfersRequired, durationMinutes, discountPercent }; "transfersRequired" above 1 means the price needs an order that large. "quote" is the order priced on the market's best tier as { totalTrx, trxPerTransfer, energy, durationMinutes, purchases, raisedToMinimum } or null when the market has no rate card or no tier takes the order. A period of a day or less is priced as one burst; a longer one spreads the transfers evenly and renews a tier shorter than the period, once a day for a batched tier shorter than a day. When quoting a batched order on a tier shorter than a day, say that each day's transfers must be sent inside that one rental. "purchases" counts the rentals bought, including a fixed-size package bought several times; "energy" is summed across them. Splitting an order across different tiers is not modelled. "orderbook" is { capturedAt, bid?, ask? } with { orderCount, totalEnergy, vwapSun } per side, or null. "supplyYield" is { advertisedBestRatePercent (the highest yearly rate among the market's open programs), openPrograms, witnessedRatePercent (the yearly rate the chain shows it paid), witnessedHolders } or null when the market buys no energy from holders; an advertised rate is the market's claim and the witnessed rate is the evidence. "unpriced" lists markets with no advertised price as { slug, displayName, pageUrl, supplyYield }. "history", present only when "historyDays" was given, is { historyDays, runs, firstRunAt, lastRunAt, markets, unquoted }: "runs" counts the capture runs in the window; each "markets" entry is { slug, displayName, lowest, highest, runsCaptured, runsQuoted, firstCapturedAt, lastCapturedAt }, where "lowest" and "highest" are { capturedAt, quote } for the cheapest and dearest quote of the order in the window (a tie to the SUN goes to the newest run), sorted by the lowest quote's totalTrx, cheapest first; markets whose lowest totalTrx is equal to the SUN are tied, so report them as tied. "firstCapturedAt" and "lastCapturedAt" are the market's own oldest and newest capture in the window, which can be later than "firstRunAt" when its price fetch failed for part of it. "unquoted" lists markets the window captured whose rate card never took the order, as { slug, displayName, runsCaptured }. A market missing from the window entirely had no capture in it. With "slug", returns { success, asOf, order, historyDays, pageUrl, market: { slug, displayName, pageUrl, advertised, supplyYield } }. No link to a market's own site is returned; send readers to "pageUrl", where the market's site is linked. "advertised" is null for a market with no price fetcher, and otherwise { capturedAt, price, rateCard, orderbook, priceHistory, quoteHistory, quote }: "rateCard" is { capturedAt, usdtTransferEnergy, cells (up to 100), cellsTotal } where each cell is { minutes, sun, minBorrow?, maxBorrow?, discountPercent? } and "sun" is the price for the whole rental in SUN per unit of energy with TRON's one-day minim… [1057 more characters not shown]
Annotations the server declares
- title: Compare energy rental prices
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search-blog-postsNeeds a free TronRelic account: calling it makes your app ask the user to sign in, then the call runs.Reads text others writeNo findings
Why it is in this group
- The name "search-blog-posts" says "search": a word for reading.
What it can reach
- untrusted-inputThe name "search-blog-posts" says "search" and "post": it reads posts, which other people can write.
Description, as the server wrote it Needs 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).
Annotations the server declares
- title: Search blog posts
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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 write3
- 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.
Looked at Nov 15, 2026, 13:18 UTC, unchanged since Nov 15, 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
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://tronrelic.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://tronrelic.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- no
- Client ID metadata documents
- yes
Findings
Matches of fixed checks, with the text they matched.
The description is 4,196 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...mark). An unknown slug returns { success: false, error } listing the known slugs."
The description is 7,057 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...iling. An unknown slug returns { success: false, error } listing the known slugs."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools8 changed.~8 changedView diff
- Changed:get-blog-postOnly readstitleannotations
- Changed:list-blog-postsOnly readstitleannotations
- Changed:pages-getOnly readstitleannotations
- Changed:pages-listOnly readstitleannotations
- Changed:pages-searchOnly readstitleannotations
- Changed:resource-markets-get-activityOnly readstitledescriptionannotations
- Changed:resource-markets-get-pricesOnly readstitledescriptionannotations
- Changed:search-blog-postsOnly readstitleannotations
Install
Pinned to version 1.2.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http tronrelic https://tronrelic.com/mcpclaude mcp add --transport http tronrelic https://tronrelic.com/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__tronrelic__resource-markets-get-activity",
"mcp__tronrelic__resource-markets-get-prices",
"mcp__tronrelic__get-blog-post",
"mcp__tronrelic__list-blog-posts",
"mcp__tronrelic__pages-get",
"mcp__tronrelic__pages-list",
"mcp__tronrelic__pages-search",
"mcp__tronrelic__search-blog-posts"
],
"ask": [],
"deny": []
}
}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 tronrelic. Review it before you use it.
Capability tags behind 3 rules
- mcp__tronrelic__get-blog-post untrusted-input
- mcp__tronrelic__list-blog-posts untrusted-input
- mcp__tronrelic__search-blog-posts 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/com.tronrelic/mcp/verify?hash=b02fc2098291f024eadc3a71bf9ce3e7aa74f26deec764cfbc0a795676692e69" | jq -e '.changed == false'Pinned hash b02fc2098291, from Nov 16, 2026, 13:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.tronrelic/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.tronrelic/mcp)Source: MCP Registry · repository. Synced Nov 16, 2026, 13:17 UTC.
TronRelic MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the TronRelic MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, all of which only read, and 2 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the TronRelic MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the TronRelic 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 TronRelic MCP server have?
- 8 tools: 8 read. resource-markets-get-activity, resource-markets-get-prices, get-blog-post, list-blog-posts, pages-get, pages-list, pages-search and search-blog-posts.
Does the TronRelic MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the TronRelic MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the TronRelic MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.