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

@zero-ar/mcp

v0.5.0

Published

Expose reviewed Zero-AR work to MCP clients and import bounded MCP capabilities.

Readme

@zero-ar/mcp

Expose reviewed Zero-AR work to MCP clients without creating a second owner of that work. The package also discovers MCP peers and compiles bounded tool or resource imports for a separate admission decision.

The native Zero-AR API still owns every run, task, quality decision, effect, artifact and cancellation. MCP discovery grants no capability, and a remote peer's result remains a peer claim until native validators establish the local result.

A recorded Zero-AR run showing the durable state that remains behind an MCP entrypoint.

Install

Node.js 24.11.0 through the Node 24 LTS line is required.

npm install @zero-ar/mcp @zero-ar/client @zero-ar/contracts

First working example

Compile one published work entrypoint and mount the MCP handler behind an authenticated application boundary. The request body cannot choose its tenant or replace the tenant-bound native client.

import { ZeroARClient } from '@zero-ar/client';
import {
  compileMcpPublishedWorkEntrypoint,
  contentHash,
} from '@zero-ar/contracts';
import { createZeroARMcpServer } from '@zero-ar/mcp';

const entrypoint = compileMcpPublishedWorkEntrypoint({
  name: 'research-report',
  title: 'Research report',
  description: 'Produce a cited research report.',
  publication_ref: contentHash({ publication: 'research-agent-1.0.0' }),
  agent_ref: contentHash({ agent: 'research-agent-1.0.0' }),
  accountable_principal: 'operator:research',
  input_schema: {
    type: 'object',
    properties: {
      objective: { type: 'string', maxLength: 10_000 },
    },
    required: ['objective'],
    maxProperties: 1,
    additionalProperties: false,
  },
  output_schema: {
    type: 'object',
    properties: {},
    maxProperties: 8,
    additionalProperties: true,
  },
  default_budgets: {
    model_tokens: 50_000,
    tool_calls: 100,
    attention: 2,
    verification_reserve_fraction: 0.2,
    max_turns: 12,
  },
  mcp_visible: true,
  assurance_extension_required: true,
});

const native = new ZeroARClient(process.env.ZERO_AR_URL!, {
  headers: {
    authorization: `Bearer ${process.env.ZERO_AR_API_KEY}`,
  },
});

const mcp = createZeroARMcpServer({
  tenant: 'tenant-research',
  binding_ref: contentHash({ binding: 'research-mcp-v1' }),
  entrypoints: [entrypoint],
});

export async function handleMcpRequest(
  request: Request,
  principal: string,
): Promise<Response> {
  return mcp.fetch(request, {
    tenant: 'tenant-research',
    principal,
    native,
  });
}

Call mcp.close() when the surrounding server stops. The handler stores no run state, so rebuilding it does not replace or lose a native task.

Public surface

Serve reviewed work

createZeroARMcpServer serves MCP 2026-07-28 and the Tasks extension. It lists only the supplied published entrypoints. A tool call creates a deferred native run with the caller's idempotency key. Task reads, answers, cancellation, results and notifications resolve from the tenant-bound native client.

Discover and import peer capabilities

discoverMcpPeer requires two deployment-owned ports:

  • A credential resolver that receives a secret:// reference for each request and returns the current bearer value.
  • An egress port that sends the bounded request through the deployment's network policy.

Discovery returns an immutable McpPeerSnapshot. Use compileMcpToolImport or compileMcpResourceImport to create a dry-run native publication plan. A reviewer chooses operation class and authority. Only admitMcpToolImport or admitMcpResourceImport attaches an admission ref.

Prompt import is omitted. Peer prompts never become agent instructions or skills.

What this does not establish

MCP remains a bounded work-entrypoint adapter. It is not a second runtime and does not grant effect authority. Product backends use the native API for tenant administration, runtime artifact upload, external observations, complete audit reads and effect decisions. A generic MCP task answer cannot stand in for an independently authorized effect decision or dispatch receipt.

Where to go next