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

@arbiterlabs/mcp

v0.1.1

Published

MCP server exposing Arbiter judgment tools to any MCP-capable agent.

Readme

@arbiterlabs/mcp

Judgment tools for any MCP-capable agent — Claude Code, Claude Desktop, OpenClaw, or your own host.

Lets a model check whether an action is safe before taking it, rather than finding out afterwards.

Setup

// claude_desktop_config.json, or .mcp.json
{
  "mcpServers": {
    "arbiter": {
      "command": "npx",
      "args": ["-y", "@arbiterlabs/mcp"],
      "env": {
        "ARBITER_URL": "https://arbiter-hs23.onrender.com",
        "ARBITER_PRIVATE_KEY": "base64-64-byte-algorand-key",
        "ARBITER_MAX_SPEND_USD": "10"
      }
    }
  }
}

Tools

| Tool | Does | Cost | |---|---|---| | judge_transaction | Is this transaction safe to sign? | $0.002 | | judge_counterparty | Is this address who I think it is, and can it receive? | $0.01 | | judge_human | What would a person say about this? | $0.25 | | retrieve_human_verdict | Collect a human answer already paid for | free | | arbiter_budget | How much has been spent this session | free |

Verdicts come back as readable text with the decision first and every finding explained, because that text is what the model reasons over.

Configuration

| Variable | Default | | |---|---|---| | ARBITER_URL | http://localhost:4021 | Deployment to call | | ARBITER_PRIVATE_KEY | — | Base64 Algorand key used to pay | | ARBITER_MAX_SPEND_USD | 25 | Lifetime cap for this process | | ARBITER_MAX_PRICE_PER_CALL | 1.00 | Per-call cap |

Paying

Calls are settled per request in USDC on Algorand over x402. There is no API key and no account — payment is the authentication.

Your payer account needs USDC and must be opted in to the USDC asset. On Algorand a transfer to an account that has not opted in is rejected outright, so an un-opted-in payer cannot pay at all. Fees are sponsored by the facilitator, so the payer does not need ALGO.

| Route | Price | |---|---| | Transaction verdict | $0.002 | | Counterparty verdict | $0.01 | | Human judgment | $0.25 |

Full documentation: https://arbiter-hs23.onrender.com/docs

Licence

MIT