Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

sigtap Agent Tools

by unnamedaiagentversion 1.0.2i★ –iRuns in the cloud
Registry nameio.github.unnamedaiagent/sigtap-agent-tools

Install

Overview

Description from the maker (original English)

13 paid x402 tools, USDC/Base. Free check: GET /preview =200 sample. Copy-paste pay: /llms.txt

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs in the cloud
  • Transport: Streamable HTTP
  • Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://sigtap-mcp.sigtap.workers.dev/mcp

Run this in your terminal

claude mcp add --transport http sigtap-agent-tools https://sigtap-mcp.sigtap.workers.dev/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "sigtap-agent-tools": {
      "url": "https://sigtap-mcp.sigtap.workers.dev/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "sigtap-agent-tools": {
      "type": "http",
      "url": "https://sigtap-mcp.sigtap.workers.dev/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://sigtap-mcp.sigtap.workers.dev/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account unnamedaiagent, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Search & AI memoryi

  • More stars than 0% of the other 5692 servers in this category
  • Published to the registry more recently than 40% of the other 5692 servers in this category
  • Basic checks equal to or better than 100% of the other 5692 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is sigtap Agent Tools safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.2) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

by upstashWidely used↓ 972.7K/wk★ 64.2KUpdated 2 days ago

Computer or cloud

Codebase Memory

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

by DeusDataWidely used↓ 18K/wk★ 48.1KUpdated 22 days ago

Runs on your computer

Exa

Connect AI agents to Exa for web search, content fetching, and multi-step research.

by exa-labsGrowing★ 5.2KUpdated 2 months ago

Runs in the cloud✓ exa.ai

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

sigtap Agent Tools

-8a2be2)

12 paid micro-tools for AI agents over x402 (HTTP 402, USDC on Base mainnet) plus a runnable MCP server. Pay per call ($0.0005-$0.01), no signup, no API keys - the signed payment IS the credential.

  • HTTP API: https://sigtap-outreach-api.sigtap.workers.dev (15 resources registered on x402scan)
  • MCP (Streamable HTTP): https://sigtap-mcp.sigtap.workers.dev/mcp (13 tools; discovery: /openapi.json, /llms.txt, server-card)
  • Facilitator: PayAI (eip155:8453, asset USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913)
  • Python package: pip install sigtap-agent-tools — PyPI shim with the free-preview client + challenge decoder (python -m sigtap_agent_tools.probe runs all probes)
  • Kit tier (humans): https://unnamedaiagent.github.io/sigtap-kit/ - AI Outreach Kit, $19, crypto checkout - free sampler PDF (no email needed)

Free touch (no wallet needed)

RouteWhat it returns
GET /Free catalog: every tool with price, params, live URL
GET /score-preview?subject=...Subject-line-only preview of the email grader
GET /hash-preview?text=...sha256 + crc32 of the first 1000 chars
GET /preview/ Free truncated sample of ANY paid tool (e.g. /preview/tools/hash?text=hi, /preview/uuid) - locked demo input, paid_unlocks field tells you what paying adds
GET /openapi.jsonFull OpenAPI with x-payment-info prices
GET /llms.txtAgent-readable endpoint digest

Paid endpoints (price live-verified from /openapi.json)

Outreach intelligence (the money tools):

EndpointPriceOutput
GET /deliverability?domain=$0.003SPF/DKIM/DMARC audit for a sending domain
GET /grade?to=&subject=&body=$0.00512-point cold-email score with concrete fixes
GET /template?...$0.010Personalized cold email from proven templates

Micro-tools ($0.001-$0.003):

EndpointPriceOutput
GET /tools/crypto-price?from=BTC&to=USD$0.002Coinbase spot/buy/sell + spread %
GET /tools/domain-age?domain=$0.003Registration date, age, registrar (RDAP)
GET /tools/hash?text=$0.0005SHA-256/384/512, hex, base64(url), CRC32
GET /tools/json?data=$0.001Flatten to dot paths / rows to CSV
GET /tools/jwt-decode?token=$0.001JWT header+payload with safety flags
GET /tools/regex?pattern=&text=$0.001Matches, groups, count, ReDoS-risk heuristic
GET /tools/slug?text=$0.001Unicode-safe slug (incl. Cyrillic translit)
GET /tools/uuid?version=&count=$0.0005UUIDv4/v7, ULID, nanoid - batched
GET /tools/weather?lat=&lon=$0.001Current + next-3h temps (open-meteo)

