Uap Pulse

io.github.davidmosiahPublished by GitHub account davidmosiahv0.4.0Updated Oct 24, 2026

Search and map the Pentagon UAP/UFO releases plus curated official archives from 12 nations.

VerifiedSTDIODesktop onlyKnowledge & MemoryData & Analytics

Overview

AI-generated overview

Lets an assistant search a bundled dataset of declassified U.S. and international government UAP/UFO records by release, location, agency, era, or type.

What you can do
Ships a local dataset of 350 official UAP/UFO records (U.S. PURSUE releases 1-4 plus 16 curated international cases) and exposes tools to query it. Tools include search_sightings (by release, free text, agency, type, year range, or location), search_nearby (radius around a latitude/longitude), get_sighting (full record plus its official source link), full_text_search, notable_cases, hotspots, stats, timeline, and timeline_data. Results include direct links to the originating official archive.
When to use it
Useful when an assistant needs to look up declassified government UAP/UFO files, find incidents near a place, or summarize counts and timelines of official releases. It is a read-only reference dataset, not a live feed, so it fits research, mapping, and question-answering over these records.
Requirements
Runs locally over stdio via npx (npm package uap-pulse); Node.js required. No API key, account, or authentication. The data ships with the package. An optional Streamable HTTP mode is loopback-only and configured with UAP_PULSE_HOST, UAP_PULSE_PORT, and UAP_PULSE_TRANSPORT.
Before you install
Read-only: the tools search and retrieve records and do not write, send, or delete data. No credentials or secrets are requested. The dataset is bundled and mirrored locally, so no third-party requests are needed at query time. The project states it is not affiliated with or endorsed by any government, and international records link to external archives whose rights remain with the originating source.

Installation

In SourceWeft

  1. Open Uap Pulse 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

🛸 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:

json
{  "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.

HTTP (v2 stateless)

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

bash
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

ToolWhat it does
search_sightingsSearch by release (1–4), free text, agency, type, year range, or location.
search_nearbyIncidents within a radius (km) of a lat/lng, sorted by distance.
get_sightingFull record for one file id (e.g. pursue-042) + the war.gov link.
full_text_searchRelevance-ranked search across titles, locations, and descriptions.
notable_casesCurated historically significant groups with source records.
hotspotsThe locations with the most declassified records.
statsTotals + breakdowns by release, agency, file type, and era.
timelineRecords per decade (or year), 1944 → 2026.
timeline_dataPer-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:

bash
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

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

License

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

Source: README.md at commit ccd4583

Tools

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

Version history

1
  1. v0.4.0LatestSep 16, 2026

Score

50% 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
  • License10 pts