Log inSubmit server
Uap Pulse logo

Uap Pulse

by davidmosiah

Searches and analyzes 350 official-source UAP records with location queries, timelines, statistics, and source links.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Uap Pulse

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "davidmosiah-uap-pulse": {
      "command": "npx",
      "args": [
        "-y",
        "uap-pulse"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y uap-pulse

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

Searches declassified U.S. federal UAP records with the davidmosiah/uap-pulse MCP server, including PURSUE releases, agencies, dates, file types, locations, and free-text terms. It runs locally over stdio by default, ships its dataset with the npm package, and can optionally expose a stateless local HTTP endpoint. Use it for research that needs searchable records, geographic analysis, timelines, curated cases, or links to official source files. No API key or authentication is required.

Use cases

  • Search declassified UAP records by agency, release, date, or location
  • Retrieve official source links for individual UAP files
  • Compare record counts across eras and government agencies
  • Find geographic hotspots and nearby incidents
  • Build UAP timelines and map views from coordinate data

Key features

  • Searches four PURSUE releases and curated international cases
  • Supports structured and relevance-ranked full-text search
  • Finds incidents within a geographic radius
  • Provides statistics, hotspots, and timeline counts
  • Returns direct official source links
  • Runs over stdio or optional local stateless HTTP

Tools9

What Uap Pulse lets your agent do. Expand a tool for its parameters.

Verified live~953 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

6/6 checks healthy over the last 75d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · uap-pulse (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads220Package downloads in the last 30 days.
Last commit2mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed9Callable tools this server registers over MCP.
Directory activity6 viewsConfig copies, upvotes, and views on AllMCPs.

How Uap Pulse works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Uap Pulse

Run `npx -y uap-pulse`. For an MCP client, configure `npx` with `-y` and `uap-pulse` as its arguments.

Yes. The README provides a Claude Desktop stdio configuration using `npx -y uap-pulse`.

No.

Use the `search_nearby` tool with a latitude, longitude, and radius in kilometers. Results are sorted by distance, and off-world records are excluded.

Run `npx -y uap-pulse --http`. The documented endpoints are `GET /health` and `POST /mcp` on the local default address.

Related MCP servers

All in Research All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewUap Pulse AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/davidmosiah-uap-pulse?style=directory)](https://allmcps.com/mcp/davidmosiah-uap-pulse)
HTML Embed
<a href="https://allmcps.com/mcp/davidmosiah-uap-pulse"><img src="https://allmcps.com/api/badge/davidmosiah-uap-pulse?style=directory" alt="Uap Pulse on AllMCPs" /></a>