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

gotchea-mcp

v0.2.0

Published

MCP server for gotchea: codebase comprehension maps and quizzes for coding agents

Readme

gotchea-mcp

The MCP server for gotchea: codebase comprehension maps and quizzes for coding agents.

You don't need to install it. The gotchea CLI starts it, which is the recommended setup:

claude mcp add gotchea -- npx -y gotchea mcp

For Codex, add the following to ~/.codex/config.toml:

[mcp_servers.gotchea]
command = "npx"
args = ["-y", "gotchea", "mcp"]

This package also works on its own: npx -y gotchea-mcp serves the current directory over stdio. Requires Node.js >= 20.

Tools

| Tool | What it does | |---|---| | scan | Chunk the repository and update the map (added, changed, moved and removed chunks). | | get_map | The heat map with colors, LOC and question counts; optional path and depth. | | get_chunk_for_file | The innermost chunk for a path and line, or the file chunk and its leaves. | | get_status | Chunk and question counts, reviews due now, leaf color distribution. | | get_generation_tasks | The next chunks that need questions, with numbered code and instructions (stems of existing questions only). | | save_questions | Validate and save the questions written for one task; refused if the code changed. | | start_quiz | Start or resume a quiz on one chunk; returns the first question, a cited code block and every option in full in a marked text block for the agent to show verbatim. Optional includeCode: false leaves the preview out (default: config quiz.showCode, true, for a new session; a resumed session keeps its own setting). | | submit_answer | Record the user's answer; returns the reveal (correct option, explanation and the cited lines of code, up to 15 per reference and 30 per reply), then the next question with its cited code block and full options, or the result. The excerpt is left out when previews are off, the file changed since the last scan, or the reference is approximate. Optional includeCode (default: the value the session started with). |

No tool returns a correct answer or explanation before the question is answered. Generate questions in a subagent or a separate session, never in the conversation you are quizzed in.

Taking a quiz

By default the agent shows the code block with its path:startLine-endLine header, the question and all options A–D exactly as returned. Answer with a letter, or choose A–D if the agent offers a selection prompt. The text result contains the complete question between <<<SHOW TO USER VERBATIM and SHOW TO USER VERBATIM>>>; selection prompts need only the letters. After each answer the agent should also show the answer-feedback block, between <<<SHOW ANSWER FEEDBACK TO USER VERBATIM and SHOW ANSWER FEEDBACK TO USER VERBATIM>>>: the correct option, the explanation and the cited code under path:start-end headers. The server also sends these display rules as MCP instructions. Showing them is a request to the agent, not something the protocol enforces. If a question has no code preview, the text says so. The agent waits for your answer before calling submit_answer.

Form elicitation is opt-in: launch the server with GOTCHEA_MCP_ELICIT=on (or auto) and use a client that supports forms. The form message contains the code as plain numbered lines and all options in full; its choices have short, single-line A–D titles. Long messages or code previews over 40 lines fall back to the complete text flow. GOTCHEA_MCP_ELICIT=off selects the default text flow explicitly.

Programmatic use

import { createServer, startStdioServer } from 'gotchea-mcp';

await startStdioServer({ root: '/path/to/repo' }); // or connect createServer(opts) to any transport

Documentation

See the main README and the setup guides for Claude Code and Codex.

License

MIT © 2026 Futuretea LTD