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

@accountone/mcp

v0.1.3

Published

MCP server for the AccountOne API — exposes status, payment, order, monthly summary and dev-flag endpoints as tools over stdio.

Readme

accountone-mcp

Model Context Protocol server for the AccountOne API.

Lets MCP-capable clients (Claude Desktop, Claude Code, custom agents) read AccountOne business data — account status, payments, orders, monthly bookkeeping reconciliation, and dev flags — over stdio.

Tools

| Tool | Endpoint | Required input | Purpose | | --- | --- | --- | --- | | ao_status | GET /mcp/v1/status | — | Festschreibung (closed payment_matrix and umsatz_matrix), interface health, recent transaction count | | ao_order | GET /mcp/v1/order | source_order_nr | Order line items for a given order number | | ao_payment | GET /mcp/v1/payment | one of matching_source_order_nr, payment_identifier | Payments matched to an order or a payment reference | | ao_order_month_summary | GET /mcp/v1/order_month_summary | jahrmonat (YYYY-MM) | Monthly bookkeeping reconciliation aggregated by VAT, country, marketplace |

All responses are returned as both human-readable JSON text and structured structuredContent validated against the tool's outputSchema.

Configuration

Configured via environment variables in your MCP client config:

| Var | Required | Default | Notes | | --- | --- | --- | --- | | AO_API_TOKEN | yes | — | Bearer token issued by AccountOne. Token shape: <user_id>.<secret>. Generate in the AccountOne UI under "API Tokens". The token must hold the mcp role (or admin) for /mcp/v1/*. |

Install / use

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "accountone": {
      "command": "npx",
      "args": ["-y", "accountone-mcp"],
      "env": {
        "AO_API_TOKEN": "<your-token>"
      }
    }
  }
}

Claude Code

claude mcp add accountone -- npx -y @accountone/mcp

Then set AO_API_TOKEN in the resulting config.

Pointing at staging / dev

{
  "mcpServers": {
    "accountone": {
      "command": "npx",
      "args": ["-y", "accountone-mcp"],
      "env": {
        "AO_API_TOKEN": "<your-dev-token>"
      }
    }
  }
}

Development

npm install
npm run dev            # tsx watch — runs against stdio
npm run build          # emits dist/
npm run typecheck

Quick MCP smoke-test against a live AccountOne backend:

(printf '%s\n' \
  '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"smoke","version":"0"}}}' \
  '{"jsonrpc":"2.0","method":"notifications/initialized","params":{}}' \
  '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"ao_status","arguments":{}}}'; sleep 2) | \
  AO_API_TOKEN=<token> node dist/index.js

Errors

Tool errors bubble up as MCP isError: true results with the AccountOne message, e.g. "Insufficient permissions", "Too Many Requests", "Invalid query parameters". The AccountOne API has a server-wide rate limit of 0.1 req/s per token (one call every ten seconds) — bursts return HTTP 429.

Publish

npm version <patch|minor|major>
npm publish

prepublishOnly runs the TS build. The published tarball ships only dist/, README.md, and LICENSE.

License

Proprietary — Copyright (c) 2026 AccountOne GmbH. All rights reserved. See LICENSE.