Server data from the Official MCP Registry
TRON energy rental prices and market activity from TronRelic. Free account unlocks more tools.
About
TRON energy rental prices and market activity from TronRelic. Free account unlocks more tools.
Remote endpoints: streamable-http: https://tronrelic.com/mcp
Security Report
TronRelic is a TRON blockchain analytics platform whose MCP exposure service gates each AI tool behind per-group admin grants, fingerprints capabilities, enforces safety floors, IP allowlists, and per-caller limits. The reviewed code is well structured with no evidence of exfiltration, command execution, or hardcoded secrets; the main caveat is that only a truncated excerpt of the server was provided, so the rest of the MCP endpoint, tool implementations, and dependency-level behavior could not be verified. Permissions like network_http and database access are consistent with a developer analytics tool. Supply chain analysis found 9 known vulnerabilities in dependencies (0 critical, 2 high severity).
6 files analyzed · 12 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
How to Connect
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"com-tronrelic-mcp": {
"url": "https://tronrelic.com/mcp"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
TronRelic
Open-source TRON blockchain analytics platform with real-time monitoring, whale tracking, and extensible plugins.
Quick Start
cp .env.example .env
openssl rand -hex 32 # Add to ADMIN_API_TOKEN in .env
# Add TronGrid API keys to .env (get free keys at https://www.trongrid.io/)
npm install
npm run dev
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
| Document | Purpose |
|---|---|
| Documentation Standards | Writing style, document structure, and cross-referencing |
| Environment Variables | Configuration options for the backend and frontend, and the non-obvious behaviors behind them |
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.
| Document | Purpose |
|---|---|
| System Overview | Blockchain sync, the scheduler, observers, and metrics |
| Backend Modules | The IModule interface, the two-phase init and run lifecycle, and dependency injection |
| Database Access | The IDatabaseService abstraction and its three levels of access |
| System API Reference | The 16-plus admin endpoints and how they authenticate |
| Blockchain Sync | Retrieving blocks, enriching transactions, and notifying observers |
| System Dashboard | The /system interface for job control and monitoring |
| Database Migrations | Evolving the schema, with transaction support |
| Logging System | Pino, persistence to MongoDB, and querying past logs |
| AI Tool Standard | The tool contract, capability classes, and the accountability and security rules for tools an AI model can invoke |
| Menu Module | Managing navigation and letting plugins contribute entries |
| Pages Module | The markdown content management system and file uploads |
| Identity Module | Better Auth, user groups, the wallet store, and the account directory |
| Localization Module | Languages, per-route publishing, stored translations, and the [lang] route folder |
| Traffic Module | ClickHouse traffic_events analytics, the tid and ref cookies, and Google Search Console data |
| Consent Module | The cookie banner for the EEA, the UK, and Switzerland, the rule that gates the analytics cookie, and the Google Ads tag |
| Runtime Configuration | Serving many domains from one Docker image, and how SITE_URL works |
| Scheduler Operations | Managing jobs, cron schedules, and troubleshooting |
| Testing Framework | Vitest, Mongoose mocks, and keeping tests isolated |
Plugin Development
| Document | Purpose |
|---|---|
| Plugin Overview | The five lifecycle states, package structure, and what a plugin can extend |
| API Registration | REST routes, middleware, and admin endpoints |
| Blockchain Observers | Processing transactions and subscribing to contract types |
| Frontend Context | The API client, WebSocket client, toasts, and modals a plugin receives |
| Page Registration | Routes, dynamic segments, and server-side rendering |
| Plugin Architecture | The loader, manifests, and how failures stay isolated |
| WebSocket Subscriptions | Real-time events, rooms, and namespacing by plugin id |
| Widget Zones | Injecting plugin UI into core pages |
Frontend Development
| Document | Purpose |
|---|---|
| Frontend Overview | Next.js 14, module organization, and the SSR + Live Updates pattern |
| Frontend Architecture | Directory structure, and choosing between modules and features |
| React Components | Server and client components, hooks, and context |
| UI System | Design tokens, SCSS Modules, and layout components |
| SCSS Modules | CSS variables, naming conventions, and styling a component |
| Responsive Design | Container queries and breakpoints |
| Icons and Feedback | Lucide icons, animations, and feedback for state changes |
| Accessibility | Semantic HTML, ARIA labels, and plugin styling rules |
| SSR Hydration | Preventing hydration errors, and the ClientTime component |
| Design Tokens | Primitives, semantic tokens, and theming |
| Theme System | Admin themes, CSS overrides, and injection during server rendering |
TRON Blockchain
| Document | Purpose |
|---|---|
| TRON Overview | The energy system, transactions, and chain parameters |
| Chain Parameters | The parameter service, unit conversions, and caching |
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.
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Rea
Freeby Morluto · Developer Tools
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Paperclip
Freeby Paperclipai · Developer Tools
Trending hip-hop artist momentum scores across four cultural dimensions.
Scrapling
Freeby D4Vinci · Developer Tools
Web scraping with stealth HTTP, real browsers, and Cloudflare bypass. CSS selectors supported.
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
