Skip to content
Squatch MCP
Sign in

io.github.cyanheads/nasa-power-mcp-server

io.github.cyanheads/nasa-power-mcp-server

by io.github.cyanheads· v0.4.2Source: Official MCP Registry
Sign in to watchSign in to claim this server

Findings

Detected by Squatch rules from the server's metadata and protocol behavior. Latest completed scan: .

Severity: High2 findings

Severity: HighStatus: OpenSQ-TOOL-TITLE-EFFECT-MISMATCH

Display title describes a lower-impact action than the name

The tool's display title describes a lower-impact action than its name (for example a read title on a delete tool).

First seen · Last seen

Suggested fix: Make the title describe the same action as the tool name.

Severity: HighStatus: OpenSQ-TOOL-ANNOTATION-UNDERCLAIM

Annotations understate what the tool does

The tool declares itself read-only, but its name or description indicates it changes, deletes or runs something. Clients that auto-approve read-only tools would run it without confirmation.

First seen · Last seen

Suggested fix: Set readOnlyHint to false and destructiveHint to reflect the tool's behavior.

Severity: Medium1 finding

Severity: MediumStatus: OpenSQ-SERVER-AUTH-NONE-WRITE

State-changing tools available without authentication

The remote server lists state-changing tools without requiring authentication.

First seen · Last seen

Suggested fix: Require MCP authorization for servers that expose state-changing tools.

What this scan does not cover

  • Squatch never calls a server's tools, so it cannot see what they actually do at run time.
  • It scans without credentials: tools behind authentication may not be visible.
  • It does not review source code, dependencies or the publisher's infrastructure.
  • A server can change behavior between scans; monitoring compares each scan with the last.
  • Classifications come from tool names, descriptions and schemas, which the publisher controls.

How Squatch scans servers