Is Akshare One MCP server safe?

akshare-one-mcp is an AI python_package analyzed by SkillTotal's deterministic static scanner. The scan found no malicious indicators, though 2 risky constructs are reported for review. It can: mcp tools detected — capabilities are what the code can do, not a verdict on intent. Risk score 10/100 (low).

akshare-one-mcp 0.3.9

python_package · https://github.com/zwldarren/akshare-one-mcp

LOW

/ 100 malicious-risk

Snapshot · scanned Jun 20, 2026 · akshare-one-mcp@0.3.9 · engine 0.18.0 / ruleset 19

No malicious indicators - review capabilities before installing

Notable — review in context (capabilities are not malware):

Server bound to all network interfaces
MCP tool surface detected

No malicious indicators found by static analysis.

Capabilities — what this component can do (not a risk score):

mcp tools detected

Findings (2)

MEDIUMServer bound to all network interfacesST-EXPOSE-BIND

A server is bound to all network interfaces (0.0.0.0), not just your own machine.

src/akshare_one_mcp/__main__.py:34-34

"--host", default="0.0.0.0", help="Host to bind to (default: 0.0.0.0)"

Why it matters: Without authentication, other hosts on the network can reach it.

Fix: Bind to 127.0.0.1 for local-only use, or require authentication and restrict access if remote exposure is intended.

LOWMCP tool surface detectedST-MCP-DETECTED

An MCP tool surface (manifest or tool definitions) was found.

server.json:1-1

src/akshare_one_mcp/server.py:11-11

mcp = FastMCP(name="akshare-one-mcp")

src/akshare_one_mcp/server.py:14-14

@mcp.tool

src/akshare_one_mcp/server.py:155-155

@mcp.tool

src/akshare_one_mcp/server.py:170-170

@mcp.tool

src/akshare_one_mcp/server.py:184-184

@mcp.tool

src/akshare_one_mcp/server.py:198-198

@mcp.tool

src/akshare_one_mcp/server.py:212-212

@mcp.tool

src/akshare_one_mcp/server.py:227-227

@mcp.tool

src/akshare_one_mcp/server.py:236-236

@mcp.tool

src/akshare_one_mcp/server.py:252-252

@mcp.tool

Why it matters: Just context — review which tools it offers and their permissions.

Fix: Review the declared MCP tools and their permissions.

Check your own component

Run the same evidence-backed scan on any MCP server, agent skill, or package.

Scan your own component

Or get notified if this component's risk changes:

How we determine this: deterministic static analysis (regex + AST), evidence-anchored, no code execution. Methodology →