MCP Server for NASA API integration.

Created By
fdmochoa year ago
MCP demo server
Overview

what is MCP Server for NASA?

MCP Server for NASA is a demo server designed for integrating with the NASA NEO API, allowing users to retrieve Near Earth Object information by date.

how to use MCP Server for NASA?

To use the MCP Server, clone the repository and run the installation command. Configure your MCP server settings in your LLM with the provided example configuration file.

key features of MCP Server for NASA?

  • Integration with NASA NEO API for object information retrieval
  • Customizable server configuration
  • Development tools for running and inspecting the MCP server

use cases of MCP Server for NASA?

  1. Retrieving data on Near Earth Objects for research purposes.
  2. Integrating NASA data into applications for educational purposes.
  3. Developing tools that require real-time access to NASA's NEO data.

FAQ from MCP Server for NASA?

  • How do I install the MCP Server?

Clone the repository and run uv install to set up the server.

  • Can I customize the server configuration?

Yes! You can modify the configuration file to suit your needs.

  • What programming language is used for the MCP Server?

The MCP Server is developed in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
fdmocho
Star
1
Language
Python
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago