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

@rankveo/cli

v0.1.1

Published

The rankveo command line: rankings, AI visibility, backlinks, articles and prompts for your workspace, plus an MCP bridge for agents.

Downloads

48

Readme

@rankveo/cli

The rankveo workspace from the terminal: rankings, AI visibility, backlinks, PageSpeed, cleared articles and prompt checks, plus an MCP bridge for agents that only speak stdio.

npx @rankveo/cli login          # paste a full-access key from Settings → API keys
npx @rankveo/cli keywords
npx @rankveo/cli analytics geo
npx @rankveo/cli articles list --json | jq '.articles[].slug'

Or install it: npm i -g @rankveo/cli and use rankveo.

Full-access keys come with Premium and Max. Each key belongs to one website; rankveo login once per website and switch with --workspace example.com. RANKVEO_API_KEY in the environment skips the saved key entirely, for CI.

Commands

| Command | What it does | | --- | --- | | login, logout, whoami, workspaces | Save, forget and inspect keys | | analytics seo\|geo\|backlinks | The latest cached snapshot, freshness first | | keywords | Tracked keywords with positions and ranking URLs | | pagespeed [--refresh] | The PageSpeed report; --refresh measures again | | prompts list, prompts run <id> | AI visibility prompts; a run uses quota | | articles list, articles get <id> [--out f] | Cleared articles, in any CMS format | | articles published <id> --platform p --remote-id r | Record where one went live | | preferences get, preferences set k=v … | How articles are written | | mcp, mcp config | MCP over stdio; or the config for HTTP clients |

Every command takes --json for the API response unchanged.

MCP

The workspace is a remote MCP server at https://api.rankveo.com/api/mcp. Clients that take a URL connect to it directly with the key as a bearer token; rankveo mcp config prints that configuration. For a client that can only launch a local process:

{
  "mcpServers": {
    "rankveo": {
      "command": "npx",
      "args": ["-y", "@rankveo/cli", "mcp"],
      "env": { "RANKVEO_API_KEY": "rk_your_key" }
    }
  }
}

The bridge forwards each JSON-RPC line to the API and writes the reply back; nothing runs locally.

Where the key lives

~/.config/rankveo/config.json (or $XDG_CONFIG_HOME/rankveo/, %APPDATA%\rankveo\ on Windows), written mode 0600. Move it with RANKVEO_CONFIG_PATH. Revoke a key from Settings → API keys and every copy of it stops working at once.