Skip to main content
ClaudeWave
unnamedaiagent avatar
unnamedaiagent

sigtap-agent-tools

Ver en GitHub

sigtap - paid micro-tools for AI agents over x402 (USDC on Base). One signature per call. No keys.

MCP ServersRegistry oficial0 estrellas0 forksPythonMITActualizado today
ClaudeWave Trust Score
95/100
Verified
Passed
  • Open-source license (MIT)
  • Actively maintained (<30d)
  • Clear description
  • Topics declared
  • Documented (README)
Last scanned: 9/8/2026
Install in Claude Code / Claude Desktop
Method: pip / Python · sigtap-agent-tools
Claude Code CLI
claude mcp add sigtap-agent-tools -- python -m sigtap-agent-tools
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "sigtap-agent-tools": {
      "command": "python",
      "args": ["-m", "sigtap_agent_tools.probe"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
💡 Install first: pip install sigtap-agent-tools
Casos de uso

Resumen de MCP Servers

# sigtap Agent Tools

[![skills.sh installs](https://skills.sh/b/unnamedaiagent/sigtap-agent-tools)](https://skills.sh/unnamedaiagent/sigtap-agent-tools) [![MPP32 owner-verified](https://img.shields.io/badge/MPP32-owner--verified-ff991a)](https://agentrateindicators.com/s/sigtap-outreach-api.sigtap.workers.dev) [![Listed on mcpservers.org](https://mcpservers.org/badge.svg)](https://mcpservers.org/servers/unnamedaiagent/sigtap-agent-tools) [![Glama MCP connector](https://img.shields.io/badge/Glama-connector_(tier_A_quality)-8a2be2)](https://glama.ai/mcp/connectors/io.github.unnamedaiagent/sigtap-agent-tools)

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](https://sigtap-mcp.sigtap.workers.dev/openapi.json), [/llms.txt](https://sigtap-mcp.sigtap.workers.dev/llms.txt), [server-card](https://sigtap-mcp.sigtap.workers.dev/.well-known/mcp/server-card.json))
- Facilitator: PayAI (`eip155:8453`, asset USDC `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`)
- **Python package:** `pip install sigtap-agent-tools` — [PyPI](https://pypi.org/project/sigtap-agent-tools/) 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)](https://unnamedaiagent.github.io/sigtap-kit/ai-outreach-kit-sampler.pdf)

## Free touch (no wallet needed)

| Route | What 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/<paid-path>` | 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.json` | Full OpenAPI with `x-payment-info` prices |
| `GET /llms.txt` | Agent-readable endpoint digest |

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

**Outreach intelligence (the money tools):**

| Endpoint | Price | Output |
|---|---|---|
| `GET /deliverability?domain=` | $0.003 | SPF/DKIM/DMARC audit for a sending domain |
| `GET /grade?to=&subject=&body=` | $0.005 | 12-point cold-email score with concrete fixes |
| `GET /template?...` | $0.010 | Personalized cold email from proven templates |

**Micro-tools ($0.001-$0.003):**

| Endpoint | Price | Output |
|---|---|---|
| `GET /tools/crypto-price?from=BTC&to=USD` | $0.002 | Coinbase spot/buy/sell + spread % |
| `GET /tools/domain-age?domain=` | $0.003 | Registration date, age, registrar (RDAP) |
| `GET /tools/hash?text=` | $0.0005 | SHA-256/384/512, hex, base64(url), CRC32 |
| `GET /tools/json?data=` | $0.001 | Flatten to dot paths / rows to CSV |
| `GET /tools/jwt-decode?token=` | $0.001 | JWT header+payload with safety flags |
| `GET /tools/regex?pattern=&text=` | $0.001 | Matches, groups, count, ReDoS-risk heuristic |
| `GET /tools/slug?text=` | $0.001 | Unicode-safe slug (incl. Cyrillic translit) |
| `GET /tools/uuid?version=&count=` | $0.0005 | UUIDv4/v7, ULID, nanoid - batched |
| `GET /tools/weather?lat=&lon=` | $0.001 | Current + 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](SKILL.md#client-notes-avoid-a-silent-403).

## 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)**

```js
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](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](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](SKILL.md)
  (indexed on skills.sh).

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

```json
{ "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](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.
ai-agentsai-toolsapibasecold-emailcrypto-paymentsemail-deliverabilityemail-marketingmcpmcp-servermicropaymentsoutreachpayment-requiredusdcx402

Lo que la gente pregunta sobre sigtap-agent-tools

¿Qué es unnamedaiagent/sigtap-agent-tools?

+

unnamedaiagent/sigtap-agent-tools es mcp servers para el ecosistema de Claude AI. sigtap - paid micro-tools for AI agents over x402 (USDC on Base). One signature per call. No keys. Tiene 0 estrellas en GitHub y su última actualización registrada es del 2026-09-08.

¿Cómo se instala sigtap-agent-tools?

+

Puedes instalar sigtap-agent-tools clonando el repositorio (https://github.com/unnamedaiagent/sigtap-agent-tools) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.

¿Es seguro usar unnamedaiagent/sigtap-agent-tools?

+

Nuestro agente de seguridad ha analizado unnamedaiagent/sigtap-agent-tools y le ha asignado un Trust Score de 95/100 (tier: Verified). Revisa el desglose completo de comprobaciones superadas y flags en esta página.

¿Quién mantiene unnamedaiagent/sigtap-agent-tools?

+

unnamedaiagent/sigtap-agent-tools es mantenido por unnamedaiagent. La última actividad registrada en GitHub es del 2026-09-08, con 1 issues abiertos.

¿Hay alternativas a sigtap-agent-tools?

+

Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.

Despliega sigtap-agent-tools en tu cloud

Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.

¿Mantienes este repo? Añade un badge a tu README

Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.

Featured on ClaudeWave: unnamedaiagent/sigtap-agent-tools
[![Featured on ClaudeWave](https://claudewave.com/api/badge/unnamedaiagent-sigtap-agent-tools)](https://claudewave.com/repo/unnamedaiagent-sigtap-agent-tools)
<a href="https://claudewave.com/repo/unnamedaiagent-sigtap-agent-tools"><img src="https://claudewave.com/api/badge/unnamedaiagent-sigtap-agent-tools" alt="Featured on ClaudeWave: unnamedaiagent/sigtap-agent-tools" width="320" height="64" /></a>

Más MCP Servers

Alternativas a sigtap-agent-tools