io.github.CloudCorpRecords/queueboard
NPM · @RENETURCIOS/QUEUEBOARD · 2 COMPONENTS
Feedback boards for product teams: posts, votes, comments, agent work queue, changelog.
Available components
Last scanned (36 minutes ago)
Scores higher than 35% of npm servers
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 & 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 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1659 tokens (~75/item across 22 items; 22 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "publish_board" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 22 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.
- 4 Nov 26 68
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/@reneturcios/queueboard@0.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 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 →
add_evidence ~174
Attach implementation evidence to a post (shown publicly). kind is one of branch|commit|pr|transcript|url; ref is the branch name, commit sha, or URL. Voters see these in the post page's "Implementation" section.
| Name | Type | Req | Description |
|---|---|---|---|
| action_key | – | – | Optional key identifying the agent action this evidence belongs to. |
| kind | string | yes | Kind of evidence: one of branch, commit, pr, transcript or url. |
| label | – | – | Short label shown with the evidence. |
| post_id | integer | yes | Numeric id of the post. |
| ref | string | yes | The evidence reference itself: branch name, commit hash, PR reference, transcript id or URL, according to kind. |
| slug | string | yes | Slug of the board (its URL path segment). |
No output schema declared.
No examples provided.
claim_post ~124
Atomically claim a post before working on it (double-work guard). ttl_seconds defaults to 3600 (max 86400); re-claiming with the same key extends the lease. Returns 409 if another key holds a live claim.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_label | – | – | Label identifying the claiming agent. |
| post_id | integer | yes | Numeric id of the post. |
| slug | string | yes | Slug of the board (its URL path segment). |
| ttl_seconds | – | – | Claim lifetime in seconds (defaults to 3600, max 86400). |
No output schema declared.
No examples provided.
create_board ~134
Create a new feedback board, as a DRAFT. `slug` is the board's URL path segment (lowercase, hyphenated, unique); `name` is the display name. The new board's public URL 404s until a human publishes it from the dashboard -- `publish_board` is off by default (403 `publish_disabled`).
| Name | Type | Req | Description |
|---|---|---|---|
| description | – | – | Text description of the new board. |
| name | string | yes | Display name for the new board. |
| slug | string | yes | URL path segment for the new board (lowercase, hyphenated, unique). |
No output schema declared.
No examples provided.
create_comment ~85
Comment on a post as the board team, optionally replying to a comment.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Text of the comment. |
| parent_comment_id | – | – | Id of the comment being replied to, when this comment is a reply. |
| post_id | integer | yes | Numeric id of the post. |
| slug | string | yes | Slug of the board (its URL path segment). |
No output schema declared.
No examples provided.
create_post ~75
Create a post on a board.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | Body text of the post. |
| slug | string | yes | Slug of the board (its URL path segment). |
| status | – | – | Initial status of the post. |
| tags | – | – | Tags to attach to the post. |
| title | string | yes | Title of the new post. |
No output schema declared.
No examples provided.
delete_post ~49
Delete a post by hiding it through the developer API.
| Name | Type | Req | Description |
|---|---|---|---|
| post_id | integer | yes | Numeric id of the post. |
| slug | string | yes | Slug of the board (its URL path segment). |
No output schema declared.
No examples provided.
get_analytics ~44
Get read-only analytics for a board.
| Name | Type | Req | Description |
|---|---|---|---|
| period | – | – | Analytics period to report over. |
| slug | string | yes | Slug of the board (its URL path segment). |
No output schema declared.
No examples provided.
get_board ~31
Get one board by slug.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Slug of the board (its URL path segment). |
No output schema declared.
No examples provided.
get_changelog ~33
List shipped posts for a board.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Slug of the board (its URL path segment). |
No output schema declared.
No examples provided.
get_post ~48
Get one post by board slug and post id.
| Name | Type | Req | Description |
|---|---|---|---|
| post_id | integer | yes | Numeric id of the post. |
| slug | string | yes | Slug of the board (its URL path segment). |
No output schema declared.
No examples provided.
get_queue ~96
Top UNCLAIMED posts in the owner's curated build order. Owner-ranked posts (queue_rank, lower = sooner) come first, then unranked planned posts by votes. Call this to find the next thing to build, then claim_post before starting work.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | – | – | Maximum number of queued posts to return. |
| slug | string | yes | Slug of the board (its URL path segment). |
No output schema declared.
No examples provided.
list_boards ~21
List boards available to the caller's FeatureJet API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_comments ~44
List comments for a post.
| Name | Type | Req | Description |
|---|---|---|---|
| post_id | integer | yes | Numeric id of the post. |
| slug | string | yes | Slug of the board (its URL path segment). |
No output schema declared.
No examples provided.
list_posts ~98
List posts for a board, optionally filtered by status, search, or tag.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | – | – | Maximum number of posts to return. |
| offset | – | – | Number of posts to skip before returning results (paging). |
| q | – | – | Free-text search query matched against posts. |
| slug | string | yes | Slug of the board (its URL path segment). |
| status | – | – | Filter posts by status. |
| tag | – | – | Filter posts by this tag. |
No output schema declared.
No examples provided.
list_votes ~45
List vote metadata for a post.
| Name | Type | Req | Description |
|---|---|---|---|
| post_id | integer | yes | Numeric id of the post. |
| slug | string | yes | Slug of the board (its URL path segment). |
No output schema declared.
No examples provided.
ping ~21
Check MCP and FeatureJet API reachability for the caller's key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
propose_status ~167
Propose a status change for the board owner to confirm. The agent-honest way to mark work done: nothing changes on the public board and no voter is notified until a human confirms the proposal from the dashboard. status is one of open|planned|in_progress|shipped|declined; a new proposal replaces any pending one. Prefer this over update_post's direct status flip.
| Name | Type | Req | Description |
|---|---|---|---|
| action_key | – | – | Optional key identifying the agent action behind this proposal. |
| note | – | – | Note explaining the proposed status change. |
| post_id | integer | yes | Numeric id of the post. |
| slug | string | yes | Slug of the board (its URL path segment). |
| status | string | yes | The status being proposed for the post. |
No output schema declared.
No examples provided.
publish_board ~122
Publish a board so it is live at its public URL. OFF BY DEFAULT. Putting a board on the public internet is a human decision: unless the FeatureJet deployment has opted in, this returns 403 `publish_disabled` and the owner publishes from the dashboard. Where it is enabled it needs a `write` (or `admin`) scoped key and an active subscription -- an org without one gets 403 `subscription_required`.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Slug of the board (its URL path segment). |
No output schema declared.
No examples provided.
release_post ~51
Release a post's claim so other agents can pick it up.
| Name | Type | Req | Description |
|---|---|---|---|
| post_id | integer | yes | Numeric id of the post. |
| slug | string | yes | Slug of the board (its URL path segment). |
No output schema declared.
No examples provided.
unpublish_board ~53
Return a board to draft so its public URL stops serving it. Nothing is deleted; publish it again to bring it back.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Slug of the board (its URL path segment). |
No output schema declared.
No examples provided.
update_post ~125
Update mutable post fields; null queue_rank explicitly un-ranks.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | New body text for the post. |
| pinned | – | – | Whether the post is pinned. |
| post_id | integer | yes | Numeric id of the post. |
| queue_rank | – | – | Owner-curated queue position (lower = sooner); null explicitly un-ranks the post. |
| slug | string | yes | Slug of the board (its URL path segment). |
| status | – | – | New status for the post. |
| tags | – | – | Replacement tags for the post. |
| title | – | – | New title for the post. |
No output schema declared.
No examples provided.
whoami ~19
Confirm the caller's API key by listing accessible boards.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/queueboard MCP server?
io.github.CloudCorpRecords/queueboard runs locally as an npm package, launched with npx -y @reneturcios/queueboard. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/queueboard
claude mcp add cloudcorprecords-queueboard -- npx -y @reneturcios/queueboard
What is the io.github.CloudCorpRecords/queueboard MCP server?
io.github.CloudCorpRecords/queueboard is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/queueboard. Feedback boards for product teams: posts, votes, comments, agent work queue, changelog. This page covers its npm package (@reneturcios/queueboard).
Is the io.github.CloudCorpRecords/queueboard MCP server safe to use?
io.github.CloudCorpRecords/queueboard 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 io.github.CloudCorpRecords/queueboard MCP server expose?
io.github.CloudCorpRecords/queueboard exposes 22 tools: list_boards, get_board, create_board, publish_board, unpublish_board, and 17 more. Their descriptions and schemas cost roughly 1,659 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/queueboard MCP server still maintained?
io.github.CloudCorpRecords/queueboard 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 io.github.CloudCorpRecords/queueboard MCP server under?
io.github.CloudCorpRecords/queueboard declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.