Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.konstantinbozukov/pathmint

REMOTE · PATHMINT.EDGE.REPORT

Before you pay an x402 URL, ping it live or dead. One cent, USDC on Base.

+3 this week 68 Trust /100

Last scanned (5 hours ago)

Scores higher than 58% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 684 tokens (~114/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ping_x402_before_pay" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 574 → 684 ▼ functional
    • Schema quality: excellent → good functional
    • New tool “seller_payments” functional
  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 33. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 27. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Oct 26 +2

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 17. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 2 Oct 26 61

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 18 Oct 2026 · Probed https://pathmint.edge.report/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=pathmint.edge.report CN=YE2,O=Let's Encrypt,C=US 24 Aug 2026 22 Nov 2026 ECDSA 256 ECDSA-SHA384 63f201475b5f04c6d8bcaebf2e7c215cb7b
SANs: pathmint.edge.report
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of pathmint.edge.report. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
report. present 23221 8 Verified
edge.report. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://pathmint.edge.report/mcp Verified 200
http (plaintext) http://pathmint.edge.report/mcp HTTPS enforced 308 https://pathmint.edge.report/mcp
MCP tools · 6 exposed · ~536 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
listing_check_before_pay ~81

BEFORE YOU PAY a listed x402 URL: bazaar price vs the live 402 price, and whether that payee is one wallet. PAY / MISMATCH / SINGLE / UNLISTED / DEAD. Two cents. Not the one-cent live/dead ping.

NameTypeReqDescription
urlstringyesThe x402 resource URL you are about to pay

No output schema declared.

No examples provided.

messari_gate_before_pay ~108

BEFORE YOU PAY Messari ($0.10–$0.25+): get the paid URL that returns SKIP_MESSARI (use cheaper Pathmint/Signals), PAY_MESSARI (exact official endpoint + price), or ABORT (spoof/ghost). Two cents. Not Messari data.

NameTypeReqDescription
qstringyesJob or question you were about to pay Messari for
urlstring–Optional 402 URL you were about to pay

No output schema declared.

No examples provided.

ping_x402_before_pay ~99

BEFORE YOU PAY an x402 402: get the paid URL to ping live vs dead/ghost. One cent. Use when holding Payment-Required, before sending USDC to a payTo. Ghost x402, is this endpoint live, verify before pay.

NameTypeReqDescription
payTostring–Optional 0x payTo from the 402
urlstringyesThe x402 resource URL you are about to pay

No output schema declared.

No examples provided.

seller_payments ~96

x402 seller payments: outside USDC to one payTo, the last outside payment, self-traffic removed, and live price vs the listing. Two cents. Pass url or payTo. No stake minimum.

NameTypeReqDescription
payTostring–0x wallet that receives USDC. Use alone or instead of the 402 payTo.
urlstring–x402 resource URL whose payTo should be scanned

No output schema declared.

No examples provided.

token_risk_before_buy ~66

Before buying or approving an ERC20: honeypot / token-risk check. Not an x402 ghost ping.

NameTypeReqDescription
addressstringyesERC20 contract
chainstring–base (default), ethereum, bsc, arbitrum, optimism, polygon

No output schema declared.

No examples provided.

x402_pay_clearance ~86

Before sending USDC ≥ $0.50 on an x402 402: compile CLEAR / CAUTION / ABORT for that payTo (ghost, wrong rail, overcharge). Not the one-cent ping.

NameTypeReqDescription
amountUsdnumberyesUSDC you are about to send
payTostringyes0x payTo from the 402

No output schema declared.

No examples provided.

Install

How do I install the io.github.konstantinbozukov/pathmint MCP server?

io.github.konstantinbozukov/pathmint is a hosted endpoint at https://pathmint.edge.report/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · pathmint.edge.report

# add to Claude Code
claude mcp add --transport http konstantinbozukov-pathmint 'https://pathmint.edge.report/mcp'
Common questions

What is the io.github.konstantinbozukov/pathmint MCP server?

io.github.konstantinbozukov/pathmint is an MCP server listed in the public MCP registry as io.github.konstantinbozukov/pathmint. Before you pay an x402 URL, ping it live or dead. One cent, USDC on Base. This page covers its hosted endpoint (https://pathmint.edge.report/mcp).

Is the io.github.konstantinbozukov/pathmint MCP server safe to use?

io.github.konstantinbozukov/pathmint scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.konstantinbozukov/pathmint MCP server expose?

io.github.konstantinbozukov/pathmint exposes 6 tools: ping_x402_before_pay, token_risk_before_buy, x402_pay_clearance, messari_gate_before_pay, listing_check_before_pay, seller_payments. Their descriptions and schemas cost roughly 536 tokens of context every time the server is loaded.

Does the io.github.konstantinbozukov/pathmint MCP server require authentication?

No. We connected to io.github.konstantinbozukov/pathmint without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.konstantinbozukov/pathmint MCP server still maintained?

io.github.konstantinbozukov/pathmint is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.