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

@orrery-labs/mcp

v0.1.0

Published

Local stdio MCP bridge for Orrery prediction-market intelligence.

Readme

@orrery-labs/mcp

Local stdio MCP bridge for Orrery.

Use this package when an MCP client prefers launching a local server process instead of connecting directly to Orrery's remote HTTP endpoint.

The bridge is intentionally thin:

Claude / Cursor / local agent
        ↓ stdio MCP (Content-Length framed JSON-RPC)
@orrery-labs/mcp
        ↓ HTTPS JSON-RPC
https://orrery.me/api/mcp/v1
        ↓
Orrery x402/API-credit tools

It does not duplicate Orrery taxonomy, pricing, Kalshi, alert, or signal logic. All tool calls are forwarded to the canonical remote MCP endpoint.

Install

npx @orrery-labs/mcp

Claude Desktop

{
  "mcpServers": {
    "orrery": {
      "command": "npx",
      "args": ["-y", "@orrery-labs/mcp"],
      "env": {
        "ORRERY_API_KEY": "orrery_live_..."
      }
    }
  }
}

Cursor

{
  "mcpServers": {
    "orrery": {
      "command": "npx",
      "args": ["-y", "@orrery-labs/mcp"],
      "env": {
        "ORRERY_API_KEY": "orrery_live_..."
      }
    }
  }
}

Configuration

| Env var | Default | Purpose | |---|---|---| | ORRERY_MCP_URL | https://orrery.me/api/mcp/v1 | Remote MCP endpoint | | ORRERY_API_KEY | unset | Orrery API-credit key, forwarded as X-Orrery-API-Key | | ORRERY_X_PAYMENT | unset | x402 payment proof, forwarded as X-PAYMENT | | ORRERY_PAYMENT_SIGNATURE | unset | x402 payment proof, forwarded as PAYMENT-SIGNATURE | | ORRERY_MCP_STDIO_FRAMING | content-length | Use newline only for local smoke tests |

CLI flags mirror the env vars:

orrery-mcp --url https://orrery.me/api/mcp/v1 --api-key orrery_live_...

For quick shell smoke tests that send one JSON-RPC object per line:

ORRERY_MCP_STDIO_FRAMING=newline orrery-mcp --url http://localhost:3000/api/mcp/v1

Safety

Orrery is read-only. The MCP bridge exposes intelligence tools, resources, and prompts. It does not trade, submit orders, connect to Polymarket/Kalshi accounts, read private positions, or provide buy/sell recommendations.