Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Nothing to run from here
ChatStack - App Cost Estimator is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
5
tools declared
remote
at its publisher
—
calls last 7d
What it does
Estimate development costs and hours, scope an MVP, and write a PRD with user stories and specs.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http chatstack-app-cost-estimator-mcp https://mcp.chatstack.app/mcp
# 2 — ask your agent for something these tools do
# start_session, send_turn, send_action and 2 more
ChatStack - App Cost Estimator costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CHAll 1 server
chatstack1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http chatstack-app-cost-estimator-mcp https://mcp.chatstack.app/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Start a guided session to estimate app development cost, scope an MVP, and generate a software PRD. No portal account or personal access token is required. Call it with no arguments unless the user already named Review each step (clarify_first) or Run it for me (auto_complete). Do not choose an interaction mode on the user's behalf — wanting an estimate or a fast answer is not auto_complete. If in
| Parameter | Type | Required | Notes |
|---|---|---|---|
| interaction_mode | string | no | Omit this. Set it only when the user explicitly named a mode (e.g. "use auto-complete"): clarify_first reviews every gate, auto_complete advances on its own and reports each decision. |
Continue an app cost estimate by sending the user's answers or requested changes to the MVP scope, user stories, requirements, or technical specification. Pass their exact words in input_as_text, even when next_tool is send_action. Compact replies such as "1A, 2B" are valid. Preserve the user's selections; in interaction mode Review each step do not choose answers for them. In interaction mode Rev
| Parameter | Type | Required | Notes |
|---|---|---|---|
| thread_id | string | yes | Interview thread id from start_session. |
| interview_handle | string | yes | Opaque interview handle from start_session. Pass it on every later tool. |
| input_as_text | string | no | User message text; omit for a style-only interaction_mode switch. |
| interaction_mode | string | no | Interview style: clarify_first (Review each step) or auto_complete (Run it for me). Required for a style-only switch; when omitted with input_as_text, clarify_first is accepted by default. |
Submit the user's pending choice. Set action_type to a value from pending_gate_payload.allowed_actions. In Review each step, action_type is required; confirmed_by_user=true is preferred and is not a substitute for it. In Run it for me, omit action_type and payload to advance one milestone, and do not ask the user to choose – show the user that milestone's Auto-complete decision receipt and pipe-ta
| Parameter | Type | Required | Notes |
|---|---|---|---|
| thread_id | string | yes | Interview thread id from start_session. |
| interview_handle | string | yes | Opaque interview handle from start_session. Pass it on every later tool. |
| action_type | string | no | Widget action type from allowed_actions. Optional in auto_complete; defaults fill the pending gate. |
| payload | object | no | — |
| confirmed_by_user | boolean | no | Preferred when the user explicitly chose. Not required when action_type is already set to an allowed_actions value with a complete payload. |
Read the current app cost estimate without advancing it. Returns flow_stage, pending_gate, and pending_gate_payload. After submission it also returns post_submit_notice and post_submit_links: relay the notice verbatim, keep every URL, and do not add an email-delivery caveat. Pass the thread_id and interview_handle from the Session section. Do not call start_session to recover a session, and do not
| Parameter | Type | Required | Notes |
|---|---|---|---|
| thread_id | string | yes | Interview thread id from start_session. |
| interview_handle | string | yes | Opaque interview handle from start_session. Pass it on every later tool. |
Submit the completed software PRD and app development estimate for email delivery and portal project creation. Call it only after user stories, requirements, tech specs, and the estimate exist. (flow_stage estimate). Run it for me stops at this tool. Offer submission and wait for the user. Do not submit it the way an empty send_action advances a milestone. Before calling, tell the user it emails t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| thread_id | string | yes | Interview thread id from start_session. |
| interview_handle | string | yes | Opaque interview handle from start_session. Pass it on every later tool. |
| interview_summary | string | no | Optional override; normally loaded from the thread |
| first_name | string | no | Suggested or confirmed first name from user context. |
| last_name | string | no | Suggested or confirmed surname from user context. |
| string | no | Suggested or confirmed email from user context. | |
| country | string | no | Suggested or confirmed home country from user context. |
| project_name | string | no | Suggested or confirmed project name. Prefer values the user stated. |
| confirmed_by_user | boolean | no | Set true only after the user confirms the contact details (or corrects them). |
| feedback | string | no | Optional notes from the user (scope, questions, extra context). Ask, but omit if they skip. Never invent this. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install ChatStack - App Cost Estimator or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.0 · scanned 30 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestc2a123caafa19f2a3615f8cf5246d8c89f0e13df7d26bb4aae7cffd8a9e95919
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| start_session | state-write | state-write: declares readOnlyHint: false |
| send_turn | state-write | state-write: declares readOnlyHint: false |
| send_action | state-write | state-write: declares readOnlyHint: false |
| get_estimate_status | no tags | |
| submit_prd | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestc2a123caafa19f2a
Scanned2026-10-30
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish ChatStack - App Cost Estimator can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.