mcpField
P
PitchPilot Agent Tools (legacy name - see sigtap)

PitchPilot Agent Tools (legacy name - see sigtap)

Local
sigtap-outreach-api.sigtap.workers.devBusiness & Marketing0Updated 8w ago

About PitchPilot Agent Tools (legacy name - see sigtap)

PitchPilot Agent Tools is a deprecated legacy name; the project was renamed sigtap-agent-tools and its former workers are retired. The successor offers paid agent tools and an MCP server, with per-call x402 payments in USDC.

Key features

  1. 01Audit email-domain deliverability
  2. 02Score and draft cold emails
  3. 03Hash, JSON, and JWT utilities
  4. 04Domain, regex, and UUID utilities
  5. 05Check weather and crypto prices

Use cases

  1. 01Check authentication settings for a sending domain
  2. 02Evaluate or generate cold emails
  3. 03Call small data utilities from agent workflows

MCP support

The deployment under the legacy name is retired; its successor sigtap-agent-tools provides hosted Streamable HTTP and local stdio MCP servers. Paid tools use x402 settlement, which the input says can be handled in-band over MCP.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

[DEPRECATED] This project was rebranded and superseded by sigtap-agent-tools (live endpoints: https://sigtap-outreach-api.sigtap.workers.dev , https://sigtap-mcp.sigtap.workers.dev/mcp ). The legacy *.pitchpilot-agents.workers.dev workers are retired. This repo is kept read-only for history.

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.001-$0.01), no signup, no API keys - the signed payment IS the credential.

  • HTTP API: https://sigtap-outreach-api.sigtap.workers.dev

  • MCP (Streamable HTTP): https://sigtap-mcp.sigtap.workers.dev/mcp (13 tools)

  • Facilitator: PayAI (eip155:8453, asset USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913)

  • Kit tier (humans): https://unnamedaiagent.github.io/sigtap-kit/ - AI Outreach Kit, $19, crypto (BTC/ETH/USDT), instant email delivery - free sampler PDF (no email needed)

  • Sibling origin - sigtap Agent Tools (same 12-tool catalog, second deployment): HTTP https://sigtap-outreach-api.sigtap.workers.dev - MCP https://sigtap-mcp.sigtap.workers.dev/mcp - paid x402 calls settle over MCP end-to-end (verified on-chain). Free catalog: GET / on either origin. Listed on 402index (21 records), x402scan (15 resources), Official MCP Registry (io.github.unnamedaiagent/sigtap-agent-tools) and Smithery. Repo: unnamedaiagent/sigtap-agent-tools

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 /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.001SHA-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?type=&count=$0.001UUIDv4/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 an X-PAYMENT header.
  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.

MCP server

  • Hosted: https://sigtap-mcp.sigtap.workers.dev/mcp - Streamable HTTP, 13 tools, x402 v2 payment settled in-band. 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.

    If your client's x402 middleware does not settle on this server's paid tools, use the sibling sigtap origin above - MCP settlement there is verified working.

Agent integration

  • Skill for Claude Code / any SKILL.md-aware agent: see SKILL.md (indexed on skills.sh).
  • Claude Desktop / MCP clients: hosted URL above, or docker stdio: docker run -i --rm sigtap-agent-tools.

Health: GET /health. Pricing may be adjusted upward; /openapi.json is always live.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.