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

@verdict-npm/mcp

v0.2.1

Published

Vera Explore MCP — vera_explore / vera_status / vera_sessions / vera_balance tools for Claude Code & Cursor (MCP server name: verdict)

Downloads

293

Readme

@verdict-npm/mcp

Vera Explore MCP — Claude Code·Cursor에서 Vera AI QA를 바로 실행 (MCP 서버명 verdict). v0.2.0

| 툴 | 설명 | | --- | --- | | vera_explore | URL을 frontier BFS로 크롤하며 자율 QA (Explore → Plan → Judge → Verify → Report). coverage(페이지 수)·depth(링크 깊이) 지정 가능. 대기창 초과 시 session_id 반환 | | vera_status | session_id로 진행 상황 / 완료 결과 조회 | | vera_sessions | 최근 세션 목록 | | vera_balance | 크레딧 잔액·플랜 확인 |

비용: 1 browser step = 1 credit (페이지당 ~10 스텝). 소요: 페이지당 ~2–4분 — 빠른 점검은 coverage: 3~5 권장.

설정

.mcp.json (또는 ~/.claude/mcp.json):

{
  "mcpServers": {
    "verdict": {
      "command": "npx",
      "args": ["-y", "@verdict-npm/mcp"],
      "env": {
        "VERDICT_API_KEY": "vrd_...",
        "VERDICT_BASE_URL": "https://verdict-app.net"
      }
    }
  }
}

API 키는 verdict-app.net → Settings → API Keys에서 발급.

로컬 vera-engine 직결 (API 키 없이): "env": { "VERA_API_URL": "http://localhost:8000" }

사용 예 (Claude Code)

"방금 결제 로직 수정했는데 staging을 Vera로 검증해줘"
→ vera_explore { url, coverage: 5, depth: 2 }
→ 버그 리포트 (심각도·재현 절차·스크린샷)

파이프라인 상세: docs/02_product/spec/vera_pipeline_flow.md