Nasa Tle Mcp

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

NASA TLE satellite orbital data via tle.ivanstanojevic.me.

VerifiedSTDIODesktop onlyLocation & Lifestyle

Overview

AI-generated overview

A local MCP server that gives an assistant access to NASA TLE satellite orbital data through the tle.ivanstanojevic.me service.

What you can do
Retrieve NASA TLE satellite orbital data from the tle.ivanstanojevic.me service for use in an assistant conversation. The manifest lists no individual tools, so the exact operations are not documented; expect lookups of satellite orbital element data rather than analysis or visualization.
When to use it
Useful when you want an assistant to pull satellite orbital element (TLE) data from the tle.ivanstanojevic.me service during a conversation, for example to look up a satellite's current orbital parameters.
Requirements
Runs as a local process on the user's machine, installed from the npm package nasa-tle-mcp over stdio, so a Node.js runtime is needed. It declares no authentication, environment variables or headers. Network access to the tle.ivanstanojevic.me service is implied by the description.
Before you install
The server depends on a third-party data service, so requests and any query terms go to that service and availability depends on it. No credentials are declared. The manifest lists no tools, so review what it actually exposes before relying on it.

Installation

In SourceWeft

  1. Open Nasa Tle 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.