wysh3-perplexity-mcp-server
mcp0.3.1MCP web search using perplexity without any API KEYS
By wysh3 | 3 findings | Scanned 5/4/2026 | tooltrust-scanner/v0.3.9 | 97
Repository health
Popularity and maintenance signals alongside the security grade.
97
current snapshot
33
current snapshot
2
public GitHub contributors
Dec 5, 2025
GitHub repository activity
Not collected
GitHub metadata pending
Not collected
Latest GitHub release
Stars trend
Daily star additions · githubarchive_bq · observed through Oct 3, 2026 · export updated Oct 26, 2026
Pull request activity
Weekly PR events · githubarchive_bq · observed through Oct 3, 2026 · export updated Oct 26, 2026
No observed PR events yet.
Data quality: observed_events. Charts show observed events, not a reconstructed historical total.
Risk Summary
Safe With Normal ControlsExcessive Permissions is the main signal, but overall risk remains within an acceptable range.
Potential impact: The agent may gain overly broad access to files, network, databases, or execution capabilities.
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 (3)
search:tool declares network permission
Fix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.
search:tool performs network or execution operations but declares no rate-limit, timeout, or retry configuration
Fix: 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.
search:Tool did not expose metadata.dependencies or repo_url, so supply-chain coverage is limited.
Fix: 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 wysh3-perplexity-mcp-server"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)