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

marlo-mcp

v0.1.0

Published

MCP server that audits a web page for SEO and AI-readiness issues with Marlo, the open-source AI CMO.

Readme

marlo-mcp

An MCP server that lets Claude, Cursor and other AI assistants audit a web page for SEO and technical issues with Marlo, the open-source AI CMO.

Ask your assistant things like:

  • "Audit https://mysite.com and tell me what to fix first."
  • "Check this page before I ship it."

It has one tool, audit_site. It is read-only: it fetches the page and changes nothing. It checks one page, and returns the top findings, each with evidence, why it matters and a concrete fix.

Install

Add it to your MCP client. For Claude Desktop, Cursor, Windsurf and similar clients:

{
  "mcpServers": {
    "marlo": {
      "command": "npx",
      "args": ["-y", "marlo-mcp"]
    }
  }
}

For Claude Code: claude mcp add marlo -- npx -y marlo-mcp

Requires Node.js 20 or newer.

Use your own Marlo server

By default the tool calls the hosted Marlo at https://app.marlo.mlforge.in, which rate limits public audits. To use your own self-hosted Marlo instead:

| Variable | Purpose | |---|---| | MARLO_BASE_URL | Your server, for example http://localhost:3000 | | MARLO_ACCESS_PASSWORD | Your server's MARLO_ACCESS_PASSWORD, if you set one. It is only ever sent to MARLO_BASE_URL, never to the hosted app. |

{
  "mcpServers": {
    "marlo": {
      "command": "npx",
      "args": ["-y", "marlo-mcp"],
      "env": { "MARLO_BASE_URL": "http://localhost:3000" }
    }
  }
}

What it sends

Only the page address you ask about, to Marlo's public audit endpoint. No API keys, files or conversation text leave your machine. Private and local addresses are refused by the server.

Limits

  • One page per call, and the top three findings. The full product tracks findings over time, checks AI readiness (GEO), reads Search Console and opens draft fix PRs on GitHub.
  • The hosted endpoint is rate limited. If you hit the limit, the tool says so and when to retry.

Development

npm install
npm test
node bin/marlo-mcp.mjs   # speaks MCP over stdio

License: AGPL-3.0, same as Marlo.