sigtap Agent Tools
概览
作者提供的说明(英文原文)
13 paid x402 tools, USDC/Base. Free check: GET /preview =200 sample. Copy-paste pay: /llms.txt
PopNx MCP 的三大支柱
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
- 用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
- 我们的基础检查i1 项中通过 1 项依据公开信息检查;尚未扫描代码
- 使用情况i非常新★ –
它能帮你做什么
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
- 连接方式: 在云端运行
- 传输方式: Streamable HTTP
- 分类: 搜索与 AI 记忆
安装
选择你使用的 AI 应用,然后复制设置。
安装之前
- 基础检查:1 项中通过 1 项
- 在作者的服务器上运行:你向它提出的内容会经过他们的服务器。
- 注册中心没有列出需要填写的密钥。
你需要
- 在云端运行无需安装任何东西,通过互联网连接
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
- 打开 Settings → Connectors
- 点击 Add custom connector
- 粘贴下面的地址,然后点击 Add
- 如果要求登录,请登录作者的服务
https://sigtap-mcp.sigtap.workers.dev/mcp在终端中运行这条命令
claude mcp add --transport http sigtap-agent-tools https://sigtap-mcp.sigtap.workers.dev/mcp或者自己复制设置
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"sigtap-agent-tools": {
"url": "https://sigtap-mcp.sigtap.workers.dev/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"sigtap-agent-tools": {
"type": "http",
"url": "https://sigtap-mcp.sigtap.workers.dev/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
- 打开网页版 ChatGPT → Settings → Connectors (Apps)
- 点击 Create 或 Add(部分套餐需要先在 Advanced 中开启 Developer mode)
- 粘贴下面的地址,起个名字,然后保存
- 如果要求登录,请登录作者的服务
https://sigtap-mcp.sigtap.workers.dev/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它能做什么
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 unnamedaiagent 验证,该账户拥有此仓库
- … 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
端点有响应
尚未检查;我们会轮流检查各个端点
- … 尚未检查
使用 OAuth 登录
尚未检查;我们会轮流检查各个端点
- … 尚未检查
工具描述中没有隐藏指令
尚未检查;我们会在检查端点时读取工具列表
与“搜索与 AI 记忆”中的其他服务器比较i
- 星标数多于此分类中其他 5696 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 5696 个服务器的 40% 更新
- 基础检查结果等于或优于此分类中其他 5696 个服务器的 100%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
sigtap Agent Tools 安全吗?
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
它还在维护吗?
GitHub 仓库最后更新于–,最新版本(1.0.2)于2个月前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
有什么可以替代它?
同一分类中有:Context7, Codebase Memory, Exa
替代选择
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Codebase Memory
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Exa
Connect AI agents to Exa for web search, content fetching, and multi-step research.
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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, /llms.txt, server-card) - Facilitator: PayAI (
eip155:8453, asset USDC0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) - Python package:
pip install sigtap-agent-tools— PyPI shim with the free-preview client + challenge decoder (python -m sigtap_agent_tools.proberuns 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)
| 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/ | 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)
GET /tools/hash?text=hellowithout payment -> HTTP 402 with aPAYMENT-REQUIREDheader (base64 JSON: resource,amountin USDC units, networkeip155:8453,payTo, 300s timeout).- Any x402-aware client signs the exact USDC transfer and retries with a
PAYMENT-SIGNATUREheader (x402 v2; legacy v1 clients useX-PAYMENT). - 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-urllibUser-Agent is blocked (403 error 1010). Any real UA
works (
requests,httpx,curl,axiospass 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 inparams._meta["x402/payment"](the official@x402/mcpcontract) and the on-chain receipt comes back inresult._meta["x402/payment-response"]- no HTTP headers involved. Wire-level walkthrough verified end-to-end on 2026-09-08 (settled tx0x5de43ef45b95272b9bb9ad242a088f900ce61fd5de4a971279cf5856626fa3e3): 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_previeware free; paid tools proxy the live API and surface the real 402 block until settled. See SERVER.md. Registered in the Official MCP Registry asio.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.