mcpbeat Sign in

MONARK MCP Server

by monarkgate Your server? Claim it
answering

MONARK is answering right now. Last checked 1 min ago. It exposes 4 tools.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 58 days of history · worst day 97%
58 days agonow
100.0%
Uptime 24h
92 of 92 checks
4
Tools
read from the server
249 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 8

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 18 September 2026. No other catalogue keeps this.

6 Oct a tool description was rewritten gate
4 Oct a tool description was rewritten gate
25 Sep a tool description was rewritten gate
23 Sep 2 tool descriptions were rewritten cascade, gate
23 Sep a tool changed the parameters it asks for gate
18 Sep a tool description was rewritten gate
18 Sep a tool changed version

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add monark --transport http https://mcp.monarkgate.tech/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.monarkgate.tech/mcp
~/.codex/config.toml
[mcp_servers.monark]
url = "https://mcp.monarkgate.tech/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "monark": {
      "url": "https://mcp.monarkgate.tech/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "monark": {
      "type": "http",
      "url": "https://mcp.monarkgate.tech/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

attest
attest
projection of a committed Shōgen-verified witness (Binance BTCUSDT, self-notarized); the verifier is NOT executed at call time.
calibrate
calibrate
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.
cascade
cascade
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.
gate
gate
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 their policy tables, which hold no committed calibration row: every well-formed kata call abstains with no region (under_calib, or non_evaluable on a dir lean of exactly 0), and no kata class has an attestation subject. A kata call carries a `predictor_id` of the form `kata:<kataId>@<venue>/<SYMBOL>/<h>` (no bucket, <h> the class horizon), a `features_digest`, alpha = 0.45, nMin = 6 on dir classes and alpha = 0.01, nMin = 299 on the others, tau at most 1 on dir classes, and a `produced_at` on the class horizon grid, received at most 300 s after it; the full request rules are in section 9 of the contract 1.1.0 specification. 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; non-exchangeable data (e.g. distribution-shifted or time-ordered) voids it. Never a probability of being right. A caller-carried `attested` price must declare a subject consistent with the committed task class (exact committed-URL membership; BYO classes do not accept `attested` in P1); the attestation is carried by the caller and is not re-verified at call time (the verifier is not executed here); `attest` only projects the committed witness — verify a caller-carried attestation offline with the Shōgen verifier; no temporal binding in P1. No served class has a committed attestation subject (the retired 'btc-dir-15m' held the only one), so any `attested` is refused. The gate only emits a decision; it never calls the named tool.

Endpoints

URLTransportStateLatencyChecked
https://mcp.monarkgate.tech/mcp streamable-http answering 227 ms 1 min ago

Alternatives to MONARK

same job, measured the same way
Japan Drone Rule Pre-check (partial coverage)
by mk-career-planning

Partial pre-check of Japan drone rules at a point/time: DID, 150 m, night, airports. Not a go/no-go.

4 tools answering
Deputy Workforce MCP
by hyperdrift-io

Read-only Deputy coverage, workload, timesheet, availability, and staffing signals.

62 installs/wk local only
Resend Email MCP
by helbertparanhos

Complete Resend email MCP: full API coverage + debug layer (deliverability, DNS, bounces).

52 installs/wk local only
Domain Radar
by insight

High-Speed Domain Keyword Matrix, TLD Coverage & RDAP Availability Radar (Powered by insight.surf)

90 installs/wk local only
Falcon MCP
by rijul170

Community extension of CrowdStrike falcon-mcp with near-complete Falcon API coverage

106 installs/wk local only
Coverageunlocked
by edgeedgehq

AI-powered insurance denial appeals. Win probabilities, payer intelligence & regulatory leverage.

76 installs/wk local only
Conarium
by dogrucanemek-alt

Governed database access for AI assistants: masking, signed receipts, coverage reconciliation.

1 216 installs/wk local only
Capacity Option: price-cliff hedge for agent fleets
by textforagents

Coverage-gated capacity options: the right to today's model price until expiry, for a 4% premium.

6 tools answering

MONARK — questions

Answers built from our own checks of this server.

What can MONARK do?
It exposes 4 tools, read directly from the server on our last check. Among them: attest, calibrate, cascade, gate. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is MONARK working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 249 ms. The bar chart above shows every period we have measured.
Is MONARK still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect MONARK?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does MONARK need an API key?
No. MONARK completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is MONARK?
It answers our handshake in 249 ms on average, which is faster than 57% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.