io.github.spranab/icantmarket-mcp
NPM · ICANTMARKET-MCP
Browse verified products and open asks, post asks, and submit reviews on icantmarket.
Available components
Last scanned (14 minutes ago)
Scores higher than 91% of npm servers
Category Project Management
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
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to spranab/icantmarket-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 136 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 859 tokens (~122/item across 7 items; 7 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 Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 46% of tool parameters carry a description.Partial
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
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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Oct 26 +3
No change was recorded against any check on this day. Stability & Change Management went from 30 to 53. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 +4
- Stability: unverified → 0.27 ▲ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 78
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 17 Oct 2026 · Analysed npm/icantmarket-mcp@0.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | spranab/icantmarket-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/spranab/icantmarket-mcp/.github/workflows/publish.yml@refs/tags/v0.1.0 |
| Rekor log index | 1701934619 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:29cc0c6095fc16ef78f4138bb913b19dffcc4142fc79564f6b12ef4545b4c5fa352e3a043ce8c7d2396b1453f1ddb3afca553e73924fed9ae3ecf3cef |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| 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_ask ~61
Fetch one public ask by UUID, with the bundled product summary. Returns 404 / error if the ask is verified-only. Use this after list_asks to inspect an ask in detail before deciding to review it.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Ask UUID |
No output schema declared.
No examples provided.
get_product ~69
Fetch a single verified product by slug. Public. Returns the product details plus the count of currently open asks. Useful to grab a product UUID before posting an ask, or to summarize a product for the user.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Product slug, e.g. 'yantrikdb-server' |
No output schema declared.
No examples provided.
list_asks ~107
List open public asks on icantmarket. Public, no auth needed. Use this when the user wants to find a review opportunity that fits their profile, or when they're researching the kind of help requests the community posts. Verified-only asks are not returned (they stay behind the page-level helper-cohort gate).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| product_slug | string | – | – |
| status | string | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
list_products ~77
List verified products on icantmarket. Public, no auth needed. Use this to find product slugs and UUIDs before posting an ask or to help a user browse the maker cohort. Only L1+ verified active products are returned.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
post_ask ~322
Post a structured ask on behalf of the authenticated maker. Requires ICANTMARKET_API_TOKEN. The maker must own the target product (use list_products to find product_id), and the product must be at L1+ trust. Second-and-onward asks require a credited Helpful/Completed review (Review-to-Post gate). Hype-words (revolutionary / game-changing / best-in-class / etc.) trigger 422 — rewrite, or retry with hype_acknowledged=true to override and accept the soft-flag. Voice rule: factual, concrete, with a real 'offer_back' and a measurable 'success_criteria'.
| Name | Type | Req | Description |
|---|---|---|---|
| artifact_url | string | yes | Link to the thing you want feedback on (repo, doc, landing page). |
| closes_in_days | integer | yes | Days until the ask auto-closes. |
| current_stage | string | yes | – |
| helper_profile | string | yes | Who would be a good helper. Be specific. |
| hype_acknowledged | boolean | – | – |
| i_am_building | string | yes | One-line product summary. |
| need_help_with | string | yes | Specific help requested. Be concrete. |
| offer_back | string | yes | What you'll give in return. The cohort is barter-based. |
| product_id | string | yes | UUID of a product the caller owns at L1+ trust level. Get from list_products. |
| success_criteria | string | yes | How you'll know the help worked. |
| time_needed | string | yes | – |
| type | string | yes | – |
| visibility | string | – | – |
No output schema declared.
No examples provided.
submit_review ~169
Submit a substantive review on someone else's open ask. Requires ICANTMARKET_API_TOKEN. Cannot self-review own asks. Body is scored for hype-words, content-fingerprint similarity against the reviewer's prior reviews, profile-match, sock-puppet clustering, and AI-content detection. Flags don't block; they surface on the admin review queue. The recipient sets the Helpful/Completed verdict later — that's what credits the reviewer's Review-to-Post balance. Use list_asks to find an ask UUID first.
| Name | Type | Req | Description |
|---|---|---|---|
| ask_id | string | yes | UUID of the ask you're reviewing. Get from list_asks. |
| body | string | yes | Substantive prose. Pasted boilerplate, low-similarity content, and AI-detected text get flagged. |
| hype_acknowledged | boolean | – | – |
No output schema declared.
No examples provided.
whoami ~54
Confirm the configured ICANTMARKET_API_TOKEN is valid and return the principal user (id, email, handle, isAdmin, helperVerifiedAt). Cheap, no side-effects. Call once on startup to cache the user id.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.spranab/icantmarket-mcp server?
io.github.spranab/icantmarket-mcp runs locally as an npm package, launched with npx -y icantmarket-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 · icantmarket-mcp
claude mcp add spranab-icantmarket-mcp -- npx -y icantmarket-mcp
What is the io.github.spranab/icantmarket-mcp server?
io.github.spranab/icantmarket-mcp is listed in the public MCP registry as io.github.spranab/icantmarket-mcp. Browse verified products and open asks, post asks, and submit reviews on icantmarket. This page covers its npm package (icantmarket-mcp).
Is the io.github.spranab/icantmarket-mcp server safe to use?
io.github.spranab/icantmarket-mcp scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.spranab/icantmarket-mcp server expose?
io.github.spranab/icantmarket-mcp exposes 7 tools: list_products, get_product, list_asks, get_ask, whoami, and 2 more. Their descriptions and schemas cost roughly 859 tokens of context every time the server is loaded.
Is the io.github.spranab/icantmarket-mcp server still maintained?
io.github.spranab/icantmarket-mcp is still listed as active in the MCP registry. We last reached this channel on 17 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.spranab/icantmarket-mcp server under?
io.github.spranab/icantmarket-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.