A
licenseNot graded
qualityB
maintenanceEnables transparent MCP proxying with a hash-chained effect ledger, classifying agent actions by reversibility, enforcing approval gates, and dry-run previews of sessions.
MIT
@tronhooks/mcp
by LuganBI
Related Servers
Alternatives to @tronhooks/mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables agents to propose policy-gated treasury payments and swaps, check pending human approvals, read transaction receipts, and locally verify their integrity through MCP tools.MIT
TronSave MCP Serverofficial
AlicenseAqualityBmaintenanceRent TRON energy and bandwidth from AI agents: live quotes, orders paid on-chain or from a TronSave balance, auto-buy and auto-sell, extensions and account tools. Hosted with OAuth sign-in; Nile testnet included.453MIT- AlicenseNot gradedqualityCmaintenanceEnables remote MCP servers to request wallet approvals, signatures, and transactions through an approval URL while keeping private keys in the user's browser wallet.27 npmMIT
- AlicenseAqualityDmaintenanceLocal MCP-to-browser signing bridge for EVM, Solana, and Sui, letting agents prepare and simulate transactions while users approve and sign in a browser wallet extension.6MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to use an ERC-4337 smart account with session keys to check wallet status, send ETH or ERC-20 tokens, call allowed contracts, and manage approval requests within on-chain spending limits.3 npm2MIT
TDQS
A4/5.0
Scored across 6 tools
Disambiguation5/5
Each tool targets a clearly distinct action+resource: capabilities retrieval, config validation, listing watches, listing events, and prepare-create vs prepare-delete. The descriptions explicitly delimit scope (e.g. 'does not create', 'never calls DELETE'), so misselection is unlikely.
Naming Consistency5/5
All names follow a consistent snake_case verb-first pattern (get_, validate_, list_, prepare_). The prepare_create_watch / prepare_delete_watch pair is symmetric, reinforcing the pattern.
Tool Count5/5
Six tools is well-scoped for a watch-management server; each tool maps to a distinct step in the lifecycle. Nothing feels redundant or padded.
Completeness4/5
The surface covers capabilities, validation, listing, event reconciliation, and prepare-create/delete (execution deliberately delegated to the console). Minor gaps exist: no read-single-watch/get-watch, no get-event, and no update-watch operation.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues