Websites & DNS
Distinguish resolver behavior, TCP connection, TLS handshake and HTTP response.
Find which layer of the network is failing.
Measure DNS, TCP, TLS, HTTP, UDP, QUIC and HTTP/3 separately. Explain website outages, VPS port problems, proxy failures and IPv4/IPv6 differences with traceable evidence.
Prebuilt binaries, no Rust requiredCodex & Claude Code MCP pluginsTraceable JSON evidenceDeny-by-default network authorization
Designed for real troubleshooting
Break down a connection failure by protocol and evidence. A successful ping cannot prove the application works.
VPS & proxies
Test service ports, SOCKS5 / HTTP CONNECT, UDP Echo, QUIC and HTTP/3 as separate behaviors.
IPv4 vs IPv6
Compare both address families with compatible target, port, rounds and timeout.
v1.5 guided diagnosis is available in the public release candidate
The diagnose command offers 11 named scenarios covering 10 common classes of connectivity problems. Reports distinguish observations, possible causes, unresolved questions and recommended next checks.
pathtrial diagnose --scenario web example.com pathtrial diagnose --scenario vps YOUR_VPS_IP --port 22 pathtrial diagnose --scenario latency example.com --rounds 10 pathtrial diagnose --scenario proxy --url https://example.com/ --proxy socks5://127.0.0.1:1080 pathtrial diagnose --scenario local
Public prerelease: the v1.5.0-rc.1 binaries include guided diagnosis and 10 MCP tools. Three platform release builds and MCP smoke checks passed. Windows is not supported.
Use the CLI without an AI account
Run checks directly on macOS or Linux. No cloud account or background service is needed; PathTrial does not automatically change DNS, routes, proxies or firewall settings.
Reports use PASS, WARN, FAIL, SKIP and INCONCLUSIVE, and refer to measured probe IDs rather than invented causes.
Read the CLI guide →# PathTrial v1.5.0-rc.1
pathtrial --version
pathtrial scan example.com \
--profile web --rounds 5 --redact-ipsTroubleshooting guides
Evidence-first guides for VPS ports, QUIC/HTTP3 and IPv4/IPv6 differences.
Connect to Codex and Claude Code
Use the local MCP server with version 0.3.0 plugins, exposing ten tools including guided diagnosis and report explanation.
OpenAI Codex
Install the marketplace plugin and verify the local MCP connection.
codex plugin marketplace add \ gaochenyang666-droid/PathTrial codex plugin add pathtrial@pathtrial
Claude Code
Install from the Claude Code plugin marketplace and inspect the connection with /mcp.
/plugin marketplace add gaochenyang666-droid/PathTrial /plugin install pathtrial@pathtrial /mcp
Security: probing is denied by default. Explicitly authorize targets you own or are permitted to test. Offline report explanation requires no network authorization. MCP guide
From download to your first report
Use the public release candidate with SHA-256 checksums.
01
Select your platform
Choose the macOS Apple Silicon, macOS Intel or Linux x86_64 build.
02
Verify CLI and MCP
Run pathtrial --version and pathtrial mcp --help, then install a plugin if needed.
03
Test and share safely
Probe authorized targets, redact sensitive addresses, and provide reproducible steps when reporting issues.
Frequently asked questions
How is PathTrial different from ping or curl?
It records separate protocol measurements, traces findings to probe IDs, and states what evidence does not establish.
Do I need Rust to install?
No. Prebuilt packages are available for macOS ARM64, macOS Intel and Linux x86_64.
Does PathTrial test unauthorized devices?
MCP network probes are denied by default. Authorize individual targets before testing and remove sensitive details before sharing reports.