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

@randomfact/taz-mcp

v0.1.0

Published

Model Context Protocol server for the Transaction Analyzer API. OAuth 2.0 + PKCE; tools derived at startup from the published OpenAPI spec.

Downloads

18

Readme

@randomfact/taz-mcp

Model Context Protocol server for the Transaction Analyzer. Lets an MCP-aware client — Claude Desktop, Claude Code, MCP Inspector, anything that speaks MCP — read your transactions and create or edit categorization rules on your behalf.

Add one line to your MCP client config. The first time a tool needs data, the server pops your default browser to sign in with Google; once you've signed in, tokens are cached locally and the chat just keeps going.

Install

Claude Desktop

Add to claude_desktop_config.json (%APPDATA%\Claude\ on Windows, ~/Library/Application Support/Claude/ on macOS, ~/.config/Claude/ on Linux):

{
  "mcpServers": {
    "transaction-analyzer": {
      "command": "npx",
      "args": ["-y", "@randomfact/taz-mcp"]
    }
  }
}

Quit and reopen Claude Desktop (in-app reload won't pick up edits). Ask the chat "list my transaction categories". A browser tab pops on the first tool call, sign in with Google, the chat continues.

Claude Code

Register the server with claude mcp add. Scope it to your user so it's available in every project:

claude mcp add transaction-analyzer --scope user -- npx -y @randomfact/taz-mcp

(Drop --scope user to limit it to the current project, or use --scope project to write a .mcp.json you can check into your repo.)

In a new Claude Code session, run /mcp to confirm transaction-analyzer is connected, then ask the agent something. Same flow: browser pops once, you sign in, the chat continues with results.

Other MCP clients

Anything that follows the MCP stdio transport protocol works the same way — point it at npx -y @randomfact/taz-mcp with no other configuration.

Headless / SSH

For environments without a browser (SSH, containers, CI), pass --manual-code:

npx -y @randomfact/taz-mcp --manual-code

The CLI prints the authorize URL to stderr — open it on any machine with a browser, sign in, then paste the resulting code on stdin.

Token cache

After the first sign-in, your access + refresh tokens are persisted to:

| Platform | Path | |---|---| | Linux | $XDG_CONFIG_HOME/transaction-analyzer-mcp/tokens.json (defaults to ~/.config/...) | | macOS | ~/Library/Application Support/transaction-analyzer-mcp/tokens.json | | Windows | %APPDATA%\transaction-analyzer-mcp\tokens.json |

The file is chmod 0600 on POSIX. Delete it to force a fresh sign-in — useful if you've signed in with the wrong Google account.

What's NOT available via MCP

By design, two REST surfaces are not exposed as MCP tools:

  • File upload (CSV / PDF bank statements). Upload via the SPA at https://transaction-analyzer-prod.web.app.
  • CSV report download. Use the SPA's export menu, or call the list- transactions tool and format the rows yourself.

Everything else — list / create / update / delete categories and rules, search and override transactions, preview a rule, fetch the uncategorized report — is available as a tool. Your MCP client's tool picker shows the live list.