io.github.Nadeus/toolradar
NPM · TOOLRADAR-MCP
Search, compare, and get pricing for 8,600+ software tools with verified data.
Available components
Last scanned (18 hours ago)
Scores higher than 89% of npm servers
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 55 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 803 tokens (~100/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 −1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 80.
- 8 Oct 26 −2
- Stability: pass → 0.90 functional
- 4 Oct 26 +1
- Stability: 0.97 → pass security
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 −3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Analysed npm/toolradar-mcp@2.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_tools ~78
Compare 2 to 4 software tools side by side. Returns structured comparison with pricing, scores, pros/cons, and computed insights (best overall, best value, most reviewed).
| Name | Type | Req | Description |
|---|---|---|---|
| slugs | array | yes | Array of 2-4 tool slugs to compare (e.g. ['notion', 'clickup', 'asana']) |
No output schema declared.
No examples provided.
get_alternatives ~70
Get alternatives and competitors for a specific software tool. Returns up to 10 alternatives sorted by editorial score.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Number of alternatives to return (default 10) |
| slug | string | yes | Tool slug to find alternatives for (e.g. 'jira', 'slack') |
No output schema declared.
No examples provided.
get_pricing ~58
Get detailed pricing information for a software tool including tiers, pricing model (free/freemium/paid), free trial availability, and expert pricing verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Tool slug (e.g. 'figma', 'github') |
No output schema declared.
No examples provided.
get_tool ~70
Get detailed information about a specific software tool including description, pricing, pros/cons, features, editorial score, review synthesis, and alternatives.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Tool slug (e.g. 'notion', 'linear', 'figma'). Use search_tools first if you don't know the slug. |
No output schema declared.
No examples provided.
list_categories ~35
List all software categories available on Toolradar with tool counts. Use this to discover valid category slugs for the search_tools filter.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
recommend_tools ~210
Recommend the best software tools for a described need. Unlike search_tools (raw retrieval), this ranks candidates by fit, applies hard constraints (budget, pricing, category), and returns a justified, sourced shortlist with fit scores, caveats, verified starting prices, and next steps. Use this when a user asks 'what should I use for X'.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Restrict to a category slug (e.g. 'crm', 'project-management') |
| exclude | array | – | Tool slugs to exclude from the shortlist |
| limit | number | – | Number of recommendations (default 5, max 10) |
| max_monthly_budget | number | – | Hard cap on the per-tool monthly price in USD |
| need | string | yes | Natural-language need, e.g. 'simple CRM for a 6-person agency that syncs with Gmail' |
| pricing | string | – | Restrict to a pricing model |
| team_size | number | – | Number of people who will use the tool |
No output schema declared.
No examples provided.
report_issue ~142
Report a data-quality issue you spotted while using Toolradar data (a wrong price, a dead/renamed tool, a missing or incorrect feature). Files a ticket to the verification queue. Use this when Toolradar data contradicts what you observe on the vendor's own site.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | What is incorrect and what it should be, in one or two sentences |
| evidence_url | string | – | A URL backing the claim (ideally the vendor's own page) |
| field | string | – | What is wrong (default 'other') |
| slug | string | yes | Tool slug the issue is about (e.g. 'notion') |
No output schema declared.
No examples provided.
search_tools ~140
Search and filter software tools from Toolradar's database of 8,600+ tools. Returns tools with names, descriptions, pricing, scores, and categories.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category slug (e.g. 'project-management', 'ai-writing') |
| limit | number | – | Number of results (default 10, max 50) |
| pricing | string | – | Filter by pricing model |
| query | string | – | Search query (e.g. 'project management', 'AI writing tool') |
| sort | string | – | Sort order: score (editorial rating), recent (newest first), rating (user review rating) |
No output schema declared.
No examples provided.
How do I install the io.github.Nadeus/toolradar MCP server?
io.github.Nadeus/toolradar runs locally as an npm package, launched with npx -y toolradar-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · toolradar-mcp
claude mcp add nadeus-toolradar -- npx -y toolradar-mcp
What is the io.github.Nadeus/toolradar MCP server?
io.github.Nadeus/toolradar is an MCP server listed in the public MCP registry as io.github.Nadeus/toolradar. Search, compare, and get pricing for 8,600+ software tools with verified data. This page covers its npm package (toolradar-mcp).
Is the io.github.Nadeus/toolradar MCP server safe to use?
io.github.Nadeus/toolradar scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.Nadeus/toolradar MCP server expose?
io.github.Nadeus/toolradar exposes 8 tools: recommend_tools, search_tools, get_tool, compare_tools, get_alternatives, and 3 more. Their descriptions and schemas cost roughly 803 tokens of context every time the server is loaded.
Is the io.github.Nadeus/toolradar MCP server still maintained?
io.github.Nadeus/toolradar is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.Nadeus/toolradar MCP server under?
io.github.Nadeus/toolradar declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.