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

@agentwares/mcp-kit

v0.2.0

Published

Expose any package as an MCP server: one defineTool definition served over stdio and Streamable HTTP, errors that always carry code/cause/fix/retryable, 402 payment gating, and generators for server.json, llms.txt and pricing.json.

Readme

@agentwares/mcp-kit

Expose any package as an MCP server. One defineTool definition is served over stdio and Streamable HTTP from the same code; the HTTP handler is Web-standard (Request → Response) so it runs unchanged in Next.js route handlers, Vercel Functions and Cloudflare Workers.

  • defineTool — zod input/output, naming lint (<namespace>_<verb>_<object>), descriptions written for a new teammate
  • errors always carry { code, cause, fix, retryable } (in the result text and, where the client can take it, structuredContent)
  • withPayment — 402 with x402 + Stripe MPP payment options (Wave 0 stub: comingSoon: true, free sample mode)
  • generateServerJson + registryPublishWorkflow — official MCP registry server.json and a tag-triggered OIDC publish workflow
  • renderLlmsTxt, pricingJson, listToolManifest — the machine-readable docs every product ships
npm install @agentwares/mcp-kit

Define a tool, serve both transports

import { z } from "zod";
import { createHttpHandler, defineTool, serveStdio, toolError } from "@agentwares/mcp-kit";

const createMonitor = defineTool({
  name: "agentcheck_create_monitor", // namespaced or it throws at boot
  description:
    "Create an uptime monitor for an MCP endpoint. Returns the monitor id and when it is first checked.",
  input: z.object({ url: z.url(), intervalMinutes: z.number().int().min(5).default(5) }),
  output: z.object({ id: z.string(), nextCheckAt: z.string() }),
  annotations: { readOnlyHint: false, idempotentHint: false },
  async handler({ url, intervalMinutes }, ctx) {
    if (!ctx.headers.get("authorization"))
      throw toolError("UNAUTHORIZED", "no API key sent", "retry with Authorization: Bearer <key>");
    return {
      id: await createMonitorRow(url, intervalMinutes),
      nextCheckAt: new Date().toISOString(),
    };
  },
});

const server = { name: "agentcheck", version: "1.0.0", tools: [createMonitor] };
export const POST = createHttpHandler(server); // Next.js app/mcp/route.ts (also Workers: `fetch: handler`)
if (process.argv.includes("--stdio")) await serveStdio(server); // npx entry for Claude Desktop / Cursor

ctx carries headers (empty over stdio), requestId, signal, sessionId, log(), progress() and extra (the raw SDK context: sendRequest for sampling/elicitation). createMcpServer(opts) returns the SDK McpServer if you need resources or prompts too; pass a factory createHttpHandler(() => server) in that case.

The HTTP handler is stateless by default (fresh server + transport per request, one JSON body per POST, GET → 405) — right for Vercel/Workers. Pass jsonResponse: false to stream SSE so ctx.log/ctx.progress reach the client mid-call. Pass sessions: true on a long-lived process to keep Mcp-Session-Id sessions in memory (SSE by default): that enables sampling/elicitation via ctx.extra.sendRequest and the standalone GET stream. OPTIONS handles CORS when cors: true; handleHealth({ name, version, tools }) gives you a /health JSON response.

tools/list is served from listToolManifest(tools) — JSON Schema 2020-12 with additionalProperties: false for plain z.objects (use z.looseObject to allow extra keys) — so what llms.txt documents is exactly what the server advertises.

Errors

throw toolError("NOT_FOUND", "no monitor mon_1", "list monitors and use an existing id");
throw toolError({
  code: "RATE_LIMITED",
  cause: "10 req/min exceeded",
  fix: "wait 30s",
  retryable: true,
  details: { resetAt },
});

Every failure — thrown toolError, plain Error (→ INTERNAL), invalid arguments (→ INVALID_INPUT naming the fields, zod issues in details) — becomes a result with isError: true, the JSON body in content[0].text and _meta.httpStatus. Codes: INVALID_INPUT NOT_FOUND UNAUTHORIZED PAYMENT_REQUIRED RATE_LIMITED UPSTREAM_ERROR INTERNAL (plus your own). structuredContent also carries the body unless the tool declares an output schema, because the official SDK client validates any structuredContent against outputSchema even on errors.

Payment stub (Wave 0)

const paidLookup = withPayment(lookup, {
  priceUsd: 0.05,
  authorize: async (ctx) => entitlementFor(ctx.headers),
});

Adds an optional sample: boolean input ("return an example response at no charge"). Flow per call: sample → handler with ctx.sample = true; else authorize ok → handler with ctx.userId; else the verifier checks the request's payment headers (default StubVerifier, never accepts); else a PAYMENT_REQUIRED result whose body is @agentwares/x402's PaymentRequiredBody — both rails in accepts, comingSoon: true until the wallet ships, _meta.httpStatus: 402. For plain HTTP endpoints use paymentRequiredHttpResponse({ resource, priceUsd }).

Registry: server.json + publish on tag

const serverJson = generateServerJson({
  name: "io.github.acme/deal-memo", // io.github.<owner>/ is required for OIDC publishing
  description: "Turn a pitch deck into a scored deal memo.", // ≤ 100 chars
  version: "0.1.0",
  repository: {
    url: "https://github.com/acme/deal-memo",
    source: "github",
  },
  remoteUrl: "https://deal-memo.example.com/mcp",
  npmPackage: { identifier: "@acme/deal-memo-mcp", version: "0.1.0" }, // package.json needs `mcpName`
});
writeFileSync(
  ".github/workflows/publish-mcp.yml",
  registryPublishWorkflow({ serverJsonPath: "server.json" }),
);

Schema: https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json. The workflow runs on tags matching mcp-*, installs mcp-publisher, login github-oidc, publish — no secrets.

Docs

renderLlmsTxt({ name, summary, links, tools })llms.txt; pricingJson({ product, tiers, meters, updatedAt }){ schema: "agentwares.pricing/v1", ... }; listToolManifest(tools)[{ name, description, inputSchema, annotations }].

Example + conformance

pnpm example:http        # serves example_echo / example_add / example_paid_lookup at http://127.0.0.1:8765/mcp
pnpm conformance         # builds, starts the example (stateful + SSE) with the suite's fixture tools/resources/prompts,
                         # runs npx -y @modelcontextprotocol/[email protected] server --url http://127.0.0.1:<port>/mcp
pnpm conformance --stateless   # the serverless default: everything but sampling/elicitation passes
pnpm conformance --json        # JSON responses: additionally no mid-call log/progress notifications

dist/example-http.js flags: --port= --host= --path= --sse --stateful --conformance --dns-protection. conformanceTools / registerConformanceFixtures(server) are exported so any product server can run the suite.

MIT © agentwares contributors — part of the agentwares portfolio.