MCP Risk

Directory / server

ai.smithery/fengyinxia-jimeng-mcp

This directory entry reports an automated security scan of ai.smithery/fengyinxia-jimeng-mcp, scanned 2026-07-28. Trust grade F rates provenance, transport, known vulnerabilities and instruction integrity; capability risk is reported separately, not folded into the grade.

registry.modelcontextprotocol.io, scanned 2026-07-28, tool surface via none

F 46/100 permalink

Automated checks

StatusCheckPolicyResult
PASS Listed on the official MCP registry §1.1
Listed on registry.modelcontextprotocol.io as ai.smithery/fengyinxia-jimeng-mcp. 1 finding
  • Registry entry: ai.smithery/fengyinxia-jimeng-mcp ↗
FAIL Source repository is public and maintained §1.2

Claimed source repository does not exist (or is private).
INFO Published package is consistent and attested §1.3

No published package associated with this server (remote-only or non-npm/PyPI source).
UNVERIFIABLE Tool surface is inspectable and proportionate §2.1–§2.4

Tool surface could not be inspected (no reachable tools/list, no public package source). Per policy, unverifiability caps the overall grade.
PASS HTTPS-only endpoint §3.1
Endpoint uses HTTPS. 1 finding
  • Endpoint: https://server.smithery.ai/@fengyinxia/jimeng-mcp/mcp
UNVERIFIABLE Authentication required §3.2

No MCP endpoint responded at this URL (HTTP 404); authentication could not be probed.
WARN OAuth protected-resource metadata published §3.3
No protected-resource metadata found - clients cannot discover the authorization server per spec. 1 finding
  • Checked: https://server.smithery.ai/.well-known/oauth-protected-resource
INFO No known vulnerabilities (OSV.dev) §4.1

No package to query (remote-only server).
UNVERIFIABLE Server-supplied instructions free of poisoning indicators §5.1–§5.4

No server-supplied instructions or tool descriptions were obtainable to scan.
What this grade covers
  • Provenance & supply-chain integrity (§1)
  • Tool surface & capability risk (§2)
  • Transport & authentication (§3)
  • Known CVEs via OSV.dev (§4)
  • Instruction/tool poisoning patterns (§5)

Limitations: pattern-based only (no semantic injection detection), static npm analysis (live server instructions not retrieved for package-only scans), single-server scope (no cross-server toxic flow analysis). See the full policy.

Methodology: MCP Server Security Policy. Unfamiliar term? See the glossary.