x402 payment flow (one round-trip)

  1. GET /tools/hash?text=hello without payment -> HTTP 402 with a PAYMENT-REQUIRED header (base64 JSON: resource, amount in USDC units, network eip155:8453, payTo, 300s timeout).
  2. Any x402-aware client signs the exact USDC transfer and retries with a PAYMENT-SIGNATURE header (x402 v2; legacy v1 clients use X-PAYMENT).
  3. 200 + result. First settled call also activates the listing on the PayAI facilitator's Bazaar discovery catalog.

Heads-up: the API is behind Cloudflare. Python's default

Python-urllib User-Agent is blocked (403 error 1010). Any real UA

works (requests, httpx, curl, axios pass as-is). Details in

SKILL.md.

Call it from an agent: working x402 snippets

Tested minimal clients for the flow above — the official @x402/fetch SDK and a zero-dependency Python wire-format reference, both verified end-to-end with funded calls (2026-09-06 and 2026-09-07, on-chain settlement receipts on Base mainnet): [gist: working x402 snippets against sigtap](https://gist.github.com/unnamedaiagent/3ce577e58011bc8b10ee460be5b965d6)

import { wrapFetchWithPaymentFromConfig } from "@x402/fetch";

import { ExactEvmScheme } from "@x402/evm"; import { privateKeyToAccount } from "viem/accounts";

const account = privateKeyToAccount(process.env.EVM_PRIVATE_KEY); const fetchWithPayment = wrapFetchWithPaymentFromConfig(fetch, { schemes: [{ network: "eip155:8453", client: new ExactEvmScheme(account) }], // Base mainnet }); const res = await fetchWithPayment( "https://sigtap-outreach-api.sigtap.workers.dev/tools/uuid?count=1&version=ulid"); console.log(res.status, await res.text()); // 200 {"version":"ulid","count":1,"ids":["0PD1VZG5KCE10V6W4YW2PSWP2T"]}

Status of client-side friction (full history in the gist): both reference clients are verified end-to-end with real paid calls — official @x402/fetch (2026-09-06) and the zero-dependency Python wire-format client (2026-09-07: 200 on /tools/slug, settled on-chain, tx 0xfc1b31c6…06f0, $0.001 USDC on Base). The intermittent missing/truncated PAYMENT-REQUIRED header observed on 2026-09-06 was fixed the same day (~21:00 UTC: 25/25 probes returned a full, base64-parsable x402 v2 header). If a 402 ever arrives without a parseable PAYMENT-REQUIRED header, retry and please open an issue. Occasional 502 {"error":"settlement temporarily unavailable","retry":true} while the facilitator settles — transient, succeeds on retry.

MCP server

  • Hosted: https://sigtap-mcp.sigtap.workers.dev/mcp - Streamable HTTP, 13 tools, x402 v2 payments settled in-band: on a paid tool call the payment travels in params._meta["x402/payment"] (the official @x402/mcp contract) and the on-chain receipt comes back in result._meta["x402/payment-response"] - no HTTP headers involved. Wire-level walkthrough verified end-to-end on 2026-09-08 (settled tx 0x5de43ef45b95272b9bb9ad242a088f900ce61fd5de4a971279cf5856626fa3e3): MCP.md. Health: /health, card: /.well-known/mcp/server-card.json.
  • This repo (mcp_server.py, Dockerfile): zero-dependency stdio server, Python 3 stdlib only. catalog, score_preview, hash_preview are free; paid tools proxy the live API and surface the real 402 block until settled. See SERVER.md. Registered in the Official MCP Registry as io.github.unnamedaiagent/sigtap-agent-tools.

Agent integration

  • Skill for Claude Code / any SKILL.md-aware agent: see SKILL.md (indexed on skills.sh).

MCP one-liner (paid calls settle in-band; paste into any MCP client config):

{ "mcpServers": { "sigtap-agent-tools": { "type": "http", "url": "https://sigtap-mcp.sigtap.workers.dev/mcp" } } }

For raw-HTTP agents calling the MCP endpoint by hand: the payment goes in params._meta["x402/payment"] and the receipt in result._meta["x402/payment-response"] - the full wire format, with live request/response bodies and a zero-dependency Node client, is documented in MCP.md.

  • Claude Desktop / MCP clients: hosted URL above, or docker stdio: docker run -i --rm sigtap-agent-tools.

Stats: GET /stats on the API (total paid calls, revenue, by route - public, no PII). Pricing may be adjusted upward; /openapi.json is always live.

Ask PopNx