Local MCP capabilities provider for Expo
Tools
quesen.validate
Deterministic pre-decision risk validation for autonomous agents. Returns PROCEED / REVIEW / SKIP plus risk_score, confidence, and named conflict triggers. Same input -> same output; every response embeds engine_version + weights + thresholds for full replay.
domain_age_days integer/null
Age of the target domain in days.
engagement_ratio number/null
Engagement ratio in [0, 1].
scam_keyword_count integer/null
Count of known scam keywords detected.
client_request_id string/null
Optional caller-side trace id (echoed in response).
A call is made on an account: it counts against an allowance and the publisher sees it, which is why this one asks who you are first.
5
tools declared
—
trust score
remote
via our gateway
—
p95 latency
What it does
When your AI agents make decisions or execute actions, how do you know those actions are safe, authorized and worth the risk? Quesen gives your infrastructure a deterministic trust and control layer that evaluates risk, applies defined policies and returns clear execution decisions before critical actions proceed.
Integrate Quesen through its API or MCP interface to assess activity, enforce risk thresholds and obtain structured decision evidence. Instead of relying entirely on an agent's own judgement, your systems can consult an independent authority before taking consequential actions.
Quesen also introduces the Agent Settlement Protocol (ASP), enabling signed, verifiable settlement quotes and receipts for agent-facing resources. Whether you are building autonomous workflows, agent platforms or AI, powered financial infrastructure, Quesen helps establish stronger controls, accountability and trust between autonomous systems.
Quickstart
# 1 — sign in once: npx mcprush@latest login
# it asks for a key from mcprush.com/dashboard#access
# 2 — install
npx mcprush@latest add quelum-wilson/quesen-mcp
# 3 — ask your agent for something these tools do
# quesen.validate, quesen.simulate, quesen.report and 2 more
Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither.
quesen 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 — this server runs on the publisher’s own infrastructure behind our gateway, and what you install is the connection to it.
Claude Codenot declared — it may still work
Claude Code has its own MCP command, and the key rides on it as a header — the gateway refuses a call that carries none. Claude Code reads MCPRUSH_KEY each time it connects, so the key stays out of its config: export your key from Access in your shell profile (macOS, Linux), or run setx MCPRUSH_KEY <your key> and open a new terminal (Windows). Or let npx mcprush@latest add quelum-wilson/quesen-mcp write the entry with the key for you; --scope user makes it available in every project.
claude mcp add --transport http --scope user quelum-wilson-quesen-deterministic-agent-decision https://mcprush.com/gw/quelum-wilson-quesen-deterministic-agent-decision/mcp --header 'Authorization: Bearer ${MCPRUSH_KEY}'Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install on mcprush: no card. The gateway still answers a key, so you sign in once — which is also what gives you saved lists, release alerts and a budget cap.
What it writes
One config entry pointing at the gateway. The server itself runs on the publisher’s own infrastructure, so 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.
Deterministic pre-decision risk validation for autonomous agents. Returns PROCEED / REVIEW / SKIP plus risk_score, confidence, and named conflict triggers. Same input -> same output; every response embeds engine_version + weights + thresholds for full replay.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain_age_days | integer/null | no | Age of the target domain in days. |
| engagement_ratio | number/null | no | Engagement ratio in [0, 1]. |
| scam_keyword_count | integer/null | no | Count of known scam keywords detected. |
| client_request_id | string/null | no | Optional caller-side trace id (echoed in response). |
Counterfactual scoring. Compare the baseline decision against a simulated decision under caller-supplied weights_override / thresholds_override. Free sales asset — not charged against key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain_age_days | integer/null | no | Age of the target domain in days. Same feature as quesen.validate; combined with the (possibly overridden) weights to produce a counterfactual risk score. |
| engagement_ratio | number/null | no | Engagement ratio in [0, 1]. Same feature as quesen.validate; used with the (possibly overridden) weights during simulation. |
| scam_keyword_count | integer/null | no | Count of known scam keywords detected. Same feature as quesen.validate; used with the (possibly overridden) weights. |
| weights_override | object/null | no | Optional per-feature weight override used ONLY for this simulation. When null (or omitted) the engine uses its production weights. Does NOT mutate global state. |
| thresholds_override | object/null | no | Optional decision-threshold override used ONLY for this simulation. When null the engine uses its production thresholds. Does NOT mutate global state. |
| client_request_id | string/null | no | Optional caller-side trace id. Echoed verbatim in the response for cross-system correlation. |
Post-decision outcome feedback. Accepts request_id + outcome (RUG/LOSS/OK/WIN/UNKNOWN) plus optional post-trade metadata. Aggregated deterministically for SKIP-rate vs realized-outcome correlation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | The request_id returned by a prior quesen.validate call. Ties the reported outcome back to the exact decision that produced it. |
| outcome | string | yes | Real-world outcome once known. RUG = rug-pull / total loss; LOSS = negative PnL; OK = neutral / no material result; WIN = positive PnL; UNKNOWN = outcome not yet observable. |
| notes | string/null | no | Optional free-text notes about the outcome (post-mortem, context, references). Stored verbatim for audit. |
| realized_pnl | number/null | no | Realized profit/loss in the caller's chosen unit (e.g. USD, SOL, ETH). Sign convention: positive = profit, negative = loss. Fed into the aggregate pnl_mean counter. |
| elapsed_seconds | integer/null | no | Seconds elapsed between the original quesen.validate decision and the observation of this outcome. Non-negative. |
| venue | string/null | no | Venue or platform where the trade/signal was executed (e.g. 'raydium', 'jupiter', 'uniswap-v3'). Free-form label for downstream grouping. |
| signal_hash | string/null | no | Optional hash/fingerprint of the original signal (URL, token address, message id) so outcomes can be joined across systems that don't share Quesen request_ids. |
| client_request_id | string/null | no | Optional caller-side trace id. Echoed verbatim in the response for cross-system correlation. |
Liveness probe. Returns engine_version and transport.
Takes no parameters.
Full engine configuration — weights, thresholds, versions.
Takes no parameters.
Free
$0 forever
- Every tool, no call limit, and mcprush charges nothing
- A buyer key from your dashboard — the gateway refuses a call without one
- Answers through our gateway, so every call is in your log
- 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 quesen or to call it, and its free tier carries no monthly call limit.
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: —
—Grade not published
No rule-by-rule report on file for this release
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.
This listing is a hosted endpoint: the publisher runs it and we connect to it. The scanner reads packages and source, and neither exists to read here, so there is no grade — not a withheld one, an unmeasured one. What can be checked instead is on Installation: what it asks to reach and what it writes.
Release history
The gateway serves every install the publisher’s current release, so a release cannot be pinned or rolled back to here yet. The history below is for reading; the current release on file is 0.1.0.
0.1.0
5 Nov 2026
latest- The version this listing went live with, after review.
—
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 quesen 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.