UAP Pulse
Search, explore, and analyze 350 declassified UAP records spanning 1944β2026 using these tools:
search_sightings: Filter records by free text, agency (e.g. FBI, NASA), file type (PDF, VID, IMG, AUD, DOC), year range, or location.search_nearby: Find incidents within a specified radius (km) of a lat/lng coordinate, sorted by distance (excludes off-world records).get_sighting: Retrieve the full record for a specific file ID (e.g.pursue-042), including description and officialwar.govsource link.full_text_search: Relevance-ranked search across titles, locations, and descriptions β ideal for thematic queries like 'FLIR', 'orb', or 'radar'.notable_cases: Access curated historical case groups (e.g. Foo Fighters, Gemini 7, Apollo, FBI cases) with matched records and context.hotspots: Rank incident locations by number of associated declassified records.stats: Summary statistics with breakdowns by agency, file type, and era.timeline: Count of declassified records per decade or year from 1944 to 2026.timeline_data: Per-period records with geographic coordinates, suitable for animated maps and timelines.
πΈ 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.
Tools
Tool | What it does |
| Search by |
| Incidents within a radius (km) of a lat/lng, sorted by distance. |
| Full record for one file id (e.g. |
| Relevance-ranked search across titles, locations, and descriptions. |
| Curated historically significant groups with source records. |
| The locations with the most declassified records. |
| Totals + breakdowns by release, agency, file type, and era. |
| Records per decade (or year), 1944 β 2026. |
| 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.
Related MCP server: Gods Eye Geospatial MCP
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:8080Or 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.govCSV is mirrored locally for reproducible builds; coordinates are representative centroids for named locations, maintained inscripts/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 stdioLicense
Code: MIT Β© David Mosiah (@delx369). Data: U.S. public domain.
Maintenance
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/davidmosiah/uap-pulse'
If you have feedback or need assistance with the MCP directory API, please join our Discord server