Jpl Fireball Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 24, 2026

Fireball impact data from NASA JPL. No key required.

VerifiedSTDIODesktop onlyData & Analytics

Overview

AI-generated overview

A local MCP server that gives an assistant access to NASA JPL fireball impact data, with no API key required.

What you can do
Provides fireball impact data sourced from NASA JPL for the assistant to look up and discuss. No tool list is published, so the exact queries and outputs are not documented. Runs as a local process on the user's machine.
When to use it
Useful when you want an assistant to reference NASA JPL fireball impact information, for example in casual research or educational questions about meteor and fireball events.
Requirements
Runs as a local process installed from the npm package jpl-fireball-mcp over stdio, so Node.js and npm are needed. No API key, environment variables or headers are declared.
Before you install
The tool list and data fields are undocumented, so verify what it returns before relying on it. Data comes from a third party (NASA JPL) and may be incomplete or out of date.

Installation

In SourceWeft

  1. Open Jpl Fireball Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.