mcpField
U
uap-pulse

uap-pulse

Local
uap-pulse.vercel.appLegal & Government0Updated 9w ago

About uap-pulse

uap-pulse is an MCP server and interactive map for searching and mapping declassified U.S. defense UAP files and curated official archives from other countries. It uses official sources and supports searches by agency, location, era, and record type, with links to source files.

Key features

  1. 01Search by release, agency, location, and era
  2. 02Find records within a coordinate radius
  3. 03Retrieve records with official source links
  4. 04View hotspots, timelines, and statistics
  5. 05Filter geolocated records on a 3D map

Use cases

  1. 01Find UAP files associated with a location or agency
  2. 02Review the distribution of declassified records by era
  3. 03Open official files from map hotspots

MCP support

The MCP server provides tools to search records, find nearby incidents, retrieve full entries and official links, and query hotspots, timelines, and statistics. Data is bundled with the package.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"davidmosiah-uap-pulse": {
"command": "npx",
"args": [
"-y",
"uap-pulse"
]
}
}
}
Run commandnpx -y uap-pulse

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmuap-pulse0.4.0

Tools

9

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
typeenumNoPDF document, VID video, IMG image, AUD audio, or DOC (international official record)PDF | VID | IMG | AUD | DOC
limitintegerNo
querystringNofree text matched against title, description and location
agencystringNoexact agency name, e.g. 'Department of War', 'FBI', 'NASA', 'Department of State', 'Central Intelligence Agency', 'Department of Energy', 'Office of the Director of National Intelligence'
releaseenumNoPURSUE release number, from 1 through 41 | 2 | 3 | 4
locationstringNosubstring match on the incident location, e.g. 'Iraq', 'Moon'
year_endintegerNo
year_startintegerNo

Details

From the project 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:

{
  "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:

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:

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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.