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

@webmcp-today/schema

v0.3.0

Published

Config format for WebMCP Today — zod schemas for community WebMCP tool configs

Readme

@webmcp-today/schema

Zod schemas and TypeScript types for declarative WebMCP Today package documents. Use it to validate package submissions, version bodies, registry responses, and the related API-backed tool format.

Install

npm install @webmcp-today/schema

The package is ESM-only and includes its TypeScript declarations.

Validate a package

createPackageSchema validates a complete package document. It checks package metadata, URL-pattern/domain scope, unique tool names, tool input schemas, and—when present—the API block's endpoint bindings and {{parameter}} references.

import { createPackageSchema } from "@webmcp-today/schema";

const result = createPackageSchema.safeParse({
  version: 1,
  domain: "github.com",
  urlPatterns: ["*://github.com/*"],
  title: "Example search tools",
  description: "Search tools for github.com.",
  api: {
    baseUrl: "https://github.com",
    endpoints: {
      search: {
        method: "GET",
        path: "/api/search",
        query: { q: "{{query}}" },
        returns: "results[].{title: title, url: url}",
      },
    },
  },
  tools: [
    {
      name: "search",
      description: "Search the site.",
      inputSchema: {
        type: "object",
        properties: {
          query: { type: "string", description: "Search query" },
        },
        required: ["query"],
      },
      annotations: { readOnlyHint: true },
      execution: { mode: "api", endpoint: "search" },
    },
  ],
});

if (!result.success) {
  console.error(result.error.issues);
} else {
  const pkg = result.data;
  // `domain` is normalized to lowercase, with a leading `www.` removed.
  console.log(pkg.domain);
}

domain must be a concrete, registrable hostname. Each urlPatterns entry uses a Chrome-extension-style match pattern and must stay within that domain. An API baseUrl must use HTTPS and be on the package domain or one of its subdomains. The only endpoint-level baseUrl exception is Hacker News's anonymous Firebase read API; it cannot use auth, and the executor omits cookies.

API overview

All public values are exported from the package root.

  • Package schemas and types: createPackageSchema, createPackageObjectSchema, updatePackageMetaSchema, publishVersionSchema, publishVersionSchemaForDomain, CreatePackageInput, UpdatePackageMetaInput, and PublishVersionInput.
  • Tool and input schemas: toolDescriptorSchema, inputSchemaSchema, executionDescriptorSchema, apiExecutionSchema, plus their inferred types. Tool execution currently supports execution: { mode: "api", endpoint }.
  • API format: apiBlockSchema, apiEndpointSchema, apiAuthSourceSchema, apiGraphqlSchema, collectApiIssues, and the ApiBlock/ApiEndpoint types. Endpoints can declare a method, path, query, one request-body form (body, form, or graphql), optional JMESPath returns, error locators, and named auth sources.
  • Registry and bridge wire schemas: webMcpPackageSchema, response schemas such as packageLookupResponseSchema, bridgeRequestSchema, and local-bridge request/response schemas.
  • Utilities and constants: URL-pattern parsing/matching helpers including matchUrlPattern and rankPackagesByUrl; unknownPlaceholders; canonicalizeApiBlock and apiContentHash; and limits such as TOOL_NAME_MAX, TOOL_DESCRIPTION_MAX, and ENGINE_VERSION.

For exact field constraints and all exports, see the source and the API-backed package-format documentation.

License

MIT