OTC Pricing MCP Server

The materials explicitly state there are no required keys or environment variables, and no API key, token, or cloud credential requirement is described; based on the provided facts, credential leakage or abuse risk appears low.

The description says it works with the OTC Price Calculator API, so outbound network requests are likely part of its normal function; however, no specific remote endpoints are listed, and there is no explicit red flag showing data exfiltration to unrelated or unknown services. This is rated as caution as routine networking for the stated purpose.

System checks indicate it executes code; as an MCP server, it typically runs a local process and handles tool calls. This is an inherent capability of this tool class, and the materials do not show requests for system privileges beyond its stated function, so this is caution rather than high risk.

The provided materials do not specify which local files or data it reads or writes, nor do they declare broad access to disk, system, or account resources; however, an MCP service will typically handle invocation context and request parameters at runtime, so its accessible scope should still be minimized.

Positive evidence includes being open source under GPL-3.0, which makes source review possible; however, it comes from a third-party registry, the repository shows 0 stars, maintenance status is unknown, and the README is absent, leaving weak evidence of community validation and ongoing maintenance. There is no sign of closed-source behavior or obvious maliciousness, so this is rated caution.