Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
ShelfSignal
Overview
Description from the maker (original English)
The open store index for AI agents: merchants list real stock, agents find local food and stores.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"shelfsignal": {
"command": "npx",
"args": [
"-y",
"@reneturcios/shelfsignal",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add shelfsignal -- npx -y @reneturcios/shelfsignal mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"shelfsignal": {
"command": "npx",
"args": [
"-y",
"@reneturcios/shelfsignal",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"shelfsignal": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/shelfsignal",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account CloudCorpRecords, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 32599 servers in this category
- Published to the registry more recently than 75% of the other 32599 servers in this category
- Basic checks equal to or better than 100% of the other 32599 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is ShelfSignal safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.3.1) reached the registry 12 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, Zendesk
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated 2 days ago
Install
Zendesk
by pipeworx-io
Zendesk MCP Pack — tickets, users, organizations via OAuth.
Computer or cloudUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
ShelfSignal
The open store index for AI agents.
Local merchants list what they actually sell. AI agents find real food and real products nearby, score how likely each item is actually in stock, and check a validation receipt before they send a human across town. Merchants pay one flat price to get listed. Nobody takes 30% of their food.
DoorDash and the delivery apps built a closed index: they own the customer, scrape or rent the menu, charge the merchant 15-30% per order, and still cannot tell you whether the kitchen has the thing you want. ShelfSignal is the opposite shape:
- Merchant-owned listing. The store submits its own stuff, its own prices, its own stock. The listing belongs to the merchant, not the platform.
- Built for agents, not ads. One MCP server any agent can query: find stores, find items, check stock, validate the listing. No sponsored placement, ever.
- Stock is a scored signal, not a claim. Every item carries a last-confirmed date. The likelihood engine turns that evidence into a 0-100 score with printed reasons, so agents stop bluffing "they have it" and start saying "confirmed today, likely in stock."
- Validation receipts. Every listing carries checks an agent can verify: complete profile, real prices, fresh inventory, declared fulfillment. Tier: VERIFIED, LISTED, STALE, or INCOMPLETE.
- Flat money. $100 Starter Store, one time, listed and validated. No per-order commission. See docs/PRICING.md. Merchants can join by email: docs/EMAIL-INTAKE.md.
Quick start
npm installnpm run build npm test
node dist/cli.js coverage node dist/cli.js search "birria" --city "San Francisco" node dist/cli.js stock sf-mission-taqueria-demo "Birria tacos" node dist/cli.js nearby 37.7599 -122.4148 --radius 5 node dist/cli.js ping sf-sunset-bakery-demo "Cardamom knot" in node dist/cli.js validate sf-mission-taqueria-demo node dist/cli.js doctor node dist/cli.js mcp # run the MCP server (stdio) node dist/cli.js serve # run the hosted registry API (http://0.0.0.0:8787)
Hosted registry API
A read-only HTTP API over the same registry, for agents and clients that do not speak MCP:
curl localhost:8787/v1/stores?city=San%20Franciscocurl localhost:8787/v1/stores/sf-mission-taqueria-demo curl "localhost:8787/v1/search?q=birria"
Only listings in the live state are served: listings still in the intake queue are excluded from list and search, and their detail route returns 404. Full reference: docs/API.md.
MCP tools
| Tool | What it does |
|---|---|
search_stores | Find stores by text, city, category, or type (with open-now signal) |
find_nearby | Stores near a lat/lng point, nearest first, with distance and open-now |
search_items | Find a food or product across stores, every hit carrying its stock verdict |
get_store | Full listing: hours, address, fulfillment, items, stock |
check_stock | Stock-likelihood verdict (score, band, reasons) for one item |
validate_store | Validation receipt and tier for one listing |
submit_store | Validate a merchant intake and preview its listing + receipt |
list_coverage | Cities, categories, and store count in the index |
For merchants
You run a store in the city. For $100 you get listed where the agents look:
- Fill the intake (10 minutes): who you are, where you are, your hours, and the stuff you sell with real prices. Template: examples/submission.example.json, field guide: docs/INTAKE.md.
- We validate it and your listing goes live with its first receipt.
- Update stock whenever it changes with one command or one message. Fresh listings rank as VERIFIED; stale ones decay honestly instead of lying to customers.
No commission. No tablet on your counter. No competing with your own listing.
How it works
- The registry is the source of truth:
registry/stores.json(v0.1, git-backed, every change reviewable). - The likelihood engine is deterministic: merchant-reported status, confirmation freshness, staple vs specialty. No model guesses.
- The management layer is freshness: listings decay, validation re-runs on every read, and merchants see exactly what an agent sees. Roadmap in docs/MANAGEMENT.md.
- Full design: docs/SPEC.md. Why this beats the delivery model: docs/VS-DOORDASH.md.
Bundled stores are sample data and are flagged demo: true in every response. Real merchants are never marked demo, and demo stores are never presented as real.
License
MIT