StackTab MCP
NPM · STACKTAB-MCP
StackTab: SaaS service pricing and monthly stack cost estimates.
Available components
Last scanned (9 hours ago)
Scores higher than 37% of npm servers
Category Finance and Payments
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
- 39 of 120 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 11 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 272 tokens (~136/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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: 1 category
A category scored 0 because we could not verify it: 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.
- 16 Oct 26 −6
- Source repository: pass → fail ▼ security
- Security disclosure: fail → unverified ▼ functional
- 14 Oct 26 +33
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- 11 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 8 Oct 26 23
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/stacktab-mcp@0.1.0
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 →
Dependencies 120 packages
| Packages resolved | 120 |
|---|---|
| Stale | 39 |
| 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 →
estimate_stack_cost Estimate the monthly bill for a named stack at a given scale ~130
Price a whole stack at a chosen user count using StackTab's verified plan data. Returns the plan each service lands on and an itemised bill — which lines are included in the base fee and which are metered overages. Use when someone asks "what will this cost at N users" instead of estimating from memory.
| Name | Type | Req | Description |
|---|---|---|---|
| stack | string | yes | Comma-separated service slugs, e.g. "supabase,clerk,polar,vercel". Look them up with lookup_service_pricing. |
| users | number | – | Monthly active users to price at. Default 10,000. |
No output schema declared.
No examples provided.
lookup_service_pricing Look up current published pricing for a SaaS service ~142
Read StackTab, which re-checks the published pricing of the services a product runs on (auth, database, hosting, payments) and records when each plan was last verified against the vendor's own page. Use when asked what something costs or what its free tier includes. Prices and free-tier limits change often enough that a remembered figure is a guess; each plan here carries the date it was last checked.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category: "auth", "database", "hosting" or "payments". |
| service | string | – | A specific service slug or name, e.g. "clerk", "neon", "stripe". |
No output schema declared.
No examples provided.
How do I install the StackTab MCP server?
StackTab MCP runs locally as an npm package, launched with npx -y stacktab-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 · stacktab-mcp
claude mcp add tech-thecompound-stacktab -- npx -y stacktab-mcp
What is the StackTab MCP server?
StackTab MCP is listed in the public MCP registry as tech.thecompound/stacktab. StackTab: SaaS service pricing and monthly stack cost estimates. This page covers its npm package (stacktab-mcp).
Is the StackTab MCP server safe to use?
StackTab MCP scores 65 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. 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 StackTab MCP server expose?
StackTab MCP exposes 2 tools: lookup_service_pricing, estimate_stack_cost. Their descriptions and schemas cost roughly 272 tokens of context every time the server is loaded.
Is the StackTab MCP server still maintained?
StackTab 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 StackTab MCP server under?
StackTab 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.