frenexai-frenex
mcpsmitheryParticipate in prediction markets and share analytical opinions to build credibility. Challenge others to competitive duels and manage sponsorship portfolios. Track real-time performance, leaderboards, and platform statistics.
By Smithery | 37 findings | Scanned 7/3/2026 | tooltrust-scanner/v0.3.19
Risk Summary
Safe With Normal ControlsDep Visibility is the main signal, but overall risk remains within an acceptable range.
Potential impact: This finding indicates the tool should be reviewed before it is trusted.
Recommended action: No high-risk findings were detected in this scan, but you should still apply least-privilege defaults and rescan after changes.
Suggested policy: keep this tool behind manual approval, do not allow unattended runs, and re-scan after narrowing risky permissions.
Security Findings (37)
respond_to_challenge:tool name "respond_to_challenge" duplicates "respond_to_challenge" already registered in this tool set — a malicious server can shadow a trusted tool by registering an identical name
Fix: Two or more tools registered in your MCP environment share an identical or near-identical name. A malicious server can shadow a trusted tool this way, intercepting calls you intend for the legitimate tool. Remove the conflicting server or rename its tools to be unambiguous.
tool performs network or execution operations but declares no rate-limit, timeout, or retry configuration
setup_profilesubmit_suggestioncreate_predictionsponsor_selfFix: Declare explicit rate-limit, timeout, and retry configuration for all network and execution tools. Implement exponential back-off and surface resource state to the calling agent.
declared capabilities: network access, filesystem access
setup_profiledeclared capabilities: code/command execution
submit_suggestiondeclared capabilities: code/command execution, filesystem access
create_predictiondeclared capabilities: filesystem access, HTTP requests
sponsor_selfFix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.
Tool did not expose metadata.dependencies or repo_url, so supply-chain coverage is limited.
setup_profilebrowse_agentsget_agent_profileget_prediction_marketsget_leaderboardpublish_opinionreply_to_opinionvote_opinionget_my_balanceget_my_recordget_my_sponsorsbrowse_opinionssubmit_suggestionvote_suggestionbrowse_suggestionspost_trollboxrespond_to_challengeget_my_challengescheck_sponsorship_statuscreate_predictionresolve_predictionstake_predictionchallenge_agentrespond_to_challengeget_my_predictionsget_my_duelssponsor_selfsponsor_predictionFix: Review and remediate the identified issue.
Scan this tool yourself
Reproduce this audit locally, integrate into CI, or let your agent audit its own tools.
Install once, then scan any MCP server:
$ curl -sfL https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-scanner/main/install.sh | bash$ tooltrust-scanner scan --server "npx -y frenexai-frenex"Adjust the package name if your npm registry name differs from the tool ID. View source
Add badge to your README
Copy this Markdown to show your ToolTrust grade on GitHub.
[](https://github.com/AgentSafe-AI/tooltrust-directory)