Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.davidmosiah/uap-pulse

NPM · UAP-PULSE

Search and map the Pentagon UAP/UFO releases plus curated official archives from 12 nations.

Available components

0 this week 77 Trust /100

Last scanned (14 hours ago)

Scores higher than 55% of npm servers

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 530 tokens (~58/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage81
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 42% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
  • 3 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 28 Oct 26 +1
    • Stability: 0.97 → pass security
  • 27 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 21 Oct 26 +1
    • Stability: 0.97 → pass security
  • 20 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +3
    • Stability: 0.83 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/uap-pulse@0.4.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~530 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
full_text_search ~49

Run a relevance-ranked search across every record's title, location, and description for thematic research.

NameTypeReqDescription
limitinteger––
querystringyestext to search for across all fields

No output schema declared.

No examples provided.

get_sighting ~53

Get the full record for one UAP file by id, including its release, full description, and direct official source link.

NameTypeReqDescription
idstringyesrecord id, e.g. 'pursue-042'

No output schema declared.

No examples provided.

hotspots ~26

Rank incident locations by how many declassified records mention them.

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

notable_cases ~39

Return curated, historically significant cases with matching official records and context for why each case matters.

NameTypeReqDescription
keystring–optional: just one case group

No output schema declared.

No examples provided.

search_nearby ~70

Find declassified UAP incidents within a radius (km) of a latitude/longitude. Results are sorted by distance; off-world records are excluded.

NameTypeReqDescription
latitudenumberyes–
limitinteger––
longitudenumberyes–
radius_kmnumber––

No output schema declared.

No examples provided.

search_sightings ~199

Search the declassified PURSUE UAP records by release, free text, agency, file type, year range, or location. Returns matching records in brief form.

NameTypeReqDescription
agencystring–exact 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'
limitinteger––
locationstring–substring match on the incident location, e.g. 'Iraq', 'Moon'
querystring–free text matched against title, description and location
releasenumber–PURSUE release number, from 1 through 4
typestring–PDF document, VID video, IMG image, AUD audio, or DOC (international official record)
year_endinteger––
year_startinteger––

No output schema declared.

No examples provided.

stats ~26

Return totals and breakdowns by PURSUE release, agency, file type, and era.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

timeline ~33

Count declassified UAP records per decade or year to show how records cluster over time.

NameTypeReqDescription
granularitystring––

No output schema declared.

No examples provided.

timeline_data ~35

Return per-period records with coordinates for building timelines and maps across 1944–2026.

NameTypeReqDescription
granularitystring––

No output schema declared.

No examples provided.

Install

How do I install the io.github.davidmosiah/uap-pulse MCP server?

io.github.davidmosiah/uap-pulse runs locally as an npm package, launched with npx -y uap-pulse. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · uap-pulse

# add to Claude Code
claude mcp add davidmosiah-uap-pulse -- npx -y uap-pulse
Common questions

What is the io.github.davidmosiah/uap-pulse MCP server?

io.github.davidmosiah/uap-pulse is an MCP server listed in the public MCP registry as io.github.davidmosiah/uap-pulse. Search and map the Pentagon UAP/UFO releases plus curated official archives from 12 nations. This page covers its npm package (uap-pulse).

Is the io.github.davidmosiah/uap-pulse MCP server safe to use?

io.github.davidmosiah/uap-pulse scores 77 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.davidmosiah/uap-pulse MCP server expose?

io.github.davidmosiah/uap-pulse exposes 9 tools: search_sightings, search_nearby, get_sighting, hotspots, stats, and 4 more. Their descriptions and schemas cost roughly 530 tokens of context every time the server is loaded.

Is the io.github.davidmosiah/uap-pulse MCP server still maintained?

io.github.davidmosiah/uap-pulse is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.davidmosiah/uap-pulse MCP server under?

io.github.davidmosiah/uap-pulse declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.davidmosiah/uap-pulse MCP server?

VerifyMCP ran 16 checks on io.github.davidmosiah/uap-pulse, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.