Why this verdict
mcp-server . Inconclusive
- inconclusive: gap no_tools_extracted at server.json
mcp-server glama No issues found
- benign: 47 checks satisfied, no findings for mcp-server:glama
Security findings 0
No individual findings recorded
The inconclusive verdict rests on the coverage gaps below; 1 candidate finding was refuted on review.
Execution chain 8
What it calls, runs, installs, reads and writes, with the line that does it.
GitHub repositories 1
honeylabshq/honeylabs-mcp
URLs 7
https://github.com/honeylabshq/honeylabs-mcp
https://glama.ai/mcp/schemas/server.json
https://honeylabs.net/dashboard
https://mcp.honeylabs.net/mcp
https://mcp.honeylabs.net/mcp
https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json
Refuted findings 1
Candidates the review stage examined and rejected, kept for transparency.
Agent hijacking
mediumRefutedlow confidenceServer instructions tell the agent to ALWAYS prefer this server's tools over web search for a broad set of IP, domain and CVE questions, steering tool selection; the scope stays within the declared threat-intel purpose.
ALWAYS use these tools instead of web search
Why it was refuted
The 'ALWAYS use these tools instead of web search' text is the server's own instructions, scoped to threat-intel questions that map to the server's declared tools. It is the declared core capability and routes only to the server's own tools, not to an off-purpose or hidden action. The routing is a normal tool-selection hint, not a hijack.
Coverage gaps 1
Parts of the artifact the static analysis could not fully examine.
no_tools_extracted MCP server target with no statically extractable tools/prompts/resources
server.json