com.mambabuilt/mcp-public-feature-board-roadmap-monitor
NPM · @MAMBALABSDEV/MCP-PUBLIC-FEATURE-BOARD-ROADMAP-MONITOR
A company's public feature board: top requests, votes, status, integration asks.
Available components
Last scanned (6 hours ago)
Scores higher than 35% of npm servers
Category Productivity and Notes
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 Security98
- 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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 9 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 731 tokens (~731/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 27 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 26 Oct 26 53
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@mambalabsdev/mcp-public-feature-board-roadmap-monitor@1.0.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 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
get_feature_board_requests Get a company's public feature requests ~731
Find a company's public feature board from its domain (for example clickup.com) and return its top requests. The homepage is read for a link to a feedback board or public roadmap, including one on the company's own subdomain; when none is linked, the common Canny, Featurebase, Frill, and UserVoice addresses are checked and a board is used only when it links back to the company domain. You get one company_board row (platform, board URL, total posts, top request, status counts, and the integrations customers ask for) and one request row per feature request, most votes first, with votes, status, comments, board, and an integration flag naming the product asked for. With only_new and a state_key, only new requests, status changes, and vote jumps since the last run. A Productboard portal comes back as a link. No board, a blocked board, and a board with no readable request are free. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges once per company whose board was found and read.
| Name | Type | Req | Description |
|---|---|---|---|
| board_urls | array | – | Board addresses you already know, for example https://feedback.canny.io. With one domain and one board URL, the board is read as that company's board. A board URL on its own is read as a company of i… |
| company_domain | string | – | The company website domain, for example clickup.com. The actor reads the homepage for a link to a feedback board or public roadmap, then checks the common board addresses. |
| company_name | string | – | With one domain only: the company name as its board shows it. Used to confirm a board found by name. |
| domains | array | – | Several company domains, one per line. Each gets its own board row. Up to 200 per run. |
| integration_requests_only | string | – | true to return only requests that ask for an integration. The board row still counts every request read. Default false. |
| max_boards | string | – | Boards or forums read per company, largest first, up to 5. Canny shows its top 10 and newest 10 requests on each board page. Default 2. |
| max_charge_usd | string | – | Optional. The run stops before it would charge more than this. |
| max_requests | string | – | Request rows returned per company, most votes first, up to 100. 0 returns only the board row. Default 20. |
| min_vote_increase | string | – | With only new on: the vote gain that makes a request count as changed. Default 5. |
| only_new | string | – | true to return only requests that are new, changed status, or gained at least Min vote increase votes since the last run with the same state key. The board row is returned on every run. Default false. |
| probe_platform_slugs | string | – | true (default) checks <name>.canny.io, <name>.featurebase.app, <name>.frill.co, and <name>.uservoice.com when the site links no board. A board found this way is used only when it links back to the co… |
| proxy_mode | string | – | auto (default) sends requests directly and moves a host to the Apify proxy default pool only when that host refuses. A reliability setting: proxy use adds nothing to your price. |
| state_key | string | – | Names the saved request list, so separate schedules compare separately. |
No output schema declared.
No examples provided.
How do I install the com.mambabuilt/mcp-public-feature-board-roadmap-monitor server?
com.mambabuilt/mcp-public-feature-board-roadmap-monitor runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-public-feature-board-roadmap-monitor. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mambalabsdev/mcp-public-feature-board-roadmap-monitor
claude mcp add com-mambabuilt-mcp-public-feature-board-roadmap- -- npx -y @mambalabsdev/mcp-public-feature-board-roadmap-monitor
What is the com.mambabuilt/mcp-public-feature-board-roadmap-monitor server?
com.mambabuilt/mcp-public-feature-board-roadmap-monitor is listed in the public MCP registry as com.mambabuilt/mcp-public-feature-board-roadmap-monitor. A company's public feature board: top requests, votes, status, integration asks. This page covers its npm package (@mambalabsdev/mcp-public-feature-board-roadmap-monitor).
Is the com.mambabuilt/mcp-public-feature-board-roadmap-monitor server safe to use?
com.mambabuilt/mcp-public-feature-board-roadmap-monitor scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 com.mambabuilt/mcp-public-feature-board-roadmap-monitor server expose?
com.mambabuilt/mcp-public-feature-board-roadmap-monitor exposes 1 tool: get_feature_board_requests. Their descriptions and schemas cost roughly 731 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-public-feature-board-roadmap-monitor server still maintained?
com.mambabuilt/mcp-public-feature-board-roadmap-monitor is still listed as active in the MCP registry. We last reached this channel on 5 November 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 com.mambabuilt/mcp-public-feature-board-roadmap-monitor server under?
com.mambabuilt/mcp-public-feature-board-roadmap-monitor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.