All plugins

evm-token-inspector

Inspect any EVM token contract before interacting with it: name, symbol, decimals, total supply, owner/renounced status, EIP-1967 proxy detection, and the DEX V2 pair plus liquidity reserves — one tool, evm_token_check, on BSC, Ethereum, Base and Arbitrum. Read-only; public JSON-RPC only, no API key, no signing, no credentials. Disclosure — read-only: the evm_token_check tool sends the contract address in standard JSON-RPC read calls (via the system curl binary, falling back to Python urllib) to fixed public RPC endpoints (bsc-dataseed.binance.org, bsc.publicnode.com, rpc-bsc.48.club, bsc-dataseed1.ninicoin.io, ethereum.publicnode.com, eth.drpc.org, eth-mainnet.public.blastapi.io, mainnet.base.org, base.publicnode.com, arb1.arbitrum.io, arbitrum.publicnode.com); no keys, no signing, no transactions. It does not detect honeypots or hidden taxes; it reports on-chain facts (owner, proxy, pair, reserves) for the user to judge, and is not financial advice.

sawi57003-opsToolsv1.0.0Updated 2 hours ago

About

Inspect any EVM token contract before interacting with it: name, symbol, decimals, total supply, owner/renounced status, EIP-1967 proxy detection, and the DEX V2 pair plus liquidity reserves — one tool, evm_token_check, on BSC, Ethereum, Base and Arbitrum. Read-only; public JSON-RPC only, no API key, no signing, no credentials. Disclosure — read-only: the evm_token_check tool sends the contract address in standard JSON-RPC read calls (via the system curl binary, falling back to Python urllib) to fixed public RPC endpoints (bsc-dataseed.binance.org, bsc.publicnode.com, rpc-bsc.48.club, bsc-dataseed1.ninicoin.io, ethereum.publicnode.com, eth.drpc.org, eth-mainnet.public.blastapi.io, mainnet.base.org, base.publicnode.com, arb1.arbitrum.io, arbitrum.publicnode.com); no keys, no signing, no transactions. It does not detect honeypots or hidden taxes; it reports on-chain facts (owner, proxy, pair, reserves) for the user to judge, and is not financial advice.

evm-token-inspector

A Hermes plugin that inspects an EVM token contract before you interact
with it
. One tool, evm_token_check, reads the contract over a public
JSON-RPC endpoint and reports:

  • name, symbol, decimals, total supply
  • owner() status — the owner address, renounced when it is the zero
    address, or n/a when the contract has no owner() at all
  • whether it is an EIP-1967 proxy (and the implementation address)
  • the DEX V2 pair vs the chain's wrapped native token, plus both
    reserves, so you can see whether real liquidity exists (or the pair is
    empty / missing)

Chains: BSC, Ethereum, Base, Arbitrum.

Why this exists

Before a swap, a mint or an approval, the two questions that matter are
"what is this contract?" and "is there real liquidity behind it?". This
plugin answers both with on-chain reads, in one tool call, without an API
key and without signing anything.

How it works

All reads are plain eth_call / eth_getCode / eth_getStorageAt against
public RPCs:

| Chain | RPC | DEX |
|---|---|---|
| BSC | bsc-dataseed, publicnode, 48.club, ninicoin (fallback order) | PancakeSwap V2 |
| Ethereum | publicnode, drpc.org, blastapi.io | Uniswap V2 |
| Base | mainnet.base.org, publicnode | Uniswap V2 |
| Arbitrum | arb1.arbitrum.io, publicnode | Uniswap V2 |

Transport: the plugin POSTs through the curl binary when it is present
(its TLS handshake is accepted by public RPCs that silently drop Python's
stdlib TLS fingerprint), falling back to stdlib urllib. The curl call
uses an argument list with no shell, and the URL/body are built from fixed
config plus a validated 0x address, so there is no injection surface.

No writes, no signing, no API keys, no credentials. The plugin never reads
any file or secret — the only input is the contract address (and the chain).

Install

hermes plugins install evm-token-inspector

Or from source:

git clone https://github.com/sawi57003-ops/evm-token-inspector
hermes plugins validate ./evm-token-inspector --install-deps

Example

Ask Hermes:

Check token 0x... on BSC — is it safe to look at?

The agent calls evm_token_check and gets back a JSON report like:

{
  "success": true,
  "token": {
    "chain": "bsc",
    "address": "0x...",
    "name": "Example Token",
    "symbol": "EXM",
    "decimals": 18,
    "total_supply": "1000000000",
    "owner": "0x0000000000000000000000000000000000000000",
    "owner_renounced": true,
    "is_proxy": false,
    "pair": "0x...",
    "has_liquidity_pair": true,
    "reserves": { "token": "500000000000000000000000", "wrapped_native": "1200000000000000000" },
    "liquidity_empty": false
  }
}

Disclosure

  • Read-only. It makes HTTPS calls to the public RPCs listed above and to
    nothing else.
  • It does not detect honeypots, hidden taxes or malicious logic — it
    reports the facts (owner, proxy, pair, reserves) so the agent and the user
    can judge. It is not financial advice.
  • No telemetry, no background processes, no stored credentials.

License

MIT. See LICENSE.

README from the reviewed commit abe6d9b; it updates when the author re-pins.

More by sawi57003-ops

2 plugins by sawi57003-ops in the catalog.

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section