Caveat verdict

afrexai-mcp-engineering

88
🟢 Trusted
No high-risk patterns surfaced by the deep scan — automated capability review, not behavioral proof.

This is an MCP server engineering guide; network and credential capabilities are legitimate for building and integrating MCP servers, and the content is entirely methodology documentation with TypeScript templates for standard MCP patterns.

⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis — not a human review. Caveat flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

45
security
30
transparency
70
maintenance

Permission integrity

Code accesses API keys/tokens but declares no environment variables

credential_access

Findings (2)

Pattern match critical

Possible hardcoded credential

SKILL.md · code · API_KEY: "{{env.MY_SERVICE_API_KEY}}

Confirmed in code medium

HTTP server creation — accepts inbound connections

SKILL.md · code

Permissions & capabilities

No declared permissions — minimal attack surface.

network_incredential_access

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API