Honeycheck

xyz.honeycheckPublished by honeycheck.xyzv1.0.1Updated Oct 24, 2026

Before buying a token on Arc, test whether it can be sold back. Free, or 1-5c a call over x402.

VerifiedSTDIODesktop onlyFinanceSecurity & Monitoring

Overview

AI-generated overview

Honeycheck lets an assistant test whether a token on Arc can be sold back before buying it, with free checks or paid calls over x402.

What you can do
  • Check whether a token on Arc can be sold back before buying it.
  • Run free checks that need no wallet or payment.
  • Make paid calls costing roughly 1 to 5 cents each, paid over x402 from a funded Circle Gateway wallet.
  • Cap the cost of a single call so the tool refuses to pay above a set amount.
When to use it
Useful when an assistant is evaluating a token on Arc and you want a sell-back or exit-liquidity check before committing to a purchase, rather than relying on price data alone.
Requirements
Runs locally as an npm package over stdio on a desktop machine. Free tools need no setup. Paid tools need a funded Circle Gateway wallet on Arc, supplied through the HONEYCHECK_WALLET_KEY environment variable, and optionally HONEYCHECK_MAX_USDC_PER_CALL to cap the per-call price (default 0.05).
Before you install
Paid tools spend real funds: each call costs about 1 to 5 cents in USDC, so set HONEYCHECK_MAX_USDC_PER_CALL deliberately. The server asks for a wallet private key via HONEYCHECK_WALLET_KEY; use a dedicated, minimally funded wallet rather than a main one. A sell-back check is a pre-trade signal, not a guarantee of liquidity or price.

Installation

In SourceWeft

  1. Open Honeycheck 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.

Tools

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

Version history

1
  1. v1.0.1LatestSep 20, 2026

Score

15% 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

    Publish an icon in the registry entry.

  • 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.