Quesen Deterministic Agent Decision Layer
REMOTE · WEB-PRODUCTION-3DF26.UP.RAILWAY.APP
Deterministic decision layer for autonomous agents: reproducible PROCEED/REVIEW/SKIP verdicts.
Available components
Last scanned (21 hours ago)
Scores higher than 8% of remote servers
Unreachable for 1 day in a row. Last reached 3 Nov 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Endpoint reachability: not serving MCP → unreachable ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- 14 Oct 26 −50
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.93 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- First check of Schema quality: unverified functional
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 90. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 83. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 63 to 73. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://web-production-3df26.up.railway.app/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of web-production-3df26.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://web-production-3df26.up.railway.app/mcp | Unreachable | ||
| http (plaintext) | http://web-production-3df26.up.railway.app/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
quesen.health ~19
Liveness probe. Returns engine_version and transport.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
quesen.report ~360
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client_request_id | string|null | – | Optional caller-side trace id. Echoed verbatim in the response for cross-system correlation. |
| elapsed_seconds | integer|null | – | Seconds elapsed between the original quesen.validate decision and the observation of this outcome. Non-negative. |
| notes | string|null | – | Optional free-text notes about the outcome (post-mortem, context, references). Stored verbatim for audit. |
| 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. |
| realized_pnl | number|null | – | 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. |
| 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. |
| signal_hash | string|null | – | 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. |
| venue | string|null | – | Venue or platform where the trade/signal was executed (e.g. 'raydium', 'jupiter', 'uniswap-v3'). Free-form label for downstream grouping. |
No output schema declared.
No examples provided.
quesen.simulate ~250
Counterfactual scoring. Compare the baseline decision against a simulated decision under caller-supplied weights_override / thresholds_override. Free sales asset — not charged against key.
| Name | Type | Req | Description |
|---|---|---|---|
| client_request_id | string|null | – | Optional caller-side trace id. Echoed verbatim in the response for cross-system correlation. |
| domain_age_days | integer|null | – | 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 | – | Engagement ratio in [0, 1]. Same feature as quesen.validate; used with the (possibly overridden) weights during simulation. |
| scam_keyword_count | integer|null | – | Count of known scam keywords detected. Same feature as quesen.validate; used with the (possibly overridden) weights. |
| thresholds_override | object|null | – | Optional decision-threshold override used ONLY for this simulation. When null the engine uses its production thresholds. Does NOT mutate global state. |
| weights_override | object|null | – | 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. |
No output schema declared.
No examples provided.
quesen.validate ~130
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client_request_id | string|null | – | Optional caller-side trace id (echoed in response). |
| 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. |
No output schema declared.
No examples provided.
quesen.version ~19
Full engine configuration — weights, thresholds, versions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Quesen Deterministic Agent Decision Layer MCP server?
Quesen Deterministic Agent Decision Layer is a hosted endpoint at https://web-production-3df26.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · web-production-3df26.up.railway.app
claude mcp add --transport http shxnque-quesen 'https://web-production-3df26.up.railway.app/mcp'
What is the Quesen Deterministic Agent Decision Layer MCP server?
Quesen Deterministic Agent Decision Layer is an MCP server listed in the public MCP registry as io.github.Shxnque/quesen. Deterministic decision layer for autonomous agents: reproducible PROCEED/REVIEW/SKIP verdicts. This page covers its hosted endpoint (https://web-production-3df26.up.railway.app/mcp).
Is the Quesen Deterministic Agent Decision Layer MCP server safe to use?
Quesen Deterministic Agent Decision Layer scores 23 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Quesen Deterministic Agent Decision Layer MCP server expose?
Quesen Deterministic Agent Decision Layer exposes 5 tools: quesen.validate, quesen.simulate, quesen.report, quesen.health, quesen.version. Their descriptions and schemas cost roughly 778 tokens of context every time the server is loaded.
Does the Quesen Deterministic Agent Decision Layer MCP server require authentication?
Its publisher declares no required credentials for Quesen Deterministic Agent Decision Layer. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Quesen Deterministic Agent Decision Layer MCP server still maintained?
Quesen Deterministic Agent Decision Layer is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.