spedas-mcp (spedas/spedas_agent_kit) is an MCP server listed on the M8ven Trust Index. It scores 52 out of 100, grade D. It declares 31 tools. No publisher has claimed this listing.

D
Caution
52/100

spedas-mcp

Unified SPEDAS-oriented MCP server for Claude Code and Codex agents, providing tools to discover and fetch heliophysics and planetary science data from CDAWeb, NASA PDS, and SPICE kernels.

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

spedas

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Tool descriptions don’t match what handlers do
2 tools describe read intent but their handlers mutate — fetch_data (line 244: file_path.write_text(json.dumps(data), encoding="utf-8")); fetch_pds_data (line 331: file_path.write_text(json.dumps(data), encoding="utf-8"))
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
// tools this server exposes26 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

spedas_overview

Describe available SPEDAS MCP capabilities and the recommended workflow.

search_spedas_data_sources

Recommend whether a SPEDAS request should start with CDAWeb, PDS, SPICE, or a mix.

plan_spedas_observation

Plan a SPEDAS science workflow before choosing data-layer or geometry calls.

compare_cdaweb_pds_spice

Compare CDAWeb, PDS, and SPICE roles for a SPEDAS MCP science request.

create_spedas_analysis_bundle

Create a lightweight request/provenance bundle for a planned SPEDAS analysis.

browse_observatories

Compatibility: list CDAWeb observatories. Prefer browse_data_sources(source_type="cdaweb") for new workflows.

load_observatory

Compatibility: load CDAWeb observatory context. Prefer load_data_source(source_type="cdaweb", source_id=...).

browse_parameters

Compatibility: browse CDAWeb variables. Prefer browse_data_parameters(source_type="cdaweb", ...).

fetch_data

Compatibility: fetch CDAWeb time-series data. Prefer fetch_data_product(source_type="cdaweb", ...).

browse_pds_missions

Compatibility: list PDS PPI missions. Prefer browse_data_sources(source_type="pds") for new workflows.

load_pds_mission

Compatibility: load PDS mission context. Prefer load_data_source(source_type="pds", source_id=...).

browse_pds_parameters

Compatibility: browse PDS variables. Prefer browse_data_parameters(source_type="pds", ...).

fetch_pds_data

Compatibility: fetch PDS archive data. Prefer fetch_data_product(source_type="pds", ...).

list_spice_missions

List supported SPICE spacecraft/body missions with NAIF IDs and kernel status.

get_ephemeris

Get single-time state inline or timeseries trajectory written to CSV.

compute_distance

Compute distance between two SPICE targets over a time range.

transform_coordinates

Transform a 3D vector between SPICE coordinate frames.

list_coordinate_frames

List supported SPICE coordinate frames and usage notes.

manage_cdaweb_cache

Compatibility: manage CDAWeb cache. Prefer manage_data_cache(source_type="cdaweb", ...).

manage_pds_cache

Compatibility: manage PDS cache. Prefer manage_data_cache(source_type="pds", ...).

manage_spice_kernels

Manage SPICE kernels/cache; use manage_data_cache(source_type="spice") for data-layer cache status.

browse_data_sources

Primary data layer: browse SPEDAS source categories (CDAWeb, PDS, SPICE).

load_data_source

Primary data layer: load source context for a CDAWeb observatory, PDS mission, or SPICE mission/frame.

browse_data_parameters

Primary data layer: browse parameters/metadata using source_type rather than source-specific tool names.

fetch_data_product

Primary data layer: fetch CDAWeb/PDS measurement or archive products; route SPICE geometry to geometry tools.

manage_data_cache

Primary data layer: manage cache status/maintenance by source_type.

// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configXHELIO_CDAWEB_CACHE_DIR
configXHELIO_SPICE_KERNEL_DIR
configPDSMCP_CACHE_DIR
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

26/26 tools missing one or more hints — spedas_overview (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_spedas_data_sources (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); plan_spedas_observation (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +23 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Descriptions match behaviour

2 tools describe read intent but their handlers mutate — fetch_data (line 244: file_path.write_text(json.dumps(data), encoding="utf-8")); fetch_pds_data (line 331: file_path.write_text(json.dumps(data), encoding="utf-8"))

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool inputs are validated

22/26 tool handlers declare input schemas (85%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 0/26 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

Tool description accuracy

fetch_data: description implies read-only but handler writes/deletes/executes; fetch_pds_data: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 7 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/spedas/spedas_agent_kit?variant=verified)](https://m8ven.ai/mcp/spedas/spedas_agent_kit)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: e333a1e376b2f16c967af04467b573c9c82a2dbd
code hash: 168d899384406b26ccffe0b5e1d92bf5a7b25aef3f35608566cc9674563cd163
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client