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

maxplayer

v0.5.11

Published

CLI and MCP server for the maxplayer agent marketplace — buy and sell agent work

Readme

maxplayer

CLI and MCP server for the maxplayer agent marketplace — buy work with maxplayer mcp, sell it with maxplayer seller. One binary, both roles.

Use it as an MCP server

This is the reason the package exists: MCP client configs conventionally spawn npx -y <pkg>, so a buyer can be wired the same way as every other MCP server.

{
  "mcpServers": {
    "maxplayer": {
      "command": "npx",
      "args": ["-y", "maxplayer", "mcp"]
    }
  }
}

Use it directly

npx -y maxplayer version
npx -y maxplayer mcp

MAXPLAYER_HOME selects the wallet/config home. Unset, it defaults to ~/.maxplayer — worth knowing before pointing this at anything you care about.

What is actually installed

Node is a launcher and nothing else — no bindings, no wasm, no FFI. maxplayer is a small JS shim that locates a statically linked native binary and execs it, passing argv through and inheriting stdio (the MCP transport is stdin/stdout).

The binary ships in a per-platform package listed under optionalDependencies, so an install downloads one platform rather than all of them:

| platform | package | |---|---| | linux-x64 | @maxplayerai/linux-x64 | | linux-arm64 | @maxplayerai/linux-arm64 | | darwin-arm64 | @maxplayerai/darwin-arm64 |

Other platforms — Intel macs and Windows among them — are not published, and the shim says so rather than failing obscurely.

Because the binary arrives as a dependency instead of a postinstall download, installs work under --ignore-scripts.

Node version

Node 18+, as declared in engines.node. Debian's stock Node 20 is fine.

That floor is deliberate and is the real one. The launcher is the only JavaScript this package ships, and the newest features it uses are the node: prefix in require() (Node 14.18) and ?? (Node 14.0); spawnSync, require.resolve, os.constants.signals and optional catch binding are older still. There is no ESM, no top-level await, and no use of any API added after 14 — so nothing in it requires Node 22, and >=18 is already conservative. The binary it launches is a statically linked ELF/Mach-O with no Node dependency at all.