Skip to main content
Glama
Sign In
UAP Pulse

UAP Pulse

by davidmosiah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

🛸 uap-pulse

An MCP server (and a live map) for the Pentagon's declassified UAP files.

On July 10, 2026, the U.S. Department of War published PURSUE Release 04 on war.gov/UFO. uap-pulse now bundles all four releases: 334 U.S. records, plus 16 curated official-government cases from 12 nations — 350 records total, spanning 1944–2026.

Official sources only. U.S. PURSUE records are public domain under 17 U.S.C. § 105. The international layer links to official national archives; rights remain with each originating source. No scraped civilian databases. Not affiliated with or endorsed by any government.

🗺️ Live map: https://uap-pulse.vercel.app · 📦 npm: uap-pulse

Use it as an MCP server

Your agent can search all 350 records by release, location, agency, era, or type — and pull the direct official source link for each.

Claude Desktop / any MCP client — add to your config:

{
  "mcpServers": {
    "uap-pulse": { "command": "npx", "args": ["-y", "uap-pulse"] }
  }
}

That's it — no API key, no auth, no cost. The data ships with the package.

Related MCP server: orbit-sentinel-mcp

HTTP (v2 stateless)

Default is stdio. Optional Streamable HTTP — no session id, JSON responses, loopback only:

npx -y uap-pulse --http
# GET  http://127.0.0.1:3000/health
# POST http://127.0.0.1:3000/mcp   (sessionless)

Env: UAP_PULSE_HOST, UAP_PULSE_PORT, UAP_PULSE_TRANSPORT=http.

Tools

Tool

What it does

search_sightings

Search by release (1–4), free text, agency, type, year range, or location.

search_nearby

Incidents within a radius (km) of a lat/lng, sorted by distance.

get_sighting

Full record for one file id (e.g. pursue-042) + the war.gov link.

full_text_search

Relevance-ranked search across titles, locations, and descriptions.

notable_cases

Curated historically significant groups with source records.

hotspots

The locations with the most declassified records.

stats

Totals + breakdowns by release, agency, file type, and era.

timeline

Records per decade (or year), 1944 → 2026.

timeline_data

Per-period records with coordinates for maps and animation.

Example — "What UAP files mention the Moon?" → search_sightings({ location: "Moon" }) → NASA Gemini/Apollo records with their war.gov links.

Latest release — search_sightings({ release: 4, limit: 100 }) → all 40 files released on July 10, including the 1949 Los Alamos conference transcript, Project Sign records, new sensor videos, and STS-80 images.

The live map

A 3D globe of every geolocatable record — points pulse where the sightings cluster, colored by agency, filterable by era (WWII Foo Fighters → the Navy Era). Click a hotspot to read the files and open them on war.gov. Off-world records (Moon, orbit) get their own panel.

Run it locally:

cd site && python3 -m http.server 8080   # then open http://localhost:8080

Or deploy the site/ folder to Vercel (static, no build step).

Data

  • Source: war.gov/UFO — PURSUE Releases 1–4 (2026-05-08 through 2026-07-10).

  • License of the data: Public domain (U.S. federal government work, 17 U.S.C. § 105).

  • Coverage: 350 records · 275 geolocated · 20 off-world · 1944–2026. U.S. records by agency: War (171), FBI (87), NASA (40), CIA (21), State (7), DOE (5), ODNI (1), Intelligence Community Agency (1), U.S. Government (1).

  • The official war.gov CSV is mirrored locally for reproducible builds; coordinates are representative centroids for named locations, maintained in scripts/build_data.py.

Rebuild the dataset: npm run data (or python3 scripts/build_data.py).

Develop

npm install
npm run build      # tsc -> dist/
npm start          # run the MCP server over stdio

License

Code: MIT © David Mosiah (@delx369). Data: U.S. public domain.

Available Tools

9 tools
full_text_searchA

Relevance-ranked free-text search across every record's title, location and description. Use this for thematic digs ('FLIR', 'orb', 'triangular', 'heat source', 'radar').

Inputs: query (required), limit.

get_sightingA

Get the full record for one UAP file by id (e.g. 'pursue-042'), including the full description and the direct war.gov source link.

Inputs: id (required).

hotspotsB

Rank the incident locations by how many declassified records mention them (the UAP hotspots).

Inputs: limit.

notable_casesA

Return curated, historically significant cases from the release (Foo Fighters, Gemini 7, Apollo, Maury Island, the 1963 presidential memo, the FBI case file, the Navy era) — each with the matching records and why it matters.

Inputs: key.

search_nearbyA

Find declassified UAP incidents within a radius (km) of a latitude/longitude. Sorted by distance. Off-world records (Moon, orbit) are excluded.

Inputs: latitude (required), longitude (required), limit, radius_km.

search_sightingsC

Search the declassified PURSUE UAP records by free text, agency, file type, year range, or location. Returns matching records (brief form).

Inputs: type, limit, query, agency, +3 more.

statsB

Summary statistics for the PURSUE release: totals and breakdowns by agency, file type, and era.

Inputs: no named parameters.

timelineA

Count declassified UAP records per decade (or per year), to see how sightings cluster over time (1944–2026).

Inputs: granularity.

timeline_dataB

Per-period records WITH coordinates — for building animated timelines / maps that play through 1944→2026.

Inputs: granularity.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools have clear distinct purposes, but full_text_search and search_sightings both support searching with different scopes, which could cause slight confusion. Descriptions help differentiate them.

    Naming Consistency3/5

    Naming conventions are mixed: some use verb_noun (get_sighting, search_nearby), some are single nouns (hotspots, stats, timeline), and notable_cases is adjective_noun. Inconsistent but readable.

    Tool Count4/5

    With 9 tools, the set is well-scoped for exploring declassified UAP records. Not too many or too few for the apparent purpose.

    Completeness4/5

    Covers major exploration needs: text search, filtered search, nearby search, detailed records, stats, hotspots, notable cases, and timeline data. Minor gaps like export or more advanced filtering but sufficient.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources

    Related MCP Connectors

    Related MCP Servers

    • epstein

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables full-text, page-level citation search over the House Oversight Committee's published Epstein investigation documents, plus structured search over transcribed rows from Epstein's pilot flight logbook with provenance and confidence markers.
      153 npm
      MIT