Back to Browse

Iss Number MCP Server

Developer ToolsModerate5.6MCP RegistryRemote
Free

Server data from the Official MCP Registry

iss-number MCP — wraps StupidAPIs (keyless — no credential needed)

About

iss-number MCP — wraps StupidAPIs (keyless — no credential needed)

Remote endpoints: streamable-http: https://gateway.pipeworx.io/iss-number/mcp

Security Report

5.6
Moderate5.6Moderate Risk

The iss-number server is a small, keyless wrapper that makes a single read-only HTTPS GET to api.stupidapis.com for an ISS-derived novelty number, with no hardcoded secrets, no shell execution, and no user data sent externally. Its only notable traits are the gateway-wide meta-tools exposed on the hosted endpoint and a large amount of error-handling boilerplate that is more elaborate than the single tool requires, neither of which is a security defect. Supply chain analysis found 5 known vulnerabilities in dependencies (0 critical, 3 high severity).

3 files analyzed · 9 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-pipeworx-io-iss-number": {
      "url": "https://gateway.pipeworx.io/iss-number/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

mcp-iss-number

iss-number MCP — wraps StupidAPIs (keyless — no credential needed)

Part of Pipeworx — an MCP gateway connecting AI agents to 1882+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

ToolDescription
iss_number_generateFetch the ISS's live orbital coordinates and return a number computed from them. No inputs required. Returns a single integer that changes with the ISS position — useful as a space-themed novelty value, not a stable seed.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "iss-number": {
      "url": "https://gateway.pipeworx.io/iss-number/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/iss-number/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1882+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/iss_number_generate \
  -H 'Content-Type: application/json' \
  -d '{}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/iss_number_generate. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "iss-number": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-iss-number"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-iss-number

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Iss Number data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Reviews

No reviews yet

Be the first to review this server!