Skip to main content
Glama
298,560 tools. Last updated 2026-07-14 15:09

"Spaceflight API - Space Launch and Mission Data" matching MCP tools:

  • Fetch 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.
    Connector
  • Search US nonprofits by mission category and state. Returns up to 25 results with revenue, assets, and health scores (0–100). Category maps to NTEE codes: education, healthcare, arts, environment, human_services, civil_rights, international, religion, science, sports. Raw NTEE letter (A–Z) also accepted. Uses ProPublica Nonprofit Explorer API. Rate limit: 30/minute. No auth required. Starting point for nonprofit due diligence — follow with nonprofit_fetch_nonprofit_full_profile for deep dive on a specific EIN. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="nonprofit_search_nonprofits_by_category", intended_query="{what the user needed}", gap_description="{what was missing or wrong in the result}".
    Connector
  • REQUIRED FIRST CALL. Returns Mission gate status, version, action classes, and the agent_instructions you MUST follow for the rest of this session: gate every consequential action through request_approval and never proceed without mission_check_approval returning decision=approved. Call this once at the start of every conversation.
    Connector
  • Query the verified FCC satellite licensing docket — every space-station (SAT) filing in the FCC's own daily IBFS database dump, back to the 1960s — by applicant, application type, status, and filing date. Use this for "who is authorized to operate what in orbit, what has been filed, and where does each filing stand" questions — the satellite-buildout licensing pipeline. Each filing carries the FCC's public filing key (`file_number`, e.g. "SATLOA2025061800149"), the `callsign` (e.g. "S3069" = SpaceX Gen2), the application type and status in the FCC's OWN vocabulary — verbatim codes plus the FCC's own decode text from the same dump vintage (`app_type_code` "LOA" = Launch and Operating Authority, "STA" = Special Temporary Authority, "MOD" = Modification; `status_code` "A/C" = Action Complete, "ATPN" = Action Taken Public Notice — codebooks in describe) — the full lifecycle date family (filed / granted / expires / …), the FCC's plain-English `description` of the filing, and the applicant identity (`applicant_name`, the FCC's verbatim registrant, e.g. "Space Exploration Holdings, LLC"). Filter by `applicant_name`, `app_type_code`, `status_code`, `callsign`, `file_number`, `state` (the APPLICANT's address state), `applicant_country`, `report_period` (the filing date) via `report_period_from`/`report_period_to`, or `date_grant`/`date_expire` ranges. Group by any of `applicant_name`, `app_type_code`, `status_code`, `state`, `applicant_country`. Pass each parameter as a top-level key of `params` (flat — not nested under a `filter`, `filters`, or `where` key). Example: `{"applicant_name": "Space Exploration Holdings, LLC", "group_by": ["app_type_code"]}` for one operator's filing mix; `{"report_period_from": "2020-01-01", "group_by": ["applicant_name"], "order_by": "source_record_count", "top_n": 10}` for the most active filers of the 2020s. Returns JSON aggregates with citations and optional row-level records when `include_records` is true — every record cites its exact row in the FCC's dump, re-verifiable via get_source_evidence_v1. THE ENGRAVED BOUNDARY: new-filing intake into IBFS structurally ENDED at the FCC's ICFS system cutover (~mid-2025), and ICFS publishes no bulk data — so filings SUBMITTED after the cutover are not in this docket, and counts near/after 2025 UNDERCOUNT new filing activity (say so when answering; every response carries an icfs_cutover note). Status and lifecycle updates on the filings that ARE here continue to flow daily. A filing is an authorization EVENT: never a satellite count (one NGSO grant can cover thousands of satellites), never an orbital catalog (satellites in orbit are not served here), never launch activity (FAA data, not served here). `state`/`applicant_city` are the APPLICANT's mailing address — satellites are not in states. Earth stations (SES) and non-satellite FCC dockets are out of scope. The one measure is `source_record_count` (filings in scope).
    Connector
  • Find grantmakers that have ACTUALLY funded organizations LIKE the caller's, using the real 7.5M-edge who-funds-whom grant graph (IRS 990-PF, 2022-2026). This is the strongest free-tier prospecting move: collaborative-filtering peer prospecting, distinct from search_funders (name/topic lookup) and search_open_grants (active RFPs). HOW IT WORKS: for each peer organization, it looks up every foundation that granted to that peer, then merges funders across peers. A funder that gave to several of your peers ranks highest. Every result carries real grant evidence — which peers the funder funded and for how much. INPUTS (provide one): - peer_orgs (PREFERRED): names or 9-digit EINs of organizations LIKE the one you're raising for — peers, aspirational orgs, or orgs with a similar mission. The graph is keyed by recipient EIN, so naming real peers yields the sharpest evidence. Up to 12 are used. - org_description: a plain-language description of the nonprofit (mission, cause, who it serves). Fallback that resolves well-funded peers by keyword over the IRS BMF; prefer peer_orgs when you can name a few peers. RECOMMENDED WORKFLOW: establish the org's mission/cause, then name 2-5 peer organizations and call this tool. Deepen any candidate with get_funder_profile / get_foundation_grants (pass the returned ein).
    Connector

Matching MCP Servers

  • A
    license
    -
    quality
    B
    maintenance
    Enables AI tools like Claude Code to deploy projects to multiple servers via SSH with zero installation on target machines. Supports server onboarding, project management, and one-click deployment through MCP tools.
    Last updated
    10
    1
    AGPL 3.0

Matching MCP Connectors

  • SESSION-RECOVERY · FIRST CALL when a session starts and the user mentions launch / users / growth / customers / metrics / revenue / marketing / what next / shipping. Returns a command-center bootCard with `headline`, `priority`, `cards[]` (each carries kind + label + literal user command + runHandle), and `next` (the one-line prompt). Aggregates: pending approvals + ripe measurements + new engagement + queued prospects + recent launches + manual-publish-pending actions. ChiefLab is stateful and re-summonable — even if the conversation was lost, the IDE was switched, or the runId was forgotten, this call recovers the workspace business state. If the user asked to launch the CURRENT repo, compare boot cards to currentRepoContext/projectName; if the open loop is unrelated, start a fresh launch instead of resuming stale work.
    Connector
  • Use this when the user explicitly wants to delete a whole documentation Space. Destructive state-changing action: removes the manageable Space directly after the MCP client authorizes the call. Requires numeric space_id from list-spaces and should not be used for deleting individual pages.
    Connector
  • Register a new agent on Human Pages. Returns an API key (hp_...) that you MUST save — it cannot be retrieved later. The agent is auto-activated on PRO tier (free during launch): 15 job offers/day, 50 profile views/day. Use the API key as agent_key in create_job_offer, get_human_profile, and other authenticated tools. Typical first step before hiring.
    Connector
  • List all countries with their current launch phase on Molt2Meet. Returns ISO code, name, flag, default currency, Stripe support, launch phase (Closed/UnderEvaluation/Roadmap/Alpha/Beta/Live) and expected launch date. Use this BEFORE dispatch_physical_task to (1) verify your target country is in phase 'Live' and (2) read its currencyCode — pass that value as payoutCurrency on dispatch (NL→EUR, US→USD, GB→GBP, etc.) so operators are paid in the local currency. Only Live countries can execute tasks. If your target country is in Closed/UnderEvaluation/Roadmap/Alpha/Beta phase, do NOT dispatch — instead call join_country_waitlist with the country's isoCode. Agent waitlist signups directly influence which countries we prioritize for next launch, so joining the waitlist actively brings your target country closer to going Live. No authentication required.
    Connector
  • Fetch an agency's current fiscal year overview including mission, budget authority, obligation totals, sub-agency count, and DEF codes for disaster/emergency funding. Also returns sub-agency breakdown with transaction counts. Accepts either a 3-digit toptier_code (e.g., 097 for DoD, 012 for Agriculture) or an agency_slug (e.g., department-of-defense) — both appear in usaspending_list_agencies results and award search results.
    Connector
  • Upcoming or recently-launched orbital rocket launches from Launch Library 2 (The Space Devs). Per launch: name, provider (+ type/country), vehicle (+ family/reusability/flight count), pad + location (+ coordinates), net launch time + a live countdown (T-minus / T-plus), net precision + launch window, mission (name/type/orbit/description), and current go/scrub status. `window` = "upcoming" (default — next launches by net time) | "previous" (recently launched). `limit` = how many to return, 1-30 (default 10). Keyless; Launch Library 2 free to use (commercial OK) — we re-serve a value-added envelope (countdown, normalised fields, freshness + provenance), never the raw passthrough or the non-commercial launch imagery. Schedules slip frequently; trust `status` + `net_precision`. Every value is returned in an Ed25519-signed, provenance-stamped envelope (source and observation time) you can verify offline against /.well-known/keys, no account required.
    Connector
  • Returns the official ATA company mission and description. Call this when a user asks what ATA is, what we do, our vision, or about the company.
    Connector
  • Register a company (developer, platform, or retirement broker) as a Gigaverse integration partner. Returns a partner_id attribution slug immediately (status pending_review) — pass it on start_signup so signups are attributed to the partner. No API secrets are issued pre-RIA; advisory services and partner revenue share launch upon RIA registration approval.
    Connector
  • Create a space; the caller becomes its owner (write scope). `slug` is derived from `name` when omitted. Use to start a new top-level container of pages; to add a page inside an existing space use create_page, and to rename a space use update_space.
    Connector
  • List every space the API key can access (id, name, slug). Read-only. Start here to discover a `space_id` for list_pages / search / create_page when you don't already have one; for a single space you already know, use get_space instead.
    Connector
  • DATA CENTERS IN SPACE — curated registry of compute/AI spacecraft in orbit (Starcloud's NVIDIA H100 GPU, ESA Φsat-2 AI edge, D-Orbit in-orbit cloud), each enriched with LIVE orbital data (altitude, period, inclination) and the speed-of-light round-trip latency floor for ground links. Use for "what data centers / compute are in space, and the latency to reach them". Unique data. Every value is returned in an Ed25519-signed, provenance-stamped envelope (source and observation time) you can verify offline against /.well-known/keys, no account required.
    Connector
  • Persist one event to this agent's memory stream. For kind=chat, ALWAYS pass `speaker` (the in-world player name behind the line) - flattening "grassguy: i am here" into event_text causes the agent to parrot the speaker as itself on the next tick. Server-side will embed `text` via Workers AI so the memory is reachable by `search_memories` semantic retrieval. Observation/action memories auto-anchor to your current space and last-looked subject by default once you have entered a space; pass space + subjectPosition only to override the anchor precisely. Reflection/chat stay unanchored.
    Connector
  • Live SpaceX activity — next & recent SpaceX launches + Starlink constellation size, from public data; not financial/stock data. A single composite digest answering "what is SpaceX doing right now": the next SpaceX launches and the most recent ones (name, vehicle, pad, net launch time + live countdown, go/scrub status), plus the size of the Starlink constellation we track (object count + a couple of sample objects). Argless. INDEPENDENT — not affiliated with or endorsed by SpaceX; "SpaceX"/"Starlink" used descriptively only. Reuses two feeds we already serve (no new upstream): rocket_launches (Launch Library 2, The Space Devs) filtered to the SpaceX provider, and satellites(group=starlink) off our CelesTrak TLE mirror — so it does NOT hammer upstreams on the request path. Each part degrades independently (one source down → the others still return). HARD CONSTRAINT: NO stock price, share price, valuation, or IPO/investment data of any kind — launch schedule + constellation facts only, informational, from public data (The Space Devs, CelesTrak). Every value is returned in an Ed25519-signed, provenance-stamped envelope (source and observation time) you can verify offline against /.well-known/keys, no account required.
    Connector
  • Check the launch promo status — free PRO tier for the first 100 agents. Returns how many slots are claimed and remaining. No authentication required.
    Connector