Pellet

io.github.pelletfiPublished by GitHub account pelletfiv0.4.2Updated Oct 24, 2026

Token intelligence on Base. Market data, safety flags, and analysis via x402.

VerifiedSTDIODesktop onlyFinanceSecurity & Monitoring

Overview

AI-generated overview

Pellet gives an assistant token intelligence on Base: market data, safety flags and contract analysis, with paid calls settled via x402 micropayments.

What you can do
Retrieve market data for tokens on Base, including safety flags and analysis results, through the Pellet tools exposed to the assistant. Run free tools without any wallet setup. Run paid tools, such as contract lookup and token analysis, which are charged per call through x402 micropayments.
When to use it
Useful when you want an assistant to check Base token market data, safety signals or contract details while researching or evaluating tokens, and you are comfortable paying small per-call fees for the deeper tools.
Requirements
Runs locally as an npm package via npx on a desktop machine with Node.js. Paid tools require an EVM wallet private key supplied in the EVM_PRIVATE_KEY environment variable; free tools work without it. Network access is needed to reach Pellet's service and settle x402 payments.
Before you install
The server asks for an EVM wallet private key in EVM_PRIVATE_KEY, which controls funds in that wallet; use a dedicated wallet with limited balance. Paid tools spend money per call (contract lookup and token analysis are charged), so costs can accumulate. Token data and analysis are third-party output and should not be treated as financial advice.

Installation

In SourceWeft

  1. Open Pellet in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.4.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.