Check before you sign: tx and signature safety

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

See what a transaction or signature will do before your agent signs it, plus address and link risk.

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

VerifiedSTDIODesktop onlyFinanceSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant preview what a crypto transaction or signature will do, and check address and link risk, before anything is signed.

What you can do
  • Preview a transaction or signature to see what it will do before signing
  • Check the risk of an address
  • Check the risk of a link
  • Surface payment invoices when the free trial runs out so the agent can pay and retry
When to use it
Useful when an agent handles crypto transactions or signatures and you want a safety check on the transaction, address or link before approving or signing anything.
Requirements
Runs as a local process on the user's machine via a container image over stdio; desktop only, not web-executable. No authentication is declared. An optional secret, CWX_X_PAYMENT, can supply an x402 X-PAYMENT header; without it the server uses each service's free trial of 3 calls per day.
Before you install
Without CWX_X_PAYMENT the server falls back to a 3-calls-per-day free trial and then returns a 402 invoice to the agent, which may pay it through its own x402 client, so spending can occur. Transaction and address data is sent to the provider's service for analysis. Treat the payment secret as sensitive.

Installation

In SourceWeft

  1. Open Check before you sign: tx and signature safety 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