Pathguard

org.cieltech.pathguardPublished by pathguard.cieltech.orgv1.0.0Updated Oct 24, 2026

Crypto transaction safety tool — screens addresses and transactions for scam risk.

VerifiedStreamable HTTPWeb executableFinance Security & Monitoring

Server details

Identifier: org.cieltech.pathguard/pathguard
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to pathguard.cieltech.org, but the endpoint is not on that domain, so the publisher may not run this server.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/org.cieltech.pathguard%2Fpathguard.svg)](https://sourceweft.com/mcp/org.cieltech.pathguard%2Fpathguard?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

PathGuard is a remote MCP server that lets an AI assistant screen crypto addresses and transactions for scam risk in conversation.

What you can do: Check a single crypto destination and optional amount for risk signals, and run the full pre-send check that returns allow, review or block. Batch-check up to 1,000 transactions with a compact summary or full results. Report a suspected scam address when the user explicitly asks. View the connected account's plan and monthly scan usage, and identify the PathGuard account behind the OAuth connection.
When to use it: Use it when you want a scam-risk check before sending a crypto transaction, or want an assistant to screen destination addresses and batches of transactions in conversation. Also useful for checking plan usage or reporting a suspected scam address.
Requirements: The remote endpoint connects an existing PathGuard account through OAuth, so an account and API key are needed. Local stdio use needs Python 3.10 or later and mcp 2.0 or later, installed from the public repository, with the key supplied through the PATHGUARD_API_KEY environment variable. Network access is required.

Before you install

A PathGuard API key is required; the remote flow verifies an existing key through OAuth, and the key should stay private and out of version control or browser-side code. Tools are analysis-only and do not sign, broadcast or transfer funds, and do not ask for private keys or seed phrases. Reporting a scam address writes data, and transaction details are sent to the PathGuard service. A block result is only a safety signal; authorization and execution stay with the wallet or application.

Installation

In SourceWeft

Open Pathguard in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/org.cieltech.pathguard%2Fpathguard/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "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.

[MCP Registry]

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:

json

{  "mcpServers": {    "pathguard": {      "command": "pathguard-mcp",      "env": {        "PATHGUARD_API_KEY": "pg_your_key_here"      }    }  }}

{  "mcpServers": {    "pathguard": {      "command": "pathguard-mcp",      "env": {        "PATHGUARD_API_KEY": "pg_your_key_here"      }    }  }}

Claude Code

Set PATHGUARD_API_KEY in the environment that starts Claude Code.

Gemini CLI

json

{  "mcpServers": {    "pathguard": {      "command": "pathguard-mcp",      "env": {        "PATHGUARD_API_KEY": "pg_your_key_here"      }    }  }}

{  "mcpServers": {    "pathguard": {      "command": "pathguard-mcp",      "env": {        "PATHGUARD_API_KEY": "pg_your_key_here"      }    }  }}

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	What it does
`check_transaction`	Inspect one crypto destination and optional amount for PathGuard risk signals.
`preflight_transaction`	Run the full pre-send check and return `ALLOW`, `REVIEW`, or `BLOCK`.
`check_transactions_batch`	Check up to 1,000 transactions and return a compact risk summary or full results.
`report_scam_address`	Record a suspected scam address when the user explicitly asks to report it.
`get_usage_status`	View the connected account's plan and monthly scan usage.
`get_profile`	Identify the PathGuard account represented by the OAuth connection.

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 .env files.

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

Source: README.md at commit 26191e2

Tools

SourceWeft has not read this server's tools yet.

Version history

v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts
Declare a license in the repository or the registry entry.