Checktrail

Name: Checktrail
Author: stsepelin

by stsepelinversion 0.1.0-alpha.5i★ –iRuns on your computer

Registry nameio.github.stsepelin/checktrail

Install

Overview

Description from the maker (original English)

Local code validation with explicit execution trust and evidence of what actually ran.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "checktrail": {
      "command": "npx",
      "args": [
        "-y",
        "@stsepelin/checktrail",
        "serve",
        "--root",
        "{project_root}"
      ]
    }
  }
}

Run this in your terminal

claude mcp add checktrail -- npx -y @stsepelin/checktrail serve --root '{project_root}'

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "checktrail": {
      "command": "npx",
      "args": [
        "-y",
        "@stsepelin/checktrail",
        "serve",
        "--root",
        "{project_root}"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "checktrail": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@stsepelin/checktrail",
        "serve",
        "--root",
        "{project_root}"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account stsepelin, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32700 servers in this category
Published to the registry more recently than 47% of the other 32700 servers in this category
Basic checks equal to or better than 100% of the other 32700 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Checktrail safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0-alpha.5) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Agent Data Tools: Utilities

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Agent Data Tools: Utilities

by Nutshell2000

103 tools: JSON repair, CSV, hashes, cron, dates, units, validators. 25 free calls.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Checktrail

Local code validation with a CLI, MCP tools, and evidence of what actually ran.

The local MCP server works through the chosen MCP host. That host handles AI selection and subscription/API authentication; Checktrail does not need to log in to a model service. Direct provider calls are an optional separate interface. See the MCP review workflow for implemented tools, planned review stages and the limits of fresh-session enforcement.

Formerly Repo Verifier. See the rename guide for existing source checkouts.

Published preview: 0.1.0-alpha.5. Public source is available at stsepelin/checktrail. See implementation status, the plan and the language matrix before relying on an adapter. Installation covers the CLI, Claude Code and Codex. Agent skills provides setup, validation and review workflows installable with npx skills add stsepelin/checktrail. Project setup covers init, doctor and MCP configuration generator. Release preparation records publication and verification gates. The milestone audit separates implemented profiles from open acceptance work; client checks record actual application coverage. Public adoption records the published package on five pinned libraries, including setup friction and compatibility gaps. Alpha.3 fixes the recorded TypeScript 4.9.5 incompatibility. The setup scope guide explains language, documentation and workflow coverage. Alpha.5 adds named Go build-tag profiles with per-check exclusions. Its release record includes package, client and upgrade/rollback verification.

The hosted matrix passed at release commit 832a044 on Linux and macOS. The exact npm tarball and fresh CLI/MCP installations were verified. The MCP Registry entry is active; execution remains disabled by default.

Checktrail discovers projects, plans registered checks, invokes native tools when explicitly trusted, and reports results without turning skipped or empty checks into success. The same engine serves developers, CI and MCP clients.

The optional library task store retains local validation results across restarts. A library worker adds native execution, polling and cancellation. MCP reports still use memory; standard Tasks integration remains pending.

Try the local checkout

Requires Node.js 22 or newer. Execution currently targets macOS and Linux.

npm ci --ignore-scripts

npm run build node dist/src/cli.js plan --root examples/javascript --detailed node dist/src/cli.js run --root examples/javascript --trust-project --detailed

plan and inspect read files without executing project code. run requires --trust-project: tests, compiler plugins and project configuration can execute code with your user privileges. This is not a sandbox.

Successful commands return JSON except help/version; input errors use stderr. Exit codes:

Code	Meaning
0	Selected checks passed, read-only operation succeeded, or advisory experiment completed
1	At least one selected check failed
2	Required evidence is incomplete, execution is untrusted, or input is invalid

A passing run applies to the selected checks and scope only. PHP syntax passing does not imply its application tests passed. Unknown frameworks and empty plans are incomplete. A source change during validation prevents an aggregate pass.

Initial adapters

Ecosystem	Execution in this foundation
JavaScript	Native Node tests; explicit ESLint checking with per-file coverage evidence
Python	Explicit unittest/pytest tests and Ruff/mypy checks
Go	gofmt check, go vet, uncached go test with JSON events
PHP	Syntax checks and explicit PHPStan analysis; native verification in status
TypeScript	Explicit `javascript.typescript`: local tsc, no emit, file inclusion evidence
Jest	Explicit `javascript.jest`: native result accounting; pending tests are incomplete
Vue	Explicit `javascript.vue-tsc`: SFC and TS checking; opt-in `javascript.vue-router` route contracts
Vitest	Explicit `javascript.vitest`: native JSON counts and exact test-file accounting
Playwright	Explicit `javascript.playwright`: native test/project evidence and prepared browsers
Other framework test runners	Manifest discovery; execution integrations planned
Rust	Locked offline Cargo builds, explicit workspace/target profiles, Clippy/libtest/doctests and Cargo/Rustfmt
Ruby	MRI grammar checks; bounded opt-in RuboCop/RSpec/Minitest with source and lifecycle evidence
Swift	Grammar checks; bounded Linux ARM64 SwiftPM builds, XCTest/Swift Testing and explicit SwiftLint rules
C / C++	Prepared Clang checks; bounded C17/C++20 CMake builds, CTest, clang-format and clang-tidy
Java	Explicit classpath compilation and bounded pinned Checkstyle, Maven reactor and Gradle module tests
C# / .NET	Explicit C# compilation; bounded opt-in C#/F#/VB build/NUnit and C#/VB whitespace checks
GitHub Actions	Static workflow checking with native per-file accounting
Kubernetes	Bounded offline kubeconform document/schema validation with physical source addresses
Kustomize	Bounded local resource/prefix/replica assembly with native render reconciliation and source-bound schema findings
Terraform	Bounded provider-free multi-file JSON module validation with native source diagnostics
Helm	Root-chart and opt-in local application/subchart alias validation with native constraints and source diagnostics
Kotlin	Opt-in pinned detekt light analysis with every-selected-file rule, source, suppression and completion accounting
Scala	Opt-in pinned Scala 2/3 compilation; explicit mixed/generated/compile-only script and ordered macro stages

Tools must already be installed. No dependency installation, automatic fixes, service startup, migrations, commits or deployments are performed by the engine. Go execution disables module proxy downloads and toolchain auto-downloads. The Rust profile uses locked offline Cargo and disables rustup auto-installation. Other invoked tools and test code can still access the network.

Select checks

Without configuration, registered defaults apply to each detected project. Node tests are selected automatically only for the exact script node --test. Python needs an explicit selection because a manifest does not identify a runner. Create checktrail.json in the inspected root:

"schemaVersion": 1, "projects": [ { "path": "web", "checks": ["javascript.node-test", "javascript.eslint"] }, { "path": "library", "checks": ["javascript.typescript"] }, { "path": "service", "checks": ["go.format", "go.vet", "go.test"] }, { "path": "worker", "checks": ["python.unittest"] } ] }

