Uap Pulse vs Scopus MCP — MCP Server Comparison | AllMCPs
Uap Pulse vs Scopus MCP
A side-by-side look at the Uap Pulse and Scopus MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Uap Pulse for research work as a local process; choose Scopus MCP for research as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Uap Pulse when
You need dedicated capabilities in the Research domain.
You prefer a local stdio subprocess transport.
Its auth model fits you: No auth required.
You want tools like search_sightings, search_nearby, get_sighting.
search_sightingsSearch the declassified PURSUE UAP records by release, free text, agency, file type, year range, or location. Returns matching records in brief form.
search_nearbyFind declassified UAP incidents within a radius (km) of a latitude/longitude. Results are sorted by distance; off-world records are excluded.
get_sightingGet the full record for one UAP file by id, including its release, full description, and direct official source link.
hotspotsRank incident locations by how many declassified records mention them.
statsReturn totals and breakdowns by PURSUE release, agency, file type, and era.
timelineCount declassified UAP records per decade or year to show how records cluster over time.
full_text_searchRun a relevance-ranked search across every record's title, location, and description for thematic research.
notable_casesReturn curated, historically significant cases with matching official records and context for why each case matters.
timeline_dataReturn per-period records with coordinates for building timelines and maps across 1944–2026.
Scopus MCP tools 6
query
count
sort
coverDate
scopus_id
author_id
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Uap Pulse is categorized under Research and uses a local stdio subprocess. Scopus MCP belongs to Research and uses a local stdio subprocess. Pick Uap Pulse for research work and Scopus MCP for research.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Uap Pulse is listed as free. Auth: no auth required. Scopus MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add davidmosiah-uap-pulse and scopus-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Uap Pulse has a quality signal of 63/100 (Good) with 5 views, 0 installs and 0 GitHub stars. Scopus MCP has 53/100 (Good) with 1 views, 0 installs and 46 GitHub stars.