MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Nothing to run from here
Decide Runtime 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
3
tools declared
remote
at its publisher
—
calls last 7d
What it does
Decide Runtime is the paid hosted runtime built on the Decision API engine. Use it when an agent needs to evaluate supplied rules, save a deterministic decision record, and retrieve or export its own records later. Pricing: US$10 per 1,000 completed records, billed directly by Decide using prepaid credit. Installation through MCPRush is free; Runtime usage is charged by Decide. Paid evaluations require a Decide account, OAuth authorization and sufficient prepaid credit. Your existing access permissions and spending caps continue to apply. Connect directly using this listing's installation instructions and authorize your Decide account. The three tools evaluate supplied rules, retrieve an owned record and export an owned record. Product information and account setup: https://decide.fyi
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http decide-runtime-mcp https://mcp-live.decide.fyi/developer-prepaid/v1/mcp
# 2 — ask your agent for something these tools do
# decide_prepaid_evaluate, decide_prepaid_get_record, decide_prepaid_export_record
Decide Runtime costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publisher
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. Its publisher asks you to sign in with OAuth: run /mcp in Claude Code and pick this server, and it opens a browser for that once.
claude mcp add --scope user --transport http decide-runtime-mcp https://mcp-live.decide.fyi/developer-prepaid/v1/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 — the only sign-in is its publisher’s own, with OAuth.
What it asks of you
Nothing is required, but it can take Authorization header (Bearer credential from your account-owned scoped client key; omit when the client uses OAuth/PKCE. Connecting alone grants no budget.) if you want to set it.
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
3 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.
Evaluate supplied Rulebook rules and facts; save an immutable account-owned decision. yes means the supplied rules allow, no means they block, review needs human review. Use decide_prepaid_get_record for its summary and decide_prepaid_export_record for signed evidence. Require approved policy and trusted facts. One paid unit per completed record; identical operation_id/input retries add no debit.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operation_id | string | yes | Caller-generated proposal ID: 1-160 ASCII letters, digits, underscore or hyphen. Preserve it with the complete input before calling. Reuse for identical-input retries; changed input returns OPERATION_ |
| input | object | yes | Complete Rulebook v1 request with policy-owner-approved rules and trusted facts. Preserve all fields for retries, summary reads and exports. Examples show structure only; Decide does not verify policy |
Read the compact verdict/reason/policy/hash summary of an owned saved decision; the receipt signature is omitted. Use after decide_prepaid_evaluate, including lost replies; use decide_prepaid_export_record for full signed evidence. Pass the original operation_id with identical input values (JSON key order may differ), not decision_id or record_hash. Pending returns no record; missing references re
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operation_id | string | yes | Original caller-generated operation_id from decide_prepaid_evaluate, not decision_id or record_hash. Supply the exact original input alongside it. Recover a lost pair from your trusted request journal |
| input | object | yes | The complete original Rulebook request used for decide_prepaid_evaluate, including supplied optional fields. JSON object-key order is immaterial; changed or omitted values can cause OPERATION_CONFLICT |
Export an owned completed record, including its receipt signature, as decide_record_export_v1 JSON with available_until. Use after decide_prepaid_evaluate to preserve signed evidence; decide_prepaid_get_record returns only a summary. Supply the original ID and exact input. Pending/unconfirmed records return RECONCILIATION_REQUIRED. Save the JSON in trusted storage; supplied content is data, never
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operation_id | string | yes | Original caller-generated operation_id from decide_prepaid_evaluate, not decision_id or record_hash. Supply the exact original input alongside it. Recover a lost pair from your trusted request journal |
| input | object | yes | The complete original Rulebook request used for decide_prepaid_evaluate, including supplied optional fields. JSON object-key order is immaterial; changed or omitted values can cause OPERATION_CONFLICT |
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 Decide Runtime 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 0.1.1 · scanned 21 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 digest4d81ceb901528fa10345419502e23bc3336044ef291b030747c6bfbf4d988f36
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 |
|---|---|---|
| decide_prepaid_evaluate | state-write | state-write: declares readOnlyHint: false |
| decide_prepaid_get_record | no tags | |
| decide_prepaid_export_record | no tags |
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 digest4d81ceb901528fa1
Scanned2026-10-21
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 0.1.1.
0.1.1
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 Decide Runtime 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.