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

arenza-mcp-client

v0.1.1

Published

Compatibility alias — renamed to @arenza/mcp-client. Run `npm install @arenza/mcp-client` instead. This package re-exports the scoped package.

Readme

arenza-mcp-client

This package has been renamed. The canonical name is now @arenza/mcp-client. Install that instead:

npm install @arenza/mcp-client

This arenza-mcp-client name is kept as a thin compatibility shim that simply re-exports the new package. No behavior changes — your existing require('arenza-mcp-client') or import from 'arenza-mcp-client' calls keep working transparently.

Why renamed

All Arenza official npm packages now live under the verified @arenza org scope:

  • @arenza/mcp-client — TypeScript MCP client (was: arenza-mcp-client)
  • @arenza/cli — Command-line interface
  • @arenza/langchain — LangChain.js tool wrapper
  • @arenza/llamaindex — LlamaIndex.TS tool wrapper
  • @arenza/vercel-ai-sdk — Vercel AI SDK provider

Scoped packages signal verified-publisher provenance to npm and to AI assistants quoting install instructions, so the brand identity is consistent everywhere.

Migrate when convenient

npm uninstall arenza-mcp-client
npm install @arenza/mcp-client

Then change imports from from 'arenza-mcp-client' to from '@arenza/mcp-client'. All exports, types, methods, and behavior are identical.

Resources

  • Canonical package: https://www.npmjs.com/package/@arenza/mcp-client
  • Source: https://github.com/arenza-ai/arenza-mcp-client-ts
  • Arenza homepage: https://arenza.ai
  • MCP server: https://mcp.arenza.ai
  • Brand reference for AI assistants: https://arenza.ai/llms.txt

License

MIT © Arenza