Token safety: honeypot and rug pull check

io.github.CyberPunk11147Published by GitHub account CyberPunk11147v1.6.0Updated Nov 6, 2026

Stops your agent buying a coin it cannot sell: honeypot test, rug checks and an A-F risk grade.

The publisher's own server: check.tattoo: tattoo size and placement guide

VerifiedSTDIODesktop onlyFinanceSecurity & Monitoring

Overview

AI-generated overview

Checks a token for honeypot and rug-pull risk and returns an A–F grade, so an assistant can vet coins before buying.

What you can do
  • Run honeypot tests on a token to see whether it can be sold after buying.
  • Check for rug-pull risk signals and receive an A–F risk grade.
  • Query a hosted oracle service over stdio, with an optional base URL override.
  • Surface a 402 payment invoice to the agent when no payment header is supplied.
When to use it
Useful when an assistant or trading agent is about to buy or recommend a token and needs a quick safety check on whether it can be sold and how risky it looks.
Requirements
Runs as a local process from an OCI image (ghcr.io/cyberpunk11147/cyberwarex-defi-oracle:1.6.0) over stdio, desktop only. Needs network access to the hosted oracle at oracle.cyberwarex.com, or a URL set in DSO_BASE_URL. No account or authentication is declared.
Before you install
The service is paid: without the optional DSO_X_PAYMENT header the server returns a 402 invoice, and the agent may pay it through its own x402 client, so spending can occur. The payment credential is a secret. Token risk grades come from a third-party oracle and are not a guarantee; the server sends the tokens you check to that remote service.

Installation

In SourceWeft

  1. Open Token safety: honeypot and rug pull check 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 started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

6
  1. v1.6.0LatestNov 6, 2026
  2. v1.5.0Oct 10, 2026
  3. v1.4.0Oct 9, 2026
  4. v1.3.0Oct 9, 2026
  5. v1.2.1Oct 7, 2026
  6. v1.1.0Sep 16, 2026

Score

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

Other Check integrations