When present, this file selects only the listed projects/checks. Paths are exact discovered project roots relative to --root; use . for that root itself. Configuration cannot supply arbitrary commands or enable execution permissions. The schema rejects unknown fields and check IDs are validated by the engine. Private configuration and rules need not be published. Local public/private JSON packs and additive operator overlays are implemented; see policy packs. An explicit fetch-pack command can download a pinned data-only pack over HTTPS for later offline use. The explicit fetch-adapter command verifies every artifact in a pinned executable bundle before publishing a private file; registration and trusted execution are separate actions.

Operator-registered external adapters can run a pinned local Node, Python, PHP or native executable bundle. Repository configuration can select their registered checks; execution still requires operator trust. The protocol checks evidence completeness, while the adapter author remains responsible for the correctness of its analysis.

The TypeScript check requires a local tsconfig.json and an installed compiler inside the configured root (project-local or hoisted to an ancestor). It disables noCheck, emission and incremental state. Every inventoried .ts, .tsx, .mts and .cts file in that project must appear in the compiler's file list. A clean compiler exit with excluded source is incomplete. Other compiler options, including strictness and declaration checking, come from the project config. Use javascript.typescript-build for project-reference solutions with fresh in-memory declarations. Vue SFC checking uses its separate adapter. TypeScript 6.0.3 is exercised in integration tests; other versions are unverified.

javascript.vue-router captures a selected native testing router and verifies complete record participation in declared URL probes; see the Vue Router profile for versions and projection limits. javascript.nuxt-runtime builds a fresh SSR testing assembly and checks native router capture after in-process requests. Opt-in version 2 also verifies native server handlers, middleware invocations, runtime config boundaries, generated API consumer types and controlled responses. See the Nuxt profile and assembly contracts for versions and scope limits. python.fastapi-routes captures a configured FastAPI application's native routes. Opt-in configuration version 2 also checks declared mounted/hosted assembly, security dependencies, response models, middleware/lifespan order and controlled ASGI responses. See the FastAPI profile and assembly contracts for versions and scope limits. python.django-routes captures supported nested URL resolv

Only the beginning is shown; read the rest in the repo

Checktrail

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Agent Data Tools: Utilities

README from the maker

Checktrail

Try the local checkout

Initial adapters

Select checks