# MONARK (remote · mcp.monarkgate.tech)

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

- Trust score: 65/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.monarkgate.tech`: 65/100 (this document), [markdown](https://verifymcp.io/servers/tech-monarkgate-monark/mcp.md), [page](https://verifymcp.io/servers/tech-monarkgate-monark/mcp)

## Channel facts

- Endpoint: `https://mcp.monarkgate.tech/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 78% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## 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.

### Claude

```bash
claude mcp add --transport http tech-monarkgate-monark 'https://mcp.monarkgate.tech/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tech-monarkgate-monark": {
      "url": "https://mcp.monarkgate.tech/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tech-monarkgate-monark": {
      "type": "http",
      "url": "https://mcp.monarkgate.tech/mcp"
    }
  }
}
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tech-monarkgate-monark --url 'https://mcp.monarkgate.tech/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tech-monarkgate-monark:
    url: "https://mcp.monarkgate.tech/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tech-monarkgate-monark": {
      "Transport": "http",
      "Url": "https://mcp.monarkgate.tech/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tech-monarkgate-monark -t streamable-http -u 'https://mcp.monarkgate.tech/mcp'
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 65, +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.

### 2026-09-19 (score 64, 0)

- [functional] Server version: 1.0.0 → 0.4.0

### 2026-09-18 (score 64, 0)

- [security] Tool “gate” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 220 → 279

### 2026-09-16 (score 64, +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.

### 2026-09-14 (score 63, +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.

### 2026-09-12 (score 62, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-11 (score 61)

First indexed and scored.

## MCP tools (4)

### `gate` (~563 tokens)

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;…

Input parameters:

- `params` (object, required)
- `prediction` (object, required)

Output parameters:

- `action`
- `allow` (boolean)
- `intent` (string|number|null)
- `reason`
- `remaining_budget` (number)
- `schema_version` (string)
- `tool` (string)
- `verdict` (object)

### `cascade` (~329 tokens)

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.

Input parameters:

- `L` (array, required): Nominal interbank liabilities matrix L[i][j] = what node i owes node j. Square, entries >= 0, zero diagonal.
- `e` (array, required): External assets (liquidation value) per node at the clearing date. One value per node.
- `producedAt` (string, required): Caller-carried RFC3339 instant, injected for hash stability (D4); the tool reads no clock.
- `shock` (number, required): 24h collateral price shock fraction in [0,1] — a declared fixture parameter, not a dynamics model.

Output parameters:

- `features_digest` (string)
- `predictor_id` (string)
- `produced_at` (string)
- `schema_version` (string)
- `task_class` (string)
- `yhat` (string|number)

### `attest` (~38 tokens)

projection of a committed Shōgen-verified witness (Binance BTCUSDT, self-notarized); the verifier is NOT executed at call time.

Output parameters:

- `label` (string): Honesty label carried OUTSIDE the frozen price (K-1): the witness is demonstrative, not probative.
- `price` (object)
- `provenance` (object)

### `calibrate` (~187 tokens)

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.

Input parameters:

- `alpha` (number, required): Target miscoverage in the open interval (0,1).
- `nMin` (integer, required): Minimum calibration count (>= 1); n < nMin fails closed to under_calib.
- `scores` (array, required): Caller-supplied nonconformity scores (BYO: the caller owns the score function; MONARK stays agnostic).

Output parameters:

- `alpha` (number): The target miscoverage (echoed).
- `label` (string): Honesty label (K-1): the marginal coverage holds only under exchangeability with the supplied scores.
- `method`: The conformal method — always split.
- `n` (integer): The number of supplied scores (echoed).
- `qhat` (number|null): The conformal quantile q̂, or null when the calibration is insufficient (fail-closed).
- `reason` (string|null): under_calib when q̂ is null, else null on success.
- `set_digest` (string): calibDigest(scores): recalculable by reference; the audit tie to verdict.calib_digest (C2).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tech-monarkgate-monark/mcp#diagnostics

## Score history

- 2026-09-20: 65
- 2026-09-19: 64
- 2026-09-18: 64
- 2026-09-17: 64
- 2026-09-16: 64
- 2026-09-15: 63
- 2026-09-14: 63
- 2026-09-13: 62
- 2026-09-12: 62
- 2026-09-11: 61

## 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.

## Links

- Remote endpoint: https://mcp.monarkgate.tech/mcp
- Repository: https://github.com/KraidleAI/monark
- Website: https://monarkgate.tech/
- Changelog RSS feed: https://verifymcp.io/servers/tech-monarkgate-monark/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/tech-monarkgate-monark/mcp.json
- HTML version of this page: https://verifymcp.io/servers/tech-monarkgate-monark/mcp