1toolring@1.0.1
CAUTION· static onlyPublisher claims: "Call live data tools through 1ToolRing (1toolring.com), one key and one prepaid balance for thousands of pay-per-call tools. Use when a task needs live Google search results, keyword search volume and SEO data, Google Maps places, Amazon or other e-commerce product prices, stock, crypto or exchange-rate data, social media data, web page scraping, jobs or weather data, or AI image, video and voice tools, and the agent has no direct vendor account for them." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-10 and scored it 66/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
{"mcpServers": {"1toolring": {"type": "http", "url": "https://mcp.1toolring.com/mcp"}}}Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.No other findings across 132 lines in 2 files.
Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
14 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim khmuhtadin: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
- MCP server using network transport (SSE/HTTP)≈ +2 on the totalNamespace tool names and keep tool descriptions literal; no instructions to the agent inside them.