# Honeycheck (npm · honeycheck-mcp)

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

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `honeycheck-mcp`: 65/100 (this document), [markdown](https://verifymcp.io/servers/xyz-honeycheck-honeycheck-mcp/honeycheck-mcp.md), [page](https://verifymcp.io/servers/xyz-honeycheck-honeycheck-mcp/honeycheck-mcp)

## Channel facts

- Registry: `npm`
- Package: `honeycheck-mcp`
- Version: `1.0.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 32 of 114 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 470 tokens (~78/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

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

### Claude

```bash
claude mcp add xyz-honeycheck-honeycheck-mcp -- npx -y honeycheck-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "xyz-honeycheck-honeycheck-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "honeycheck-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "xyz-honeycheck-honeycheck-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "honeycheck-mcp"
      ]
    }
  }
}
```

### Codex

```bash
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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xyz-honeycheck-honeycheck-mcp --command npx --arg -y --arg honeycheck-mcp
```

### Hermes

```yaml
mcp_servers:
  xyz-honeycheck-honeycheck-mcp:
    command: "npx"
    args: ["-y", "honeycheck-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "xyz-honeycheck-honeycheck-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "honeycheck-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add xyz-honeycheck-honeycheck-mcp -t stdio -c npx -a -y honeycheck-mcp
```

### Other

```json
{
  "mcpServers": {
    "xyz-honeycheck-honeycheck-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "honeycheck-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 65)

First indexed and scored.

## MCP tools (6)

### `check_token` (~124 tokens)

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.

Input parameters:

- `token` (string, required): The token contract address on Arc: 0x and forty hex characters.

### `hook_track_record` (~77 tokens)

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.

Input parameters:

- `limit` (integer): How many hooks, busiest first. Default 15.

### `recent_traps` (~42 tokens)

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

Input parameters:

- `limit` (integer): How many. Default 20.

### `new_launches` (~77 tokens)

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.

Input parameters:

- `limit` (integer): How many, newest first. Default 25.

### `liquidity_pulls` (~52 tokens)

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

Input parameters:

- `limit` (integer): How many, newest first. Default 25.

### `verdict_changes` (~98 tokens)

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.

Input parameters:

- `limit` (integer): How many, newest first. Default 30.
- `since` (string): An ISO timestamp, usually the builtAt of your last answer. Only what changed after it comes back.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/xyz-honeycheck-honeycheck-mcp/honeycheck-mcp#diagnostics

## Score history

- 2026-09-20: 65
- 2026-09-19: 65

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

## Links

- npm package: https://www.npmjs.com/package/honeycheck-mcp
- Socket report: https://socket.dev/npm/package/honeycheck-mcp
- Website: https://honeycheck.xyz/
- Changelog RSS feed: https://verifymcp.io/servers/xyz-honeycheck-honeycheck-mcp/honeycheck-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/xyz-honeycheck-honeycheck-mcp/honeycheck-mcp.json
- HTML version of this page: https://verifymcp.io/servers/xyz-honeycheck-honeycheck-mcp/honeycheck-mcp