Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MONARK

REMOTE · MCP.MONARKGATE.TECH · SCANNED SEP 20

Commit / defer / abstain over a conformal coverage region - not a probability of being right.

+3 this week 65 Trust /100
Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability57
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1117 tokens (~279/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 Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 78% 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
Install

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

# add to Claude Code
claude mcp add --transport http tech-monarkgate-monark 'https://mcp.monarkgate.tech/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "tech-monarkgate-monark": {
      "url": "https://mcp.monarkgate.tech/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "tech-monarkgate-monark": {
      "type": "http",
      "url": "https://mcp.monarkgate.tech/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.tech-monarkgate-monark]
url = "https://mcp.monarkgate.tech/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tech-monarkgate-monark": {
      "type": "remote",
      "url": "https://mcp.monarkgate.tech/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add tech-monarkgate-monark --url 'https://mcp.monarkgate.tech/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  tech-monarkgate-monark:
    url: "https://mcp.monarkgate.tech/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "tech-monarkgate-monark": {
      "Transport": "http",
      "Url": "https://mcp.monarkgate.tech/mcp"
    }
  }
}
# add to Vellum
assistant mcp add tech-monarkgate-monark -t streamable-http -u 'https://mcp.monarkgate.tech/mcp'
// mcp.json
{
  "mcpServers": {
    "tech-monarkgate-monark": {
      "type": "http",
      "url": "https://mcp.monarkgate.tech/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 0
    • Server version: 1.0.0 → 0.4.0 functional
  • 18 Sept 26 0
    • Tool “gate” rewrote its description, which is the text the model reads security
    • Schema quality: 220 → 279 functional
  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1
    • Stability: unverified → 0.03 functional
  • 11 Sept 26 61

    First indexed and scored.

Diagnostics

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 20 Sept 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
MCP tools · 4 exposed · ~1,117 tokens

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 →

Tool Tokens
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.

NameTypeReqDescription
labelstringyesHonesty label carried OUTSIDE the frozen price (K-1): the witness is demonstrative, not probative.
priceobjectyes
provenanceobjectyes

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.

NameTypeReqDescription
alphanumberyesTarget miscoverage in the open interval (0,1).
nMinintegeryesMinimum calibration count (>= 1); n < nMin fails closed to under_calib.
scoresarrayyesCaller-supplied nonconformity scores (BYO: the caller owns the score function; MONARK stays agnostic).
NameTypeReqDescription
alphanumberyesThe target miscoverage (echoed).
labelstringyesHonesty label (K-1): the marginal coverage holds only under exchangeability with the supplied scores.
methodyesThe conformal method — always split.
nintegeryesThe number of supplied scores (echoed).
qhatnumber|nullyesThe conformal quantile q̂, or null when the calibration is insufficient (fail-closed).
reasonstring|nullyesunder_calib when q̂ is null, else null on success.
set_digeststringyescalibDigest(scores): recalculable by reference; the audit tie to verdict.calib_digest (C2).

No examples provided.

cascade ~329

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.

NameTypeReqDescription
LarrayyesNominal interbank liabilities matrix L[i][j] = what node i owes node j. Square, entries >= 0, zero diagonal.
earrayyesExternal assets (liquidation value) per node at the clearing date. One value per node.
producedAtstringyesCaller-carried RFC3339 instant, injected for hash stability (D4); the tool reads no clock.
shocknumberyes24h collateral price shock fraction in [0,1] — a declared fixture parameter, not a dynamics model.
NameTypeReqDescription
features_digeststring
predictor_idstringyes
produced_atstringyes
schema_versionstringyes
task_classstringyes
yhatstring|numberyes

No examples provided.

gate ~563

Coverage-gated decision from the real HIKAE L3 policy (commit/defer/abstain) over a caller-carried authorization budget B_t. Dispatches on task_class. For 'btc-dir-15m' it conformalizes against a committed synthetic calibration derived from the HIKAE S2a instrument (seed 101, n=300 draw), declared synthetic — a plumbing fixture, not a measured predictor. 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; every other (task_class, predictor_id) abstains (under_calib); for any other population, no stable-run velocity calibration is committed for this population; the gate abstains (under_calib). When the caller instead supplies a `calibration` (its own nonconformity scores plus a `mode`: `interval` ⇒ region [yhat - q̂, yhat + q̂], or `set` ⇒ a conformal set over caller `candidates`), the gate conformalizes against THOSE caller-supplied scores (BYO): 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;…

NameTypeReqDescription
paramsobjectyes
predictionobjectyes
NameTypeReqDescription
actionyes
allowbooleanyes
intentstring|number|nullyes
reasonyes
remaining_budgetnumberyes
schema_versionstringyes
toolstringyes
verdictobjectyes

No examples provided.

Common questions

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 65 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,117 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.