io.github.ygfalcon/coinlight

None of its 31 tools are described as changing anything. For 31 the reading was uncertain, so no mark is shown.

• new_launcheson 2 other servers

  “Freshest DEX pools on Solana or Base (newest first) with age in minutes, liquidity, 5m/1h volume, buys vs sells and instant red flags (no liquidity, sells far below buys, extreme FDV/liquidity).”

  Publisher declares: read-only yes · open-world yes

  4 inputs

  • chainstring“solana (default) or base.”
  • minLiquidityUsdstring“Minimum pool liquidity in USD.”
  • maxAgeMinutesstring“Only pools younger than this, 1-1440.”
  • paymentstring“Optional x402 PAYMENT-SIGNATURE header value.”
• tx_explainon 3 other servers

  “Paste any Solana signature or Base tx hash and get a one-sentence English explanation (e.g.”

  Publisher declares: read-only yes · open-world yes

  2 inputs, 1 required

  • txstringrequired“Solana signature (base58) or Base 0x tx hash.”
  • paymentstring“Optional x402 PAYMENT-SIGNATURE header value.”
• wallet_portfolioon 10 other servers

  “One call returns a USD-valued portfolio across Solana and Base: SOL, every SPL/Token-2022 holding, Base ETH and USDC, each priced from live DEX liquidity, sorted by value, with dust and unpriced toke…”

  Publisher declares: read-only yes · open-world yes

  3 inputs

  • solanastring“Solana wallet (base58).”
  • evmstring“0x wallet on Base.”
  • paymentstring“Optional x402 PAYMENT-SIGNATURE header value.”
• token_sell_check

  “Pre-trade safety in one keyless call, chain auto-detected.”

  Publisher declares: read-only yes · open-world yes

  3 inputs, 1 required

  • tokenstringrequired“Solana mint (base58) or Base ERC-20 0x address.”
  • sizeUsdstring“Trade size to simulate in USD (Solana), 1-10000.”
  • paymentstring“Optional x402 PAYMENT-SIGNATURE header value.”
• uuidon 18 other servers

  “Generate 1-50 random v4 UUIDs from a cryptographic RNG, e.g.”

  Publisher declares: read-only yes · open-world yes

  2 inputs

  • countstring“How many, 1-50.”
  • paymentstring“Optional x402 PAYMENT-SIGNATURE header value.”
• text_statson 20 other servers

  “Count characters, words, lines, bytes and estimate LLM tokens for a text, so an agent can budget context before sending it.”

  Publisher declares: read-only yes · open-world yes

  2 inputs, 1 required

  • textstringrequired“Text to measure (max 200k chars).”
  • paymentstring“Optional x402 PAYMENT-SIGNATURE header value.”
• time_converton 7 other servers

  “Convert a unix timestamp (seconds or ms) or ISO date into ISO UTC, unix seconds, unix ms and a relative 'x ago' string.”

  Publisher declares: read-only yes · open-world yes

  2 inputs

  • valuestring“Unix seconds, unix ms, or ISO 8601 date.”
  • paymentstring“Optional x402 PAYMENT-SIGNATURE header value.”
• encodeon 3 other servers

  “Convert data between utf8, hex, base64 and base58 (Solana keys and signatures use base58).”

  Publisher declares: read-only yes · open-world yes

  4 inputs, 3 required

  • datastringrequired“Input data.”
  • fromstringrequired“Encoding of data.”
  • tostringrequired“Target encoding.”
  • paymentstring“Optional x402 PAYMENT-SIGNATURE header value.”
• hashon 27 other servers

  “Hash a string with sha256, sha512, sha1 or keccak256 and get hex and base64 output.”

  Publisher declares: read-only yes · open-world yes

  3 inputs, 1 required

  • textstringrequired“Text to hash (UTF-8).”
  • algostring“Algorithm.”
  • paymentstring“Optional x402 PAYMENT-SIGNATURE header value.”
• units_converton 1 other server

  “Exact, bigint-safe conversion between human and atomic units: SOL<->lamports, ETH<->gwei<->wei, USDC<->atomic (6 decimals) or any decimals.”

  Publisher declares: read-only yes · open-world yes

  4 inputs, 2 required

  • amountstringrequired“Amount to convert, e.g.”
  • fromstringrequired“Unit of amount.”
  • decimalsstring“Decimals when from is units/atomic.”
  • paymentstring“Optional x402 PAYMENT-SIGNATURE header value.”
• address_validateon 2 other servers

  “Tell what kind of address a string is (Solana base58 or EVM 0x), whether it is valid, and its EIP-55 checksum form.”

  Publisher declares: read-only yes · open-world yes

  2 inputs, 1 required

  • addressstringrequired“Any address string.”
  • paymentstring“Optional x402 PAYMENT-SIGNATURE header value.”
• base_transactionon 1 other server

  “Look up a Base transaction hash: success or failure, block, from, to, value, gas used and fee paid.”

  Publisher declares: read-only yes · open-world yes

  2 inputs, 1 required

  • hashstringrequired“0x transaction hash.”
  • paymentstring“Optional x402 PAYMENT-SIGNATURE header value.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-24.

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.