Deterministic decisions before software acts. Evaluate supplied facts against supplied rules, receive yes, no or review with reasons, and read or export your own saved decision records. Supplying rules does not prove policy-owner approval. Your application owns execution; Runtime does not spend money, issue refunds or perform external actions. Paid, controlled business pilot: USD 10 including applicable tax for 1,000 completed records (USD 0.01 each). Enrollment is limited to 25 business accounts in documented supported EU, UK and US markets. Identical retries and reads add no record debit, but all admitted MCP requests count toward the bounded account request allowance. Records are available for 90 days with export. See the website for package, refund and request-limit terms. Smithery connection: supply the full Bearer value of your own short-lived, budget-capped evaluate/read client key from console.decide.fyi in decide-runtime-key. Smithery forwards it as an Authorization header and proxies requests. Never supply Stripe, Clerk, admin or merchant credentials. Connecting alone creates no credit or spending permission; account funding and an explicit scoped budget are required. Smithery OAuth is not configured for this listing; use the scoped-key route. Direct client connections and onboarding: https://www.decide.fyi/mcp#connect-runtime. Free testing is separate: decidefyi/decision-runtime (Decide Runtime — Free Sandbox).

MCP readiness

B · 83/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	23/25	Endpoint answers the MCP initialize handshake (5871 ms); very slow response -2.
Protocol revision	8/10	Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	13/15	26/30 probes succeeded over 30 days (87%).
Tool declaration	10/10	Lists 3 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Very slow (5871 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 60% of peers; This listing 83 · peer median 81
Latency: Faster than 8% of peers; This listing 989 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Live MCP endpoint −2 — Answer initialize and tools/list at the declared endpoint.
Now: Endpoint answers the MCP initialize handshake (5871 ms); very slow response -2.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-10-12 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/decidefyi/runtime/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/decidefyi/runtime/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://www.decide.fyi/mcp#connect-runtime

Listed at (smithery)

https://www.decide.fyi/mcp#connect-runtime