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

@procedures/bundle-assistant

v0.46.0

Published

The opt-in tools of the personal assistant for an MCP host: calendar files, mail parsing, places, routes, weather and photo metadata, without the procedures that can carry data out.

Readme

@procedures/bundle-assistant

npm

The opt-in tools of the personal assistant for an MCP host. The bundle has the procedures of @procedures/ics, @procedures/mail, @procedures/geo, @procedures/weather and @procedures/exif.

Use

The dev-tools server of @procedures/mcp-dev-tools loads the bundles of MCP_BUNDLES. Add this bundle to the default bundle:

MCP_BUNDLES=@procedures/bundle-mcp,@procedures/bundle-assistant mark mcp

The tools

| Tool | What it does | |---|---| | ics.parse, ics.occurrences | They read a calendar file and its repeated events. They are pure. | | ics.write | It writes a calendar file from events. It is pure. | | mail.parse | It reads the headers and the text of a message. It is pure. | | geo.geocode, geo.route | They read one public service each. | | geo.distance, geo.geohash | They give the distance between two points and the geohash of a point. They are pure. | | weather.forecast | It reads one public service. | | exif.read | It reads the date and the place of a photo on the host. |

The dev-tools server sends the requests of geo.geocode, geo.route, weather.forecast and ics.fetch through the default host policy of @procedures/http. The policy refuses a baseUrl or a feed on a loopback, private or link-local address.

  • weather.forecast uses the policy in each registry.
  • The export mcpHostModules gives geo and ics with the policy. The dev-tools server gives them to createRegistry() before the bundle, so they replace the default modules.
  • The bundle keeps the default modules of geo and ics. Thus mark and the site load the bundle next to the packages geo and ics.

Another host does the same:

import bundleAssistantModule, { mcpHostModules } from "@procedures/bundle-assistant/module";

const registry = createRegistry(...mcpHostModules, bundleAssistantModule);

These procedures are not tools:

  • ics.fetch fetches any URL, so a tool call can carry data out in the URL.
  • mail.headers reads a private mailbox.
  • notify.send, restic.run and tailscale.run are not in the bundle. The first one posts to any topic of a public server, and the others run destructive commands.

A test pins the list of tools. Each tool changes nothing.