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

graylog-mcp-fix

v1.0.0

Published

Local MCP proxy for Graylog — fixes schemas and response data for standard MCP client compatibility

Readme

graylog-mcp-fix

A local MCP proxy that sits between your AI client and a Graylog MCP server, fixing schema and response compatibility issues that prevent standard MCP clients from working with Graylog's API.

Why

Graylog's MCP implementation has several issues that cause MCP clients to reject its responses:

  • Output schemas contain $ref/$defs references that clients cannot resolve
  • datarows are returned as arrays-of-arrays instead of arrays-of-objects
  • effective_timerange.from/.to are returned as primitives but schemas require objects
  • Optional object fields (e.g. unit) are returned as null but schemas lack null support

This proxy transparently fixes all of these on the fly.

Setup

npm install

Create a .env file in the project root:

GRAYLOG_TOKEN=your_api_token_here
GRAYLOG_MCP_URL=https://your-graylog-instance/api/mcp

The token is used as HTTP Basic Auth: Authorization: Basic base64(token:token).

Running

node index.js

MCP client configuration

For opencode (~/.config/opencode/opencode.json):

{
  "mcp": {
    "graylog": {
      "type": "local",
      "command": "node /path/to/graylog-mcp-fix/index.js",
      "enabled": true,
      "environment": {
        "GRAYLOG_MCP_URL": "Graylog MCP endpoint URL",
        "GRAYLOG_TOKEN": "Graylog API token"
      }
    }
  }
}

Environment variables

| Variable | Default | Description | |---|---|---| | GRAYLOG_TOKEN | (empty) | Graylog API token | | GRAYLOG_MCP_URL | (built-in URL) | Graylog MCP endpoint URL |