Stackapps Suite MCP server
io.github.Explorer-64/stackapps-suite-mcp·v0.1.10StackApps suite gateway: Imagcon, StackBill, Dicta-Notes. Pay per call in USDC via x402.
0 stars
Reviews
Write oneNobody has reviewed Stackapps Suite yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Stackapps Suite tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualityno auth information5/15
- Maintenancelast push 58 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Stackapps Suite compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 63/100
- higher than 18% of 48,255 servers
Install Stackapps Suite in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the Stackapps Suite repository's README, as published. We do not edit it. Read it on GitHub
StackApps
StackApps leads with a free, open-source AI/crawl readiness audit (twelve signals, GitHub-visible). The Stackhouse is a human-moderated public registry for browser-ready indie apps: when live-approved, listings get canonical HTML proof, an embeddable badge, scan results, and Bronze / Silver / Gold tiers (plus a PWA badge) — credibility and citations, not pay-to-list SEO noise. StackApps is discoverability infrastructure; it is not the business tool itself.
For the long-term strategy and product framing, see VISION.md.
Tech stack
- Frontend: React + TypeScript + Vite
- Auth/Data/Storage: Firebase Auth + Firestore + Storage
- Backend: FastAPI (Python) on Cloud Run
- Hosting: Firebase Hosting
Running locally
Environment variables
Frontend (client/.env.example → copy to client/.env.local):
- VITEFIREBASEAPI_KEY
- VITEFIREBASEAUTH_DOMAIN
- VITEFIREBASEPROJECT_ID
- VITEFIREBASESTORAGE_BUCKET
- VITEFIREBASEMESSAGINGSENDERID
- VITEFIREBASEAPP_ID
Backend (copy .env.example → .env.local or export in your shell):
- FIREBASESERVICEACCOUNT_KEY (JSON string of a Firebase Admin service account key)
- GOOGLEAIAPIKEY (Gemini API key)
- GOOGLESAFEBROWSINGAPIKEY
Notes:
- Admin emails are hardcoded in firestore.rules and client/src/lib/admins.ts (and should be replaced before deploying).
- The backend reads GOOGLEAIAPIKEY (some teams name this GEMINIAPIKEY in their own deployments; keep the variable name aligned with code unless you intentionally change it).
Install + run
npm install
npm run devDeploying
Build then deploy hosting:
npm run build
firebase deploy --only hostingStrategic context
See VISION.md.
Nothing above is checked by us. What we check is on the safety report.
Stackapps Suite: common questions
- Is Stackapps Suite MCP server safe?
- With care: it is graded C, so read the findings first (63/100). Read the Stackapps Suite safety report
- Does Stackapps Suite need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Stackapps Suite maintained?
- The last commit was 99 days ago (2026-07-28). The latest release is v0.1.10.