ShelfSignal
NPM · @RENETURCIOS/SHELFSIGNAL · 2 COMPONENTS
The open store index for AI agents: merchants list real stock, agents find local food and stores.
Available components
Last scanned (21 hours ago)
Scores higher than 38% of npm servers
Category E-commerce
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 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 9 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 629 tokens (~78/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 Management30
- Stability observed for 9 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.
- 4 Nov 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.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +6
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: unverified → fail ▼ security
- Dependency health: unverified → 0.85 ▲ functional
- 26 Oct 26 60
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 npm/@reneturcios/shelfsignal@0.3.1
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| 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 →
check_stock ~93
Score how likely a store actually has an item right now. Returns a 0-100 score, a band (likely / probable / uncertain / unlikely), and the reasons. Never present an 'uncertain' or 'unlikely' verdict to a human as available.
| Name | Type | Req | Description |
|---|---|---|---|
| item | string | yes | Item name as listed, e.g. 'Birria tacos'. |
| store_id | string | yes | Registry id of the store. |
No output schema declared.
No examples provided.
find_nearby ~92
Find listed stores near a point (lat/lng), nearest first, each with distance in km and an open-now signal (null when the store has no structured hours: unknown, not a guess).
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Latitude of the search point. |
| lng | number | yes | Longitude of the search point. |
| radius_km | number | – | Search radius in kilometers; defaults to 5. |
No output schema declared.
No examples provided.
get_store ~55
Full listing for one store by registry id: hours, address, fulfillment, and every item with its last-confirmed stock status.
| Name | Type | Req | Description |
|---|---|---|---|
| store_id | string | yes | Registry id, e.g. sf-mission-taqueria-demo. |
No output schema declared.
No examples provided.
list_coverage ~33
Which cities and categories the index currently covers, with store counts. Check coverage before promising a human you can search somewhere.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_items ~90
Find a specific food or product across listed stores, e.g. 'birria tacos' or 'oat milk'. Every hit carries its stock verdict (score, band, reasons), best evidence first. Never present an 'uncertain' or 'unlikely' verdict to a human as available.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Limit to one city. |
| query | string | yes | Item or food to find. |
No output schema declared.
No examples provided.
search_stores ~121
Find real local stores (restaurants, groceries, bakeries, bodegas, markets) in a city. Returns merchant-submitted listings, not scraped delivery-app menus.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category filter, e.g. tacos, bakery, produce. |
| city | string | – | City name, e.g. San Francisco. |
| query | string | – | Free text matched against store names, categories, and items. |
| type | string | – | Store type: restaurant, grocery, bakery, bodega, cafe, pharmacy, butcher, market, retail. |
No output schema declared.
No examples provided.
submit_store ~74
Validate a merchant submission (the $100 Starter Store intake) and preview exactly how it would appear in the registry, with its validation receipt. Does not charge anything and does not publish until the listing is merged into the registry.
| Name | Type | Req | Description |
|---|---|---|---|
| submission | object | yes | The merchant submission object; see examples/submission.example.json for the shape. |
No output schema declared.
No examples provided.
validate_store ~71
Run the ShelfSignal validation checks on a listing and return its receipt: tier (VERIFIED / LISTED / STALE / INCOMPLETE), score, and every check with its evidence. Use this before recommending a store you have not used before.
| Name | Type | Req | Description |
|---|---|---|---|
| store_id | string | yes | Registry id of the store. |
No output schema declared.
No examples provided.
How do I install the ShelfSignal MCP server?
ShelfSignal runs locally as an npm package, launched with npx -y @reneturcios/shelfsignal. 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/shelfsignal
claude mcp add cloudcorprecords-shelfsignal -- npx -y @reneturcios/shelfsignal
What is the ShelfSignal MCP server?
ShelfSignal is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/shelfsignal. The open store index for AI agents: merchants list real stock, agents find local food and stores. This page covers its npm package (@reneturcios/shelfsignal).
Is the ShelfSignal MCP server safe to use?
ShelfSignal scores 70 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 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 ShelfSignal MCP server expose?
ShelfSignal exposes 8 tools: search_stores, find_nearby, search_items, get_store, check_stock, and 3 more. Their descriptions and schemas cost roughly 629 tokens of context every time the server is loaded.
Is the ShelfSignal MCP server still maintained?
ShelfSignal 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 ShelfSignal MCP server under?
ShelfSignal declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.