PayPerScreen

io.github.TonytheTiger22Published by GitHub account TonytheTiger22v0.1.3Updated Oct 29, 2026

Sanctions, crypto wallet, email and IP screening for agents. Pay per check in USDC via x402.

VerifiedSTDIODesktop onlyFinanceSecurity & Monitoring

Overview

AI-generated overview

PayPerScreen gives an AI assistant sanctions, crypto wallet, email and IP screening checks, paid per check in USDC via x402.

What you can do
  • Run screening checks on sanctions lists, crypto wallets, email addresses and IP addresses.
  • Pay 2 cents per check in USDC from a configured wallet, with free tools available without a key.
  • Cap total session spending in USD through a configured limit.
When to use it
Useful when an assistant needs quick risk or compliance screening of a wallet address, email, IP or sanctions match, and you are willing to pay per check in USDC from a funded wallet.
Requirements
Runs as a local npm package over stdio on a desktop machine. Needs a wallet private key in PAYPERSCREEN_PRIVATE_KEY holding a few dollars of USDC for paid checks; free tools work without it. Optional settings: PAYPERSCREEN_MAX_SPEND (default 1.00 USD per session) and PAYPERSCREEN_NETWORK (base, polygon or arbitrum). No declared authentication beyond the key.
Before you install
The server asks for a wallet private key in PAYPERSCREEN_PRIVATE_KEY, which controls funds; use a dedicated wallet holding only a small USDC balance. Checks cost 2 cents each in USDC, so real money is spent, bounded by PAYPERSCREEN_MAX_SPEND. Screening queries about wallets, emails and IPs are sent to a third-party service.

Installation

In SourceWeft

  1. Open PayPerScreen 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 has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.1.3LatestOct 29, 2026
  2. v0.1.1Oct 14, 2026

Score

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

    Declare a license in the repository or the registry entry.