io.github.CloudCorpRecords/askboard
OCI · GHCR.IO/CLOUDCORPRECORDS/ASKBOARD · 2 COMPONENTS
Feature-request boards for software teams: ranked requests, board stats and spec drafts.
Available components
Last scanned (6 hours ago)
Scores higher than 43% of OCI 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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Build provenance not yet verified. View diagnostics → Unverified
- 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 393 tokens (~56/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability observed for 0 of 30 days with no destabilising changes; credit accrues until the full window elapses.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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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: 2 categories
Categories scored 0 because we could not verify them: 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.
- 4 Nov 26 40
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 4 Nov 2026 · Analysed oci/ghcr.io/cloudcorprecords/askboard@0.1.0
Provenance Inconclusive
We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.
| Result | Inconclusive |
|---|---|
| Ecosystem | oci |
| Reason | Attestation not fetched |
Background: How many MCP packages publish verified provenance →
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 →
generate_spec Generate implementation spec ~37
Generate an agent-ready markdown implementation spec for one feature request.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Identifier of the feature request to generate the spec for. |
No output schema declared.
No examples provided.
get_board_stats Get board stats ~27
Get request counts, vote totals, and top requests for the connected FeatQ board.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_ranked_requests Get ranked feature requests ~87
Get the top feature requests by demand score, excluding requests already marked done. Requests are ranked by demand: each vote counts as one point and each comment as half a point, with scores gradually decaying as a request ages (90-day scale) so recent demand ranks higher, and ties going to the newer request.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of ranked requests to return. |
No output schema declared.
No examples provided.
get_request Get feature request ~37
Get one feature request with its comments for the connected FeatQ board.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Identifier of the feature request to return. |
No output schema declared.
No examples provided.
list_competitor_claims List competitor claims ~64
List what watched competitor comparison pages say about this product. Read only. Claims are signals, not votes.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of competitor claims to return. |
| state | string | – | Filter by claim state: new, added or dismissed. |
No output schema declared.
No examples provided.
list_requests List feature requests ~73
List feature requests for the connected FeatQ board.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of requests to return. |
| sort | string | – | Ordering of results: votes (most voted first) or newest. |
| status | string | – | Filter by request status: new, considering, planned, in_progress or done. |
No output schema declared.
No examples provided.
update_request_status Update request status ~68
Update the status of a feature request. Marking a request done makes it appear in the public changelog.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Identifier of the feature request to update. |
| status | string | yes | New status for the request: new, considering, planned, in_progress or done. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/askboard MCP server?
io.github.CloudCorpRecords/askboard runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/askboard:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/cloudcorprecords/askboard
claude mcp add cloudcorprecords-askboard -- docker run --rm -i ghcr.io/cloudcorprecords/askboard:0.1.0
What is the io.github.CloudCorpRecords/askboard MCP server?
io.github.CloudCorpRecords/askboard is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/askboard. Feature-request boards for software teams: ranked requests, board stats and spec drafts. This page covers its container image (ghcr.io/cloudcorprecords/askboard).
Is the io.github.CloudCorpRecords/askboard MCP server safe to use?
io.github.CloudCorpRecords/askboard scores 40 out of 100 on VerifyMCP. 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/askboard MCP server expose?
io.github.CloudCorpRecords/askboard exposes 7 tools: list_requests, get_request, get_board_stats, get_ranked_requests, generate_spec, and 2 more. Their descriptions and schemas cost roughly 393 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/askboard MCP server still maintained?
io.github.CloudCorpRecords/askboard is still listed as active in the MCP registry. We last reached this channel on 4 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/askboard MCP server under?
io.github.CloudCorpRecords/askboard declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.