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

rea-light-mcp

v0.1.0

Published

Lightweight MCP facade for REA (Reverse Engineer Anything) — 4 flat tools, depth-1 schemas, full REA behind

Readme

rea-light-mcp

Lightweight MCP facade for REA (Reverse Engineer Anything).

Full REA advertises ~139 tools / ~1.87MB of schemas with nesting up to depth 14 — strict providers (Muse Spark / Gemini / Moonshot 10-level cap, Moonshot ~14KB/schema cap) reject the whole request because of one deep tool, even for hi.

rea-light-mcp advertises 4 flat tools (depth 1, ~2KB total) and keeps the full REA catalog hidden server-side behind a persistent REA MCP child.

Tools

| Tool | Input (all depth 1) | What | |------|---------------------|------| | rea_search | query:string, domain?:enum, limit?:1-10 | Keyword search over cached REA catalog, top 5 briefs | | rea_describe | name:string | One tool's full schema as markdown text (never as schema) | | rea_call | name:string, args_json:string | Run any REA tool; complex args travel as a string, validated server-side | | rea_investigate | target:string, question:string, depth?:enum | Pinned agentic entry: open + inspect, final markdown only |

Install

No installation — run with npx once published, or locally:

cd /home/md/src/mcp/rea-light-mcp && npm ci && npm run build

Configure (OpenCode)

"rea-light": {
  "type": "local",
  "command": ["node", "/home/md/src/mcp/rea-light-mcp/dist/index.js"],
  "enabled": true,
  "environment": {
    // optional overrides:
    // "REA_COMMAND": "npx -y [email protected] mcp",
    // "REA_TIMEOUT_MS": "120000",
    // "REA_LIGHT_ALLOW_WRITE": "1",
  }
}

Disable full rea while using this — that is the point.

Env

| Var | Default | Notes | |-----|---------|-------| | REA_COMMAND | npx -y [email protected] mcp | Pinned 139-tool release; avoids unreleased HEAD +33 groups | | REA_TIMEOUT_MS | 120000 | stdio is sequential, like worklink-mcp | | REA_LIGHT_ALLOW_WRITE | unset (read-only) | Set 1 to allow annotate_*/set_* write-path tools |

Why not 5 flat tools?

Flat tools re-introduce deep schemas or lose capabilities. The hub keeps all 139+ capabilities with constant catalog bytes: search/describe/call is the 2026 dispatcher + progressive-discovery consensus (FastMCP search transforms, tools/list -> search_tools + call_tool).

License

MIT