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

@phyi/mcp

v0.1.0

Published

Model Context Protocol server for Phylax. Lets an assistant verify artifacts before it uses them.

Readme

Phylax MCP Server

A Model Context Protocol server for Phylax. Lets AI assistants verify packages, repositories and other MCP servers before using them.

Phylax MCP exposes the Phylax verification API through the Model Context Protocol, so any MCP aware assistant such as Claude, VS Code Copilot, Cursor or Windsurf can check a package, audit a dependency list, or refuse a risky tool as part of a conversation. It runs locally over stdio, or as a shared HTTP server for a team.

Features

  • Verify a package before the assistant suggests installing it
  • Verify another MCP server before you connect to it
  • Batch verify a whole dependency list in one call
  • Evaluate an artifact against your organization policy
  • Fetch signed attestations as evidence
  • Report the current plan and remaining quota

Install

Requires a Phylax API token. Create one at app.phyi.dev.

Claude Desktop

{
  "mcpServers": {
    "phylax": {
      "command": "npx",
      "args": ["-y", "@phyi/mcp"],
      "env": {
        "PHYLAX_API_TOKEN": "${PHYLAX_API_TOKEN}"
      }
    }
  }
}

| Platform | Config file | | --- | --- | | macOS | ~/Library/Application Support/Claude/claude_desktop_config.json | | Windows | %APPDATA%\Claude\claude_desktop_config.json | | Linux | ~/.config/Claude/claude_desktop_config.json |

Cursor

Same shape, in ~/.cursor/mcp.json for every workspace, or .cursor/mcp.json to scope it to one project.

VS Code

{
  "servers": {
    "phylax": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@phyi/mcp"],
      "env": {
        "PHYLAX_API_TOKEN": "${env:PHYLAX_API_TOKEN}"
      }
    }
  }
}

Reference the token rather than pasting it. A literal token in these files gets committed, screen shared and synced between machines.

Usage

Once connected, ask the assistant to verify something:

Use Phylax to verify pkg:npm/[email protected] before we add it.

Tools exposed

| Tool | Purpose | | --- | --- | | verify_artifact | Verify one package URL and return ALLOW, WARN or BLOCK. | | verify_artifacts | Verify many at once. Preferred for a dependency list. | | verify_mcp_server | Verify another MCP server before connecting to it. | | check_policy | Evaluate an artifact against an organization policy. | | get_attestation | Fetch signed attestations as evidence. | | search_artifacts | Resolve a vague package name to a package URL. | | phylax_status | Reachability, plan and remaining quota. |

A BLOCK verdict is returned as a tool error, not as prose. An assistant that reads "this package is risky" as text will often carry on and use it anyway, so the refusal is made structural.

Self hosting over HTTP

For a team sharing one server rather than spawning one per user:

PHYLAX_API_TOKEN=... \
PHYLAX_MCP_AUTH_TOKEN=... \
npx @phyi/mcp --http --port 8765

The server refuses to start on HTTP without PHYLAX_MCP_AUTH_TOKEN. An unauthenticated MCP endpoint grants tool execution to anyone who can reach the port.

Set PHYLAX_MCP_AUDIENCE to reject tokens minted for a different service, even when they are otherwise valid.

Configuration

| Variable | Default | Notes | | --- | --- | --- | | PHYLAX_API_TOKEN | required | Your Phylax API token. PHYLAX_API_KEY also accepted. | | PHYLAX_API_BASE_URL | https://api.phyi.dev | | | PHYLAX_MCP_TRANSPORT | stdio | Set to http for a shared server. | | PHYLAX_MCP_PORT | 8765 | HTTP only. | | PHYLAX_MCP_AUTH_TOKEN | none | Required for HTTP. | | PHYLAX_MCP_AUDIENCE | none | Expected aud claim on inbound tokens. |

Troubleshooting

The assistant never calls a tool. The client did not start the server. Run the command yourself to see the error the client swallowed:

PHYLAX_API_TOKEN=... npx @phyi/mcp

Every tool reports unauthenticated. The token is missing, malformed or revoked. Ask the assistant to run phylax_status.

Every tool reports plan_required. The capability is not part of the current subscription.

The client shows a broken protocol stream. Something wrote to stdout. On stdio, stdout carries the protocol; all logging goes to stderr.

Development

npm install
npm run typecheck
npm test
npm run build

License

MIT