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

@elicitly/tools

v0.5.0

Published

Embeddable MCP elicitation toolkit — register elicit_confirm, elicit_form, and elicit_doctor on any McpServer, plus the elicitation-schema types and capability report/probe layer.

Readme

@elicitly/tools

Embeddable MCP elicitation toolkit: put the Elicitly tools — elicit_confirm, elicit_form, elicit_doctor — on your own McpServer, with the elicitation-schema types and the capability report/probe layer they build on.

import { makeElicitAdapter, registerFormTools } from "@elicitly/tools"
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js"

const server = new McpServer({ name: "my-server", version: "1.0.0" })
const { elicit, clientView } = makeElicitAdapter(server, {
  getProtocolVersion: () => null,
})
registerFormTools(server, {
  elicit,
  clientView,
  serverInfo: { name: "my-server", version: "1.0.0" },
})

Your server now exposes the three elicitation tools with the same wire contract as elicitly — dialogs rendered by the connected host, results returned as typed JSON.

What's inside

  • registerFormTools(server, deps) — registers elicit_confirm, elicit_doctor, elicit_form (alphabetical wire order).
  • makeElicitAdapter(server, opts) — bridges an McpServer to the injected elicit function the tools use (SDK-coupled edge, kept in one place).
  • confirm / elicitForm / doctor — the tool handlers themselves, SDK-agnostic and unit-tested; use them directly for custom registration.
  • core/ (re-exported) — the SDK-free layer: elicitation-schema types (ElicitSchema, scalarSchema) and the passive capability report + probe classification (buildPassiveReport, classifyProbe).

License

Apache-2.0