Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Honeycheck

NPM · HONEYCHECK-MCP · SCANNED SEP 20

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

Available components

65 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 32 of 114 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 470 tokens (~78/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the Honeycheck MCP server?

Honeycheck runs locally as an npm package, launched with npx -y honeycheck-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · honeycheck-mcp

# add to Claude Code
claude mcp add xyz-honeycheck-honeycheck-mcp -- npx -y honeycheck-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "xyz-honeycheck-honeycheck-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "honeycheck-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "xyz-honeycheck-honeycheck-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "honeycheck-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add xyz-honeycheck-honeycheck-mcp -- npx -y honeycheck-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-honeycheck-honeycheck-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "honeycheck-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add xyz-honeycheck-honeycheck-mcp --command npx --arg -y --arg honeycheck-mcp
# ~/.hermes/config.yaml
mcp_servers:
  xyz-honeycheck-honeycheck-mcp:
    command: "npx"
    args: ["-y", "honeycheck-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "xyz-honeycheck-honeycheck-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "honeycheck-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add xyz-honeycheck-honeycheck-mcp -t stdio -c npx -a -y honeycheck-mcp
// mcp.json
{
  "mcpServers": {
    "xyz-honeycheck-honeycheck-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "honeycheck-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 65

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/honeycheck-mcp@1.0.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 114 packages
Packages resolved 114
Stale 31
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~470 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_token ~124

Before buying a token on Arc (chain 5042), check whether it can be sold back. Simulates a fresh wallet buying the token with USDC and selling it straight back, and returns a verdict (SELLABLE, TAXED, TRAP, BLOCKED, DISPUTED, UNBOUGHT, THIN), what one USDC returns, and the reason. Call this first: a token can trade actively and still be unsellable for a new buyer.

NameTypeReqDescription
tokenstringyesThe token contract address on Arc: 0x and forty hex characters.

No output schema declared.

No examples provided.

hook_track_record ~77

The track record of every Uniswap v4 launch hook on Arc: how many tokens each has launched and what those tokens do to a fresh buyer (sellable, taxed, trap). Use it to judge a launch surface before trusting a token from it.

NameTypeReqDescription
limitintegerHow many hooks, busiest first. Default 15.

No output schema declared.

No examples provided.

liquidity_pulls ~52

Tokens on Arc whose liquidity was pulled in the last day. Nothing can be bought and whoever holds them cannot sell. Paid per call.

NameTypeReqDescription
limitintegerHow many, newest first. Default 25.

No output schema declared.

No examples provided.

new_launches ~77

Every token that started trading against USDC on Arc in the last hour, with the sell test already run on it. Read off the chain every two minutes rather than from listing sites, so it holds launches no listing site has seen yet. Paid per call.

NameTypeReqDescription
limitintegerHow many, newest first. Default 25.

No output schema declared.

No examples provided.

recent_traps ~42

The most recent tokens on Arc that a fresh wallet cannot sell back, with the reason for each.

NameTypeReqDescription
limitintegerHow many. Default 20.

No output schema declared.

No examples provided.

verdict_changes ~98

What changed on Arc in the last two days: tokens checked for the first time, and tokens whose verdict is no longer what it was. Poll this to stay current instead of rechecking tokens one at a time. Paid per call.

NameTypeReqDescription
limitintegerHow many, newest first. Default 30.
sincestringAn ISO timestamp, usually the builtAt of your last answer. Only what changed after it comes back.

No output schema declared.

No examples provided.

Common questions

What is the Honeycheck MCP server?

Honeycheck is an MCP server listed in the public MCP registry as xyz.honeycheck/honeycheck-mcp. Before buying a token on Arc, test whether it can be sold back. Free, or 1-5c a call over x402. This page covers its npm package (honeycheck-mcp).

Is the Honeycheck MCP server safe to use?

Honeycheck scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Honeycheck MCP server expose?

Honeycheck exposes 6 tools: check_token, hook_track_record, recent_traps, new_launches, liquidity_pulls, verdict_changes. Their descriptions and schemas cost roughly 470 tokens of context every time the server is loaded.

Is the Honeycheck MCP server still maintained?

Honeycheck is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Honeycheck MCP server under?

Honeycheck declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.