Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
MONARK
Overview
Description from the maker (original English)
Commit / defer / abstain over a conformal coverage region - not a probability of being right.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi0 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 0 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://mcp.monarkgate.tech/mcpRun this in your terminal
claude mcp add --transport http monark https://mcp.monarkgate.tech/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"monark": {
"url": "https://mcp.monarkgate.tech/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"monark": {
"type": "http",
"url": "https://mcp.monarkgate.tech/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://mcp.monarkgate.tech/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
- ! Caution
Maker matches the repo
The publisher (monarkgate.tech) is not the repo owner (KraidleAI); someone else may have listed it
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Otheri
- More stars than 0% of the other 32464 servers in this category
- Published to the registry more recently than 45% of the other 32464 servers in this category
- Basic checks equal to or better than 33% of the other 32464 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is MONARK safe?
It passed 0 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.4.0) reached the registry 2 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, yontu
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated yesterday
Install
yontu
by senrecep
Türkçe yazı denetimi: TDK kuralları, yapay zekâ izleri, metin türüne göre üslup.
Runs on your computerUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
MONARK
MONARK is a two-sided toolkit — an AI side and a DeFi side — built like a Swiss-army knife: one handle, several blades. The handle is the MONARK engine, the AI side: a coverage-controlled decision gate that emits commit | defer | abstain against a depletable authorization budget (B_t) — never a probability of being right — with the sensors that attest to what happened on chain, the frozen contracts they speak, the harness through which other AI agents reach it, and the agents that keep it adapted to DeFi as DeFi changes. The blades are the DeFi side: the on-chain applications it powers, each one grown from an empirical study of on-chain data before it is served. The first is MONARK Bell; the others are research leads.
Single token, single ticker (MONARK). The agents are applications, not tokens. This repository is the MONARK tokenisation layer, the eight frozen interface contracts (one of them, AttestedBook, upcoming until served) and the served pieces that let AI agents and DeFi meet on measured ground.
Two sides, one engine — the eleven components
The engine is eleven components: three sensors, one gate, one act, six distribution pieces. Each of them can serve both sides. Left: what it gives an AI agent connected to the MONARK MCP endpoint (today's four tools are attest · gate · cascade · calibrate; a component marked *planned* has no served tool yet). Right: what it gives the DeFi side — the on-chain applications it powers (in parentheses: the applications on the site's diagram; *wired* = declared in the registry today, *can serve* = a lead, not a delivered link).
| AI side — for an agent on our MCP | Component | DeFi side — DeFAI, for the applications | ||
|---|---|---|---|---|
attest: an attested price testimony (bytes, hash, named residual hypotheses) the agent can cite instead of a scraped number — origin and bytes, never truth. | Shōgen — sensor, attested perception · *built* | A price an application can defend when it spends, hedges or de-risks (can serve: Warden, Softlanding, Firebreak, Ballast). | ||
gate + calibrate: the agent submits a claim and gets `commit \ | defer \ | abstain`, an auditable region and the budget left — never a probability of being right. | Hikae — the gate, coverage-controlled inference · *built* | The decision primitive of every application (wired: Firebreak, Warden, Softlanding, Verdict, Ballast). Bell's gate is its own closed publication check; a gate class for its off-hours gap is planned. |
cascade: the agent asks what a lending book would liquidate along a price path (a transitional tool; it abstains, under_calib). Through gate, the class liquidation-eligible-coverage returns a conformal upper bound on a caller-carried liquidable amount in its committed stratum, calibrated on one recorded episode; the other strata abstain (under_calib) — stated on the wire. | Ukemi — act, liquidation-cascade survival · *built* | Reads the deleveraging queue or the position before it clears (wired: Firebreak, Softlanding). | ||
A daily, replayable redemption-flow timeline (state.json, timeline.jsonl) any agent can read, and the served gate class stable-run-velocity-24h through gate. | Narabi — sensor, redemption-run sensing · *built, served daily* | Redemption-run sensing for a treasury that holds the stable: a daily, replayable reading of the redemption flow, stated after the fact, never ahead of it (can serve: Warden, Ballast). | ||
| *planned*: attest a document or an event the agent must act on — bytes and hash, never a verdict on its truth. | Mokugeki — sensor, document / event attestation · *named* | The attested event a settled decision starts from (can serve: Verdict). | ||
| *planned*: ask, before routing a swap, whether the fill is exposed to LVR / toxic flow. | Kaihi — LVR / toxicity avoidance · *named* | The execution leg of a de-risk or a hedge that must not be picked off (can serve: Firebreak, Softlanding, Ballast). | ||
| *planned*: execute a swap under transaction-cost analysis, with the gate's decision attached. | Kessai — swap execution, TCA · *named* | The act leg — de-risk, ease down, rebalance (can serve: Firebreak, Softlanding, Ballast). | ||
| *planned*: quote and manage inventory for the agent's market-making. | Kamae — inventory market-making · *named* | Inventory-aware hedging for a treasury (can serve: Ballast). | ||
| *planned*: read a PT / YT curve as an attested rate surface. | Kyokusen — PT / YT curve · *named* | The rate surface a rate treasury steadies against (can serve: Ballast). | ||
| *planned*: the weekend / off-hours gap as a sensed quantity the agent can gate on. | Koyomi — weekend gap · *named* | The off-hours gap of tokenized equities, the very quantity Bell publishes (can serve: Bell). | ||
The door: discovery of the tools and the skill (MCP Registry tech.monarkgate/monark). | Genkan — the storefront / MCP entry point · *named* (the harness serves the door today) | Distribution of every application to the agents that consume it (can serve: all six). |
Measurement first. No piece of MONARK is designed on a whiteboard and shipped. Each one starts as an empirical study — a recorded liquidation book at an archive block, a redemption-flow series measured on calm windows, a census of trading halts, a session-by-session record of tokenized-equity fills — and the study's artefacts stay attached to the served piece: committed calibrations with their digests, replayable timelines with per-line hash chains, published signing keys. That is what we mean by an instrumented environment: an AI agent operating in DeFi through MONARK acts on attested readings and audited regions, and gets an explicit abstain where nothing is measured — instead of a guess dressed as a number.
Kept adapted. DeFi does not hold still: protocols upgrade, liquidation engines change shape, oracles and data feeds move, calibrations drift. The engine is built so that each of these is a *measured* event with a pre-registered response (a drift criterion, a new recorder, a new residual hypothesis, a versioned change to a contract). The adaptation agents are the part of the AI side that detects those events and prepares the response. They are on the roadmap, not yet shipped (see the maturity table below).
What is served today
Everything below is live, machine-readable, and replayable by a third party without an account:
| Surface | What it serves | Who consumes it |
|---|---|---|
https://mcp.monarkgate.tech/mcp · https://api.monarkgate.tech/openapi.json | The engine's four tools (attest · gate · cascade · calibrate) over MCP and a plain HTTP/JSON mirror; the served OpenAPI document states the served version | Any MCP-capable agent |
https://monarkgate.tech/narabi/state.json · timeline.jsonl | Narabi's tracker state and its append-only, per-line hash-chained daily timeline (one line per window, with the blocks it was read from) | Anyone replaying the tracker; the site's /narabi page |
https://monarkgate.tech/narabi/instrument.json | A diagnostic file beside the tracker, written once from a closed block of days (never by the daily job): tracker replays at alternative parameters and a permutation-assessed CUSUM; it claims no bound | Anyone auditing the tracker; no page reads it |
https://bell.monarkgate.tech/state.json · timeline.jsonl · provenance.json · bell/pubkey.json | MONARK Bell's signed publications: per-session fills, VWAP and volume for the listed tokenized equities, halt census, supply and proof-of-reserve residuals, the provenance of each run, the active Ed25519 key | Anyone verifying a publication; the site's /bell page |
https://dojo.monarkgate.tech/ · timeline.jsonl · dojo/pubkey.json · lines/ .jsonl · history/ .jsonl | MONARK Dōjō's hold snapshot: a dated, public record of the MONARK token balances held by each address, read from the chain through two distinct operators, with a hold score per address; the signed timeline, the published key, a day's lines file and the history file that a signed line of the timeline names by its SHA-256 | Anyone recomputing it; the site's /dojo page |
https://monarkgate.tech | The vitrine: every number on it is read from a committed, hashed copy of the served files above — never typed | Readers |
A surface that is not in this table is not served. A component that has no served surface is labelled *named*, not *built*, wherever it appears.
The backbone — the gate
Everything in MONARK plugs into one decision primitive. A sensor reads the world and attests to it; a predictor turns that reading into a claim; the gate conformalises the claim into a region at a target coverage and returns one of three actions against a depletable budget:
- commit — the region is tight enough to act on, and the budget can pay for it;
- defer — the reading is ambiguous; the gate waits for a better one;
- abstain — the gate cannot state a region it stands behind, so it says nothing and invents no success.
The gate never reports how likely it is to be correct. It reports a region you can audit and a budget you can watch — never a probability of being right.
Maturity (labelled by what is built)
The labels are the point: they say what exists today and what is only named.
| Side | Layer | What it is | Status | ||
|---|---|---|---|---|---|
| AI | Backbone — the gate | Hikae (coverage control) + the MONARK token's budget B_t; turns a sensor reading into `commit \ | defer \ | abstain` | Built — eight frozen contracts (AttestedBook upcoming until served) |
| AI | Sensors and acts | the engine's agents: sensors that attest, acts that execute, one token across all of them | 4 built (Shōgen · Hikae · Ukemi · Narabi) · 7 named | ||
| AI | Harness — the door | the same engine made reachable *by other AI agents* over HTTP / MCP | Built — public 4-tool MCP endpoint (attest · gate · cascade · calibrate) | ||
| AI | Adaptation agents | agents that recalibrate, onboard protocols, track liquidation mechanics and watch data sources | Roadmap — named, not shipped | ||
| DeFi | Applications — powered by the engine | one application per DeFi need, served with its own published artefacts | 1 built (MONARK Bell) · 5 research leads |
The engine — AI side
Built:
- Shōgen — attested perception: an attested price testimony — origin and bytes, never truth.
- Hikae — coverage-controlled inference: the gate.
- Ukemi — liquidation-cascade survival: a recorder reads a lending protocol's liquidation book at an archive block under a keyless RPC quorum and digests it (the AttestedBook contract). The served gate class
liquidation-eligible-coverageholds a committed calibration for one stratum of one recorded episode: for a caller-carried liquidable amount in that stratum it returns a conformal upper bound (the lower edge is 0 by construction), and every other stratum abstains (under_calib). The bound holds only if the amount was produced by the frozen close-factor rule, which the gate does not check, and no coverage is claimed on any other event — stated plainly on the wire. Thecascadetool is transitional and abstains by construc
Only the beginning is shown; read the rest in the repo