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

@mcptrail/use-model-tool

v0.1.0

Published

React hooks that register/unregister WebMCP tools with component lifecycle — the agent only sees tools for what's currently on screen.

Readme

@mcptrail/use-model-tool

CI License: MIT

React hooks that bind WebMCP tool registration to component lifecycle. A tool is registered when its component mounts and unregistered when it unmounts — so the AI agent only ever sees the tools for what's currently on screen.

No context provider, no global tool registry to keep in sync with your UI. Register a tool where it makes sense, and React's lifecycle keeps the agent's view honest.

Install

npm install @mcptrail/use-model-tool

react (^18.2.0 || ^19.0.0) is a peer dependency.

Usage

import { useModelTool } from "@mcptrail/use-model-tool";

function CheckoutPanel({ cartId }: { cartId: string }) {
  useModelTool({
    name: "apply_coupon",
    description: "Apply a discount coupon to the current cart",
    inputSchema: {
      type: "object",
      properties: { code: { type: "string" } },
      required: ["code"],
    },
    execute: async (args) => {
      const { code } = args as { code: string };
      return applyCoupon(cartId, code);
    },
  });

  return <div>/* ...checkout UI... */</div>;
}

When CheckoutPanel is mounted, the agent can call apply_coupon. Navigate away and the tool is gone — the agent can no longer call it.

Register several tools from one component with useModelTools:

import { useModelTools } from "@mcptrail/use-model-tool";

function TableTools({ rows }: { rows: Row[] }) {
  useModelTools([
    { name: "sort_table", description: "Sort the visible table", execute: sort },
    { name: "filter_table", description: "Filter the visible table", execute: filter },
  ]);

  return <Table rows={rows} />;
}

API

useModelTool(tool, deps?)

Registers a single tool on mount and unregisters it on unmount. Pass deps to re-register when they change (defaults to [] — register once).

useModelTools(tools, deps?)

Registers every tool on mount and cleans them all up on unmount. Pass deps to re-register the set when they change (defaults to []).

registerModelTool(tool, target?): () => void

The pure, framework-free core the hooks are built on. Resolves the ambient modelContext (prefers target, then navigator, then document), calls registerTool(tool), and returns a cleanup fn:

  • if registerTool returned a disposer, cleanup calls its .unregister();
  • else if the modelContext exposes unregisterTool(name), cleanup calls that;
  • else cleanup is a no-op.

If no modelContext is available, registerModelTool is a no-op and returns a no-op cleanup — safe to call during SSR or in non-WebMCP browsers.

WebMcpTool

interface WebMcpTool {
  name: string;
  description?: string;
  inputSchema?: JSONSchema;
  annotations?: { readOnlyHint?: boolean; [k: string]: unknown };
  execute: (args: unknown) => unknown;
}

Development

npm install
npm run typecheck
npm test          # Vitest + jsdom
npm run build     # tsup → dist (ESM + CJS + d.ts)

License

MIT © Zied Guetari