Search and map declassified Pentagon UAP/UFO files from the PURSUE release.
Most developer tooling work still happens through a UI a human drives. Uap MCP server moves it into the conversation instead. Search and map declassified Pentagon UAP/UFO files from the PURSUE release.
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.
The server publishes 10 tools. What each one is for:
search_sightings — Search by release (1–4), free text, agency, type, year range, or locationsearch_nearby — Incidents within a radius (km) of a lat/lng, sorted by distanceget_sighting — Full record for one file id (e.g. pursue-042) + the war.gov linkfull_text_search — Relevance-ranked search across titles, locations, and descriptionsnotable_cases — Curated historically significant groups with source recordshotspots — The locations with the most declassified recordsstats — Totals + breakdowns by release, agency, file type, and eratimeline — Records per decade (or year), 1944 → 2026timeline_data — Per-period records with coordinates for maps and animationTools — The Tools tool exposed by this serverInstallation goes through your MCP client rather than a global install: point it at npm on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Uap's toolset — search_sightings, search_nearby, get_sighting and 7 more — is a fair guide to whether it matches your workflow. It is maintained by davidmosiah; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Uap's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| 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. |
| Tools | The Tools tool exposed by this server. |
{
"mcpServers": {
"uap-pulse": { "command": "npx", "args": ["-y", "uap-pulse"] }
}
}Configuration as documented by the project. Restart the client after saving.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.