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

@agent-teams/docs-protocol-mcp

v0.2.5

Published

Open-source read-only MCP stdio adapter for documentation governed by the Agent Teams docs protocol in any repository.

Readme

@agent-teams/docs-protocol-mcp

Open-source optional read-only MCP stdio adapter for documentation governed by @agent-teams/docs-protocol in any repository.

Prove and install the exact compatible pair only through the canonical MCP workflow, which owns versions, registry pinning, and atomic installation.

docs-protocol-mcp --consumer-root /absolute/repository/path

The consumer root is fixed when the process starts. The profile is selected by an optional --profile argument or deterministic discovery of docs.config.yaml and the legacy architecture/foundation/docs-protocol.yaml path. Discovery fails closed when both or neither exist. MCP tool arguments cannot replace either value.

The read-only adapter is capability-qualified on POSIX and Windows. A Windows repository must already contain portable authority initialized and committed from a supported POSIX host; the adapter never performs bootstrap mutation or recovery.

The V1 surface contains only docs_info, docs_find, and docs_context. docs_context returns bounded llms.txt context with optional filters and advisory fuzzy ranking. There is no authoring, recovery, upgrade, network, shell, or process-execution capability.

Results are bounded, request cancellation is propagated through an AbortSignal, and unexpected failures are returned without host paths or raw error details.

Successful tool calls use the closed Agent Teams MCP projection schema version 1, return the same projection as text and structuredContent, and advertise their exported DOCS_*_OUTPUT_SCHEMA_V1 schema through MCP outputSchema. Projection list caps and truncation evidence are part of those schemas. MCP Server 2.0 supports one success outputSchema per tool; isError responses do not carry structuredContent, so their separately exported closed DOCS_ERROR_OUTPUT_SCHEMA_V1 cannot be registered as an alternate output.