MONARK
REMOTE · MCP.MONARKGATE.TECH
Commit / defer / abstain over a conformal coverage region - not a probability of being right.
Available components
Last scanned (19 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Finance and Payments
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability52
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1603 tokens (~400/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 70% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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
- Stability: pass → 0.97 functional
- 12 Oct 26 0
- Stability: 0.97 → pass security
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 97. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 +1
- Tool “gate” rewrote its description, which is the text the model reads security
- Schema quality: 360 → 400 ▼ functional
- 6 Oct 26 +10
- Judged manipulation: unverified → pass ▲ security
- Schema quality: unverified → good ▲ functional
- 4 Oct 26 −9
- Judged manipulation: pass → unverified ▼ security
- Tool “gate” rewrote its description, which is the text the model reads security
- Schema quality: good → unverified ▼ functional
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 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.
- 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
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://mcp.monarkgate.tech/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.monarkgate.tech | CN=YE1,O=Let's Encrypt,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 59cfcafe50acc88486f4b926e38b004f9fc |
| SANs: mcp.monarkgate.tech | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.monarkgate.tech. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tech. | present | 2185 | 13 | Verified |
| monarkgate.tech. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.monarkgate.tech/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.monarkgate.tech/mcp | HTTPS enforced | 308 | https://mcp.monarkgate.tech/mcp |
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 →
attest ~38
projection of a committed Shōgen-verified witness (Binance BTCUSDT, self-notarized); the verifier is NOT executed at call time.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | yes | Honesty label carried OUTSIDE the frozen price (K-1): the witness is demonstrative, not probative. |
| price | object | yes | – |
| provenance | object | yes | – |
No examples provided.
calibrate ~187
split-conformal quantile at miscoverage α over caller-supplied nonconformity scores. MONARK does not see, store, or verify the caller's data or model, and does not validate that the supplied numbers are nonconformity scores of any model. Marginal 1−α coverage holds ONLY for future points exchangeable with the supplied scores; non-exchangeable data (e.g. distribution-shifted or time-ordered) voids it. Never a probability of being right.
| Name | Type | Req | Description |
|---|---|---|---|
| alpha | number | yes | Target miscoverage in the open interval (0,1). |
| nMin | integer | yes | Minimum calibration count (>= 1); n < nMin fails closed to under_calib. |
| scores | array | yes | Caller-supplied nonconformity scores (BYO: the caller owns the score function; MONARK stays agnostic). |
| Name | Type | Req | Description |
|---|---|---|---|
| alpha | number | yes | The target miscoverage (echoed). |
| label | string | yes | Honesty label (K-1): the marginal coverage holds only under exchangeability with the supplied scores. |
| method | – | yes | The conformal method — always split. |
| n | integer | yes | The number of supplied scores (echoed). |
| qhat | number|null | yes | The conformal quantile q̂, or null when the calibration is insufficient (fail-closed). |
| reason | string|null | yes | under_calib when q̂ is null, else null on success. |
| scores_sha256 | string | yes | scoresSha256(scores) in the caller's order: the audit tie to verdict.scores_sha256 (C2). |
No examples provided.
cascade ~342
Estimated liquidable amount from the real UKEMI cascade primitives (imported, never re-implemented): an Eisenberg-Noe clearing of the interbank system (L, e) with alpha=beta=1 yields the largest clearing vector L*; each node is then read as a leveraged position — collateral is its cleared balance-sheet value (external assets plus interbank receipts under L*), debt is its nominal obligations, liquidation threshold K=1 — and liquidableAmount sums the debts of the nodes whose cleared value, once shocked by the caller-carried 24h fraction, no longer covers their obligations. Shocking the whole cleared value is a v0 simplification; no source supports shocking interbank receivables. yhat is that liquidable amount: a monetary quantity in the reference asset, a single point that HIKAE conformalizes downstream — no guarantee, no score. Downstream, no cascade calibration is committed; the gate abstains (under_calib) on this class. This cascade tool is v0, replaced at U-5.
| Name | Type | Req | Description |
|---|---|---|---|
| L | array | yes | Nominal interbank liabilities matrix L[i][j] = what node i owes node j. Square, entries >= 0, zero diagonal. |
| e | array | yes | External assets (liquidation value) per node at the clearing date. One value per node. |
| producedAt | string | yes | Caller-carried RFC3339 instant, injected for hash stability (D4); the tool reads no clock. |
| shock | number | yes | 24h collateral price shock fraction in [0,1] — a declared fixture parameter, not a dynamics model. |
| Name | Type | Req | Description |
|---|---|---|---|
| features_digest | string | – | – |
| predictor_id | string | yes | – |
| produced_at | string | yes | – |
| schema_version | string | yes | – |
| task_class | string | yes | – |
| yhat | string|number | yes | – |
No examples provided.
gate ~1,036
Coverage-gated decision from the real HIKAE L3 policy (commit/defer/abstain) over a caller-carried authorization budget B_t. Dispatches on task_class. The class 'btc-dir-15m' is retired and answers a named refusal. For 'cascade-liquidable-24h' no cascade calibration is committed; the gate abstains (under_calib) on this class. For 'stable-run-velocity-24h' (Narabi: a redemption-flow velocity forecast) the gate holds a committed stable-run velocity calibration for the USDe synthetic-dollar-whitelisted-redeem population (key narabi:persistence-v2@eip155:1/erc20:0x4c9edd5852cd905f086c759e8383e09bff1e68b3) over calm-window redemption flow; coverage is stated under the split-conformal bound of Barber, Candes, Ramdas and Tibshirani 2023 (Thm 2, unit weights): at least 1 − α minus the average total-variation gap between calibration windows and the next one; that gap is not estimated here and the calibration is measured non-stationary across half-years, so 1 − α is the coverage only if that gap is zero (exchangeability), which is not assumed here; no coverage is measured; on that key it requires alpha = 0.1, nMin = 50; for any other population, no stable-run velocity calibration is committed for this population; the gate abstains (under_calib). For 'liquidation-eligible-coverage' (Ukemi: a per-account liquidable-amount class, class A only) the served region is a conformal upper bound on the liquidable amount for the calibrated class; the lower edge is 0 by construction, not a calibrated bound; abstains (under_calib) outside it; this class requires alpha = 0.01, nMin = 100; calibrated on one recorded episode; no coverage is claimed on any other event; the H-3 exchangeability check is a report, a YES licenses nothing more; the bound holds only if yhat was produced by the frozen close-factor rule on a mono-collateral WETH account at the first crossing, which the gate does not check. The 32 kata classes `{btc,eth,bnb,sol}-{dir,range,mae-down,mae-up}-{1h,4h}` are served from the…
| Name | Type | Req | Description |
|---|---|---|---|
| attested | object | – | – |
| params | object | yes | – |
| prediction | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| action | – | yes | – |
| allow | boolean | yes | – |
| intent | string|number|null | yes | – |
| reason | – | yes | – |
| remaining_budget | number | yes | – |
| request_sha256 | string | yes | – |
| schema_version | – | yes | – |
| tool | string | yes | – |
| verdict | object | yes | – |
No examples provided.
How do I install the MONARK MCP server?
MONARK is a hosted endpoint at https://mcp.monarkgate.tech/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 · mcp.monarkgate.tech
claude mcp add --transport http tech-monarkgate-monark 'https://mcp.monarkgate.tech/mcp'
What is the MONARK MCP server?
MONARK is an MCP server listed in the public MCP registry as tech.monarkgate/monark. Commit / defer / abstain over a conformal coverage region - not a probability of being right. This page covers its hosted endpoint (https://mcp.monarkgate.tech/mcp).
Is the MONARK MCP server safe to use?
MONARK scores 73 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 MONARK MCP server expose?
MONARK exposes 4 tools: gate, cascade, attest, calibrate. Their descriptions and schemas cost roughly 1,603 tokens of context every time the server is loaded.
Does the MONARK MCP server require authentication?
No. We connected to MONARK without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MONARK MCP server still maintained?
MONARK is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.