
Pathguard
org.cieltech.pathguard由 pathguard.cieltech.org 发布v1.0.0更新于 Oct 24, 2026
Crypto transaction safety tool — screens addresses and transactions for scam risk.
概览
PathGuard 是远程 MCP 服务器,让 AI 助理在对话中检查加密货币地址与交易是否存在诈骗风险。
- 可以做什么
- 检查单笔加密货币收款地址与金额的风险信号,并执行发送前的完整检查,返回允许、需复核或拦截的结论。批量检查最多 1,000 笔交易,可取得精简摘要或完整结果。按用户明确要求举报可疑诈骗地址。查询所连接账户的方案与每月扫描用量,并识别当前 OAuth 连接对应的 PathGuard 账户。
- 适用场景
- 适合在发送加密货币交易前先做风险检查,或希望 AI 助理在对话中快速筛查收款地址与批量交易时使用。若只需查询用量或举报可疑地址,也可加入。
- 运行要求
- 远程端点通过 OAuth 连接已有的 PathGuard 账户,需先创建账户与 API 密钥。本地 stdio 使用需 Python 3.10 以上、mcp 2.0 以上,并从公开仓库安装,且通过环境变量 PATHGUARD_API_KEY 提供密钥。需要网络连接。
安装
在 SourceWeft 中
- 打开 控制台中的 Pathguard,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
交给智能体安装
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/org.cieltech.pathguard%2Fpathguard/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。其他 MCP 客户端
把它添加到你客户端的 mcpServers 配置中。
{
"mcpServers": {
"pathguard": {
"type": "http",
"url": "https://pathguard-v2.up.railway.app/mcp"
}
}
}README
pathguard-mcp
PathGuard MCP lets MCP-compatible AI agents check crypto transactions for scams and mistakes directly in conversation. It supports local MCP clients such as Claude Desktop, Claude Code, Gemini CLI, Grok CLI, Cursor, and Codex, plus remote Streamable HTTP deployments.
Listed on the official MCP Registry as
org.cieltech.pathguard/pathguard.
The production MCP server is a thin, authenticated interface to PathGuard's transaction-safety API. PathGuard analyzes transactions before a send; it does not sign, broadcast, or transfer funds.
Production MCP
Remote Streamable HTTP endpoint:
Remote clients use OAuth to connect an existing PathGuard account. During authorization, PathGuard verifies the user's existing API key. The API key is not exposed to the AI client or returned through MCP.
For local/stdio use, the API key is supplied to the local server process through PATHGUARD_API_KEY.
Install
The package is currently installed directly from this public repository and is not published to PyPI yet.
For development, use an editable install:
Requires Python 3.10+ and mcp >= 2.0.
Get an API key
Create a PathGuard account and API key from the PathGuard API documentation.
Keep your API key private. Do not commit it to GitHub or expose it in browser-side code.
Local MCP clients
For local clients, the server uses stdio and authenticates to the PathGuard API with PATHGUARD_API_KEY.
Claude Desktop
Add this to your Claude Desktop config:
Claude Code
Set PATHGUARD_API_KEY in the environment that starts Claude Code.
Gemini CLI
Grok CLI
Codex, Cursor, VS Code, and other local MCP clients
Use the same stdio server definition as the Claude Desktop example. The exact configuration location varies by client.
Remote clients
For remote clients, use the production OAuth-protected Streamable HTTP endpoint shown above. Never put a PathGuard API key in browser-side configuration.
ChatGPT
In a ChatGPT workspace with Developer Mode enabled, create a custom MCP app and provide:
Choose OAuth authentication. ChatGPT will use the PathGuard authorization flow to connect an existing PathGuard account.
The authorization flow verifies the user's PathGuard API key, then issues OAuth credentials for the MCP connection. The raw PathGuard API key is not returned to ChatGPT.
Available tools
Tool safety boundary
PathGuard MCP is analysis-only. Its tools do not:
- sign transactions;
- broadcast transactions;
- transfer funds;
- request private keys or seed phrases;
- replace your application's authorization controls.
A BLOCK result is a PathGuard safety signal. The wallet, application, or agent remains responsible for authorization, signing, and final transaction execution.
Batch checking
check_transactions_batch supports up to 1,000 items.
By default it returns a compact summary containing:
- total items;
- processed items;
- ALLOW / REVIEW / BLOCK counts;
- maximum risk score;
- flag counts;
- a sample of flagged transactions.
Use detail_level="full" when individual results are required.
Security
- Keep API keys server-side and private.
- Use HTTPS for remote deployments.
- OAuth protects the production remote MCP connection.
- The production MCP server maps the authenticated OAuth subject to an existing PathGuard account.
- Internal server-to-server authentication is not exposed as an MCP argument or model-visible credential.
- Never commit API keys, production credentials, or local
.envfiles.
Full API reference
See the PathGuard API documentation for endpoint schemas, rate limits, pricing, and risk-flag information.
PathGuard MCP: https://pathguard.cieltech.org/mcp
来源:README.md,提交 26191e2
工具
0版本历史
1- v1.0.0最新Sep 16, 2026
评分
已满足适用检查项的 75%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通必需25 分
- 已声明认证方式必需10 分
- 已列出工具必需15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分
请在仓库或注册中心条目中声明许可证。