Uap Pulse

What davidmosiah/uap-pulse MCP server does

The davidmosiah/uap-pulse MCP server provides read-only access to a bundled dataset of declassified UAP records. The collection contains 350 records spanning 1944–2026: 334 U.S. records from four PURSUE releases and 16 curated official-government cases from 12 countries. Records include source metadata and links to the relevant official material.

The server is intended for research workflows that need to find records, compare groups of records, inspect individual files, or prepare map and timeline views. It does not modify the source data or provide an authenticated government service. The project also includes a live-map site, but the MCP tools are the relevant interface for an agent.

How it works

The package stores the dataset locally and serves MCP tools from a Node-based application. The default transport is stdio, allowing an MCP client to start the process directly. An optional stateless Streamable HTTP mode listens locally and exposes /health and /mcp; the documented default address is 127.0.0.1:3000.

Search operations can filter by PURSUE release, agency, file type, year range, location, or free text. Full-text search ranks matches across titles, locations, and descriptions. Geographic queries use latitude, longitude, and a radius in kilometers. Timeline and map-oriented tools return counts or records grouped by period, with coordinates where available.

Setup and configuration

Install and run the server through npm with npx -y uap-pulse. For Claude Desktop or another MCP client, configure a stdio server using npx as the command, -y as the first argument, and uap-pulse as the package argument. The bundled data means no API key, login, or separate database is needed.

To use HTTP mode, run npx -y uap-pulse --http. The host, port, and transport can be controlled with UAP_PULSE_HOST, UAP_PULSE_PORT, and UAP_PULSE_TRANSPORT=http. The project can also be built from source with npm install, npm run build, and npm start.

Tools and capabilities

The davidmosiah/uap-pulse MCP server exposes these operations:

• search_sightings finds brief matching records using structured filters or free text.
• search_nearby returns nearby incidents ordered by distance.
• get_sighting retrieves a complete record and its official source link.
• full_text_search performs relevance-ranked thematic searching.
• notable_cases returns curated historically significant cases and context.
• hotspots ranks locations by record count.
• stats reports totals grouped by release, agency, file type, and era.
• timeline counts records by decade or year.
• timeline_data returns period records and coordinates for maps or animations.

Limitations and notes

The server is read-only and only covers the records included in its bundled dataset. The coverage is based on PURSUE Releases 1–4 and the selected international cases, rather than a general-purpose UAP archive. Of the 350 records, 275 are geolocated and 20 are off-world; coordinates are representative centroids for named locations, not necessarily precise observation points. search_nearby excludes off-world records.

The U.S. records are public-domain federal government works, while rights for international material remain with their originating sources. The project states that it is not affiliated with or endorsed by any government. Code is licensed under MIT.