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

@limitrum/mcp-server

v0.1.7

Published

MCP server exposing Limitrum policy verification as an agent tool.

Readme

@limitrum/mcp-server

MCP server and local HTTP gateway for Limitrum policy verification.

Use it with Claude Desktop, Claude Code, Cursor, and other MCP-compatible clients to put Limitrum before sensitive tool execution.

Use it as the guard step in an MCP gateway:

MCP-compatible agent -> limitrum_guard -> sensitive tool

If the verdict is blocked, the sensitive tool should not be called.

It also exposes protected tools that perform the guard step internally:

  • limitrum_guard: verify any proposed intent.
  • limitrum_http_fetch: protected HTTP fetch.
  • limitrum_shell_exec: protected shell command.
  • limitrum_github_create_issue: protected GitHub issue creation.
  • limitrum_stripe_create_charge: protected Stripe charge dry-run.
pnpm add @limitrum/mcp-server
pnpm --filter @limitrum/mcp-server dev

Claude Desktop / Cursor config:

{
  "mcpServers": {
    "limitrum": {
      "command": "limitrum-mcp-server",
      "args": [],
      "env": {
        "LIMITRUM_MCP_AGENT_ID": "agent_local"
      }
    }
  }
}

Protected tools are dry-run by default. Explicit execution flags:

LIMITRUM_MCP_ENABLE_NETWORK=true
LIMITRUM_MCP_ENABLE_SHELL=true
LIMITRUM_MCP_ENABLE_GITHUB=true
GITHUB_TOKEN=...

Stripe remains dry-run in the public MCP server. Wrap your own real Stripe call with guardTool() when you want production execution.

SSE mode:

pnpm --filter @limitrum/mcp-server dev:sse

HTTP gateway mode is exposed by the same SSE server:

pnpm gateway:dev

Endpoints:

  • GET /health
  • GET /v1/openapi.json
  • POST /v1/verify-intent
  • GET /sse
  • POST /messages?sessionId=...

Verify an intent:

curl -s http://localhost:8788/v1/verify-intent \
  -H "Content-Type: application/json" \
  -d '{"intent":{"agentId":"agent_local","action":"fetch","target":"api.unknown-exfil.io","amount":1}}'

Set LIMITRUM_GATEWAY_API_KEY to require X-Limitrum-API-Key or Authorization: Bearer ....

See the main repository README for the full runtime-boundary workflow. See docs/AGENT_TOOL_FIREWALL.md for the product-level gateway pattern. See docs/HOSTED_GATEWAY.md for the HTTP gateway path. See docs/USE_WITH_AGENT_STACK.md for Claude/Cursor/provider setup.