npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@ahmedshaikh/verify-mcp

v0.1.0

Published

Auto-detect how a project checks itself (typecheck / lint / test / build) and run the relevant checks as an MCP server — structured pass/fail with parsed errors, so an agent stops re-deriving commands and grepping walls of output.

Readme

verify

The "did my change actually work?" tool for agents. It auto-detects how a project checks itself — typecheck / lint / test / build — runs the relevant checks, and returns structured pass/fail with parsed errors, so an agent stops re-deriving commands and grepping a wall of stdout.

verify()
→ {
    "ok": false,
    "checks": [
      { "name": "typecheck", "passed": false,
        "errors": [ { "file": "src/api.ts", "line": 42, "message": "TS2304 Cannot find name 'reqId'" } ] },
      { "name": "test", "passed": true, "duration_ms": 1840 }
    ]
  }

Why

Agents change code constantly and then flail at verifying it — re-deriving the build/test commands for every project and eyeballing raw output. verify makes "is what I just did good?" a single, structured primitive. It's the missing keystone of the loop: understand → act → verify → remember.

Tools

  • verify(only?, root?, timeout_ms?) — run the detected checks; structured results. only: ["typecheck"] to run a subset.
  • detect_checks(root?) — list the available checks + commands, without running.

What it detects

| Stack | Checks | |-------|--------| | Node / TS | package.json scripts (typecheck/lint/test/build) + tsc --noEmit from tsconfig | | Python | pytest, mypy, ruff/flake8 (from pyproject / setup.cfg / configs) | | Go | go build · go vet · go test | | Rust | cargo build · cargo test | | fallback | make targets |

Errors are parsed best-effort into {file, line, message} (tsc precisely; a generic file:line extractor for eslint/pytest/go/rust), with an output tail kept for anything unstructured.

Setup

npm install
npm test

Register with an MCP client:

claude mcp add verify -e VERIFY_ROOT=/path/to/project -- node /abs/path/verify/dist/server.js

Or use the CLI: agent-verify (run checks) / agent-verify detect (list them).

Honest limits

  • Detection is heuristic — unusual project layouts may need the only/root args, or a package.json script it can find.
  • Errors are best-effort parsed — exotic formatters fall back to the output tail.
  • Runs the whole detected check (not yet diff-scoped); large suites take as long as they take (with a timeout guard).