beforeyouship-cost-model
mcpsmitheryModel the realistic monthly cost of an LLM app **before you build it**. Not a token calculator: retries, prompt caching, batch discounts, infra overhead, and 3×/10× growth are modeled in, across GPT-5.x, Claude, Gemini, DeepSeek, and more. **Works without a key.** Connect and ask — demo mode covers the six free-tier models. A Pro API key ([beforeyouship.dev](https://beforeyouship.dev)) unlocks the full 18-model catalog. ## Tools | Tool | What it does | |---|---| - **`estimate_cost`** Full cost model for an architecture at a given usage level. Returns Naive / Realistic / Worst Case $/mo per model, growth scenarios, and an opinionated recommendation. | - **`get_model_prices`** Current per-1M-token pricing (input, output, cached, batch) with context windows and staleness metadata. | - **`list_archetypes`** Seven preset architecture patterns (chatbot, RAG pipeline, multi-step agent, …) used as starting points for estimates. | ## Try it Paste into Claude Code or Cursor after connecting: > Estimate the monthly cost of a RAG pipeline at 10,000 requests/day ## Setup ```bash claude mcp add --transport http beforeyouship https://beforeyouship.dev/api/mcp ``` ## Links - Docs & tool reference: https://beforeyouship.dev/docs#mcp - Live calculator: https://beforeyouship.dev - Announcement: https://beforeyouship.dev/blog/query-llm-costs-from-claude-code
By Smithery | 6 findings | Scanned 7/5/2026 | tooltrust-scanner/v0.3.19
Risk Summary
Safe With Normal ControlsDep Visibility is the main signal, but overall risk remains within an acceptable range.
Potential impact: This finding indicates the tool should be reviewed before it is trusted.
Recommended action: No high-risk findings were detected in this scan, but you should still apply least-privilege defaults and rescan after changes.
Suggested policy: keep this tool behind manual approval, do not allow unattended runs, and re-scan after narrowing risky permissions.
Security Findings (6)
estimate_cost:input schema exposes 11 properties (threshold: 10)
Fix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.
Tool did not expose metadata.dependencies or repo_url, so supply-chain coverage is limited.
list_archetypesget_model_pricesestimate_costFix: Review and remediate the identified issue.
input parameter "avg_input_tokens" accepts a credential (informational; not evidence of insecure handling)
estimate_costinput parameter "avg_output_tokens" accepts a credential (informational; not evidence of insecure handling)
estimate_costFix: Avoid accepting raw credentials as input parameters. Use secret managers (e.g. 1Password CLI, AWS Secrets Manager) and ensure credentials are never logged or stored in agent traces.
Scan this tool yourself
Reproduce this audit locally, integrate into CI, or let your agent audit its own tools.
Install once, then scan any MCP server:
$ curl -sfL https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-scanner/main/install.sh | bash$ tooltrust-scanner scan --server "npx -y beforeyouship-cost-model"Adjust the package name if your npm registry name differs from the tool ID. View source
Add badge to your README
Copy this Markdown to show your ToolTrust grade on GitHub.
[](https://github.com/AgentSafe-AI/tooltrust-directory)