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

mcp-multi-protocol-test

v0.1.0

Published

MCP server to test REST, GraphQL, gRPC, and WebSocket endpoints in batch.

Readme

mcp-multi-protocol-test

Node.js MCP server package for testing REST, GraphQL, gRPC (unary), and WebSocket endpoints in one batch.

Features

  • Batch execution across mixed protocols
  • Automatic protocol detection for each test case
  • Per-test status code and normalized status
  • Authentication support:
    • Headers
    • Bearer token
    • Cookies
    • gRPC metadata
  • Equivalent command output:
    • curl
    • grpcurl
    • wscat
    • websocat
  • Optional OpenAPI discovery tool from Swagger/OpenAPI URL
  • Auto-shutdown after batch completion (default behavior)

Install

npm install mcp-multi-protocol-test

Use As MCP Server

This package is a stdio MCP server. MCP clients should run it as a command.

Option 1: Use with npx (recommended)

npx -y mcp-multi-protocol-test

Use this in your MCP client config:

{
  "mcpServers": {
    "multi-protocol-test": {
      "command": "npx",
      "args": ["-y", "mcp-multi-protocol-test"]
    }
  }
}

Option 2: Use after global npm install

npm install -g mcp-multi-protocol-test
mcp-multi-protocol-test

Use this in your MCP client config:

{
  "mcpServers": {
    "multi-protocol-test": {
      "command": "mcp-multi-protocol-test",
      "args": []
    }
  }
}

Option 3: Use local source (development)

From this project folder:

npm install
npm run build
node dist/index.js

Use this in your MCP client config while developing locally:

{
  "mcpServers": {
    "multi-protocol-test-local": {
      "command": "node",
      "args": ["D:/code/node/multi-protocol-test/dist/index.js"]
    }
  }
}

Test In MCP Inspector

Run Inspector:

npx @modelcontextprotocol/inspector

Then configure server command as one of:

  • npx -y mcp-multi-protocol-test
  • mcp-multi-protocol-test
  • node dist/index.js

After connection, call tools:

  • run_batch_tests
  • discover_openapi

Build

npm run build

Run MCP server (stdio)

npm run dev

or after build:

npm start

MCP Tools

run_batch_tests

Runs one batch request containing one or more tests.

Example input:

{
  "autoShutdown": true,
  "concurrency": 2,
  "defaults": {
    "timeoutMs": 20000,
    "headers": {
      "x-env": "dev"
    }
  },
  "tests": [
    {
      "id": "rest-1",
      "url": "https://jsonplaceholder.typicode.com/posts/1",
      "protocol": "auto",
      "method": "GET"
    },
    {
      "id": "graphql-1",
      "url": "https://countries.trevorblades.com/",
      "query": "query { country(code: \"IN\") { name capital } }"
    },
    {
      "id": "grpc-1",
      "url": "grpc://localhost:50051",
      "protocol": "grpc",
      "rpcMethod": "helloworld.Greeter/SayHello",
      "protoFile": "./protos/helloworld.proto",
      "body": {
        "name": "world"
      },
      "grpcMetadata": {
        "x-tenant": "acme"
      }
    },
    {
      "id": "ws-1",
      "url": "wss://echo.websocket.events",
      "protocol": "websocket",
      "ws": {
        "message": {
          "hello": "world"
        },
        "expectContains": "hello",
        "timeoutMs": 5000
      }
    }
  ]
}

discover_openapi

Extracts endpoints from a Swagger/OpenAPI URL.

Example input:

{
  "specUrl": "https://petstore3.swagger.io/api/v3/openapi.json"
}

Output shape

Each test result includes:

  • protocol
  • detectedBy
  • status
  • statusCode
  • statusMessage
  • durationMs
  • timestamp
  • responseBody or errors
  • command equivalents

NPM publish

  1. Update package version.
  2. Build and test.
  3. Dry run package.
  4. Publish.
npm run build
npm test
npm pack
npm publish --access public

Notes

  • gRPC support is unary request/response in this version.
  • Private/internal targets are allowed by default.
  • Auto-shutdown is enabled by default after each batch run.