PromptSpend
NPM · @PROMPTSPEND/MCP · SCANNED OCT 1
LLM pricing where every rate carries its source and the date it was last confirmed.
Available components
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 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 55 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 403 tokens (~134/item across 3 items; 3 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 Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 71% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
How do I install the PromptSpend MCP server?
PromptSpend runs locally as an npm package, launched with npx -y @promptspend/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 · @promptspend/mcp
claude mcp add andrewavery7-promptspend -- npx -y @promptspend/mcp
{
"mcpServers": {
"andrewavery7-promptspend": {
"command": "npx",
"args": [
"-y",
"@promptspend/mcp"
]
}
}
} {
"servers": {
"andrewavery7-promptspend": {
"command": "npx",
"args": [
"-y",
"@promptspend/mcp"
]
}
}
} codex mcp add andrewavery7-promptspend -- npx -y @promptspend/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"andrewavery7-promptspend": {
"type": "local",
"command": [
"npx",
"-y",
"@promptspend/mcp"
],
"enabled": true
}
}
} openclaw mcp add andrewavery7-promptspend --command npx --arg -y --arg @promptspend/mcp
mcp_servers:
andrewavery7-promptspend:
command: "npx"
args: ["-y", "@promptspend/mcp"] {
"McpServers": {
"andrewavery7-promptspend": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@promptspend/mcp"
]
}
}
} assistant mcp add andrewavery7-promptspend -t stdio -c npx -a -y @promptspend/mcp
{
"mcpServers": {
"andrewavery7-promptspend": {
"command": "npx",
"args": [
"-y",
"@promptspend/mcp"
]
}
}
} 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.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 −3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- Stability: 0.97 → pass security
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 25 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
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
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 1 Oct 2026 · Analysed npm/@promptspend/mcp@0.1.6
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 92 packages
| Packages resolved | 92 |
|---|---|
| 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 →
estimate_cost ~182
What a described workload actually costs per month on each model. Accounts for conversation history compounding, cache writes, long-context tiers and reasoning tokens. Use this instead of multiplying prices by hand.
| Name | Type | Req | Description |
|---|---|---|---|
| cached_input_share | number | – | 0-1. Default 0. |
| conversations_per_day | number | – | Default 1000. |
| models | array | yes | Models to compare, up to about 8. |
| output_tokens | number | – | Typical reply. Default 350. |
| reasoning_multiplier | number | – | Bill output at this multiple. Default 1. |
| system_tokens | number | – | System prompt size. Default 800. |
| turns | number | – | Turns per conversation. Default 4. |
| use_batch_api | boolean | – | Apply batch discounts. Default false. |
| user_tokens | number | – | Typical user message. Default 150. |
No output schema declared.
No examples provided.
find_cheaper ~112
Cheaper models that score at or above the given one on capability, costed on the same workload. Returns candidates to test, not a recommendation.
| Name | Type | Req | Description |
|---|---|---|---|
| conversations_per_day | number | – | – |
| min_capability | number | – | 0-100. Defaults to the given model’s score. |
| model | string | yes | The model currently in use. |
| output_tokens | number | – | – |
| system_tokens | number | – | – |
| turns | number | – | – |
| user_tokens | number | – | – |
No output schema declared.
No examples provided.
get_price ~62
Current list price for one LLM, with the source and the date it was last confirmed. Returns disputed=true when two sources disagree.
| Name | Type | Req | Description |
|---|---|---|---|
| model_name | string | yes | Model id or name, e.g. gpt-5 or "Claude Opus 5". |
No output schema declared.
No examples provided.
What is the PromptSpend MCP server?
PromptSpend is an MCP server listed in the public MCP registry as io.github.AndrewAvery7/promptspend. LLM pricing where every rate carries its source and the date it was last confirmed. This page covers its npm package (@promptspend/mcp).
Is the PromptSpend MCP server safe to use?
PromptSpend scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 1 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 PromptSpend MCP server expose?
PromptSpend exposes 3 tools: get_price, estimate_cost, find_cheaper. Their descriptions and schemas cost roughly 356 tokens of context every time the server is loaded.
Is the PromptSpend MCP server still maintained?
PromptSpend is still listed as active in the MCP registry. We last reached this channel on 1 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 PromptSpend MCP server under?
PromptSpend declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.