Skip to content
Squatch MCP
Sign in

SaltCrate Oracle

com.saltcrate/oracle

by com.saltcrate· v1.1.8Source: 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: High1 finding

Severity: HighStatus: OpenSQ-TOOL-SENSITIVE-PATH-REFERENCE

References credential or key locations

Model-facing text references credential, key or configuration file locations unrelated to the tool's stated purpose.

First seen · Last seen

Suggested fix: Remove references to credential files, key stores and client configuration files.

Severity: Medium1 finding

Severity: MediumStatus: OpenSQ-TOOL-INJECTION-INSTRUCTIONS

Instructions addressed to the AI model

Model-facing text contains instructions addressed to the AI model rather than a description of the tool (for example to override prior instructions, to act before using tools, or to react to trigger phrases).

First seen · Last seen

Suggested fix: Describe what the tool does and its parameters. Do not include instructions to the model about other tools, the user or the conversation.

Severity: Low1 finding

Severity: LowStatus: OpenSQ-CONFORMANCE-MODERN-FAILURE

Protocol conformance checks failed

The server failed one or more MCP protocol conformance checks.

First seen · Last seen

Suggested fix: Review the failed checks against the MCP specification.

2 resolved or dismissed findings
Severity: LowStatus: ResolvedSQ-REPO-MISSING

No source repository linked

No source repository is linked in the registry entry.

First seen · Last seen

Suggested fix: Add a repository to server.json.

Status history
  1. ResolvedSquatch
Severity: LowStatus: ResolvedSQ-ENDPOINT-OUTSIDE-NAMESPACE

Endpoint host outside the namespace domain

The endpoint host is not inside the domain that the registry namespace was verified for.

First seen · Last seen

Suggested fix: Host the endpoint under the namespace domain, or verify the endpoint domain with Squatch.

Status history
  1. ResolvedSquatch

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