Science

Official registry Other

Science MCP — free science data APIs

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http science 'https://gateway.pipeworx.io/science/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "science": {
            "type": "http",
            "url": "https://gateway.pipeworx.io/science/mcp"
        }
    }
}
NPM package @pipeworx/mcp-science
Claude Code
claude mcp add science -e 'PIPEWORX_API_KEY=<your pipeworx_api_key>' -- npx -y @pipeworx/mcp-science@0.2.0
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "science": {
            "command": "npx",
            "args": [
                "-y",
                "@pipeworx/mcp-science@0.2.0"
            ],
            "env": {
                "PIPEWORX_API_KEY": "<your pipeworx_api_key>"
            }
        }
    }
}

Environment variables

  • PIPEWORX_API_KEY secret Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. mcp-science
  2. Tools
  3. Quick Start
  4. No MCP client? Call it over HTTP
  5. Standalone (no gateway account)
  6. Using with ask_pipeworx
  7. More
  8. License

mcp-science

Science MCP — free science data APIs

Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.

Tools

ToolDescription
get_iss_locationFetch the International Space Station's current latitude, longitude, and Unix timestamp from the Open Notify API. No inputs required; returns a real-time position fix.
get_earthquakesRetrieve up to 20 globally recent earthquakes from the USGS FDSN service, filtered by lookback period (1–30 days, default 1) and minimum magnitude (default 4.0). Returns magnitude, location name, depth (km), coordinates, time, and tsunami warning flag.
get_air_qualityCheck current air quality at a latitude/longitude. Returns US AQI score and category plus PM2.5, PM10, ozone, NO2, and CO levels.
get_apodGet NASA's Astronomy Picture of the Day with image URL, title, and explanation. Optionally specify a date (e.g., '2024-01-15').

Quick Start

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

{
  "mcpServers": {
    "science": {
      "url": "https://gateway.pipeworx.io/science/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/science/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 1683+ 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/get_iss_location \
  -H 'Content-Type: application/json' \
  -d '{}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/get_iss_location. 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": {
    "science": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-science"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-science

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 Science data" })

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

More

License

MIT

Frequently asked questions

What is Science?

Science MCP — free science data APIs

How do I install Science?

It runs as a remote server. In Claude Code: claude mcp add --transport http science 'https://gateway.pipeworx.io/science/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Science need an API key?

Yes. It expects PIPEWORX_API_KEY, which you set in its configuration.

Is Science open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Science?

It is published by pipeworx-io. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.