Spec Driven Development
제작자: formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
내 컴퓨터에서 실행★ 440MIT14개월 전 업데이트
설치
MONARK
개요
제작자가 쓴 설명(영어 원문)
Commit / defer / abstain over a conformal coverage region - not a probability of being right.
PopNx MCP의 세 기둥
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
- 사용자 의견i아직 리뷰가 없어요리뷰는 다음 단계에서 계정 기능과 함께 열려요
- 우리의 기본 점검i1개 중 0개 통과공개된 정보로 점검했으며, 코드는 아직 스캔하지 않았어요
- 사용 정도i아직 측정 안 함★ –
할 수 있는 일
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
- 연결 방식: 클라우드에서 실행
- 전송 방식: Streamable HTTP
- 카테고리: 기타
설치
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
설치하기 전에
- 기본 점검: 1개 중 0개 통과
- 제작자의 서버에서 실행돼요. 내가 요청한 내용은 제작자의 서버를 거쳐요.
- 레지스트리에 입력해야 할 키가 나와 있지 않아요.
필요한 것
- 클라우드에서 실행설치할 것 없음. 인터넷으로 연결돼요
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
웹, 데스크톱, 모바일의 Claude에서 쓸 수 있어요:
- Settings → Connectors 열기
- Add custom connector 누르기
- 아래 주소를 붙여 넣고 Add 누르기
- 로그인하라고 하면 제작자의 서비스에 로그인하기
https://mcp.monarkgate.tech/mcp터미널에서 이 명령어를 실행하세요
claude mcp add --transport http monark https://mcp.monarkgate.tech/mcp또는 설정을 직접 복사하기
프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"monark": {
"url": "https://mcp.monarkgate.tech/mcp"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
또는 설정을 직접 복사하기
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"monark": {
"type": "http",
"url": "https://mcp.monarkgate.tech/mcp"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요:
- 웹에서 ChatGPT 열기 → Settings → Connectors (Apps)
- Create 또는 Add 누르기(일부 요금제는 먼저 Advanced에서 Developer mode를 켜야 해요)
- 아래 주소를 붙여 넣고 이름을 정한 뒤 저장하기
- 로그인하라고 하면 제작자의 서비스에 로그인하기
https://mcp.monarkgate.tech/mcp메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
할 수 있는 일
아직 이 서버의 도구 목록을 읽지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요.
기본 점검i
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검
- ! 주의
제작자와 저장소 일치
게시자(monarkgate.tech)가 저장소 소유자(KraidleAI)가 아니에요. 다른 사람이 등록했을 수 있어요
- … 아직 점검 안 함
계속 관리되고 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
- … 아직 점검 안 함
라이선스 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
- … 아직 점검 안 함
엔드포인트 응답
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
- … 아직 점검 안 함
OAuth로 로그인
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
- … 아직 점검 안 함
도구 설명에 숨겨진 지시 없음
아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요
기타 카테고리의 다른 서버와 비교i
- 이 카테고리의 다른 서버 32433개 중 0%보다 스타가 많아요
- 이 카테고리의 다른 서버 32433개 중 45%보다 최근에 레지스트리에 공개됐어요
- 기본 점검 결과가 이 카테고리의 다른 서버 32433개 중 34%와 같거나 더 좋아요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
자주 묻는 질문
MONARK, 안전한가요?
해당하는 기본 점검 1개 중 0개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
어떤 키나 코드가 필요한가요?
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?
제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.
아직 관리되고 있나요?
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.4.0)은 2개월 전 레지스트리에 올라왔어요.
어떤 앱에서 쓸 수 있나요?
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
대신 쓸 수 있는 건 뭐가 있나요?
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, Symantec Cloud DLP AIops
대안
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
Remote Desktop Commander
제작자: desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
클라우드에서 실행★ 211어제 업데이트
설치
Symantec Cloud DLP AIops
제작자: AIops-tools
Governed Symantec Cloud DLP — 14 MCP tools, read-only with audit.
내 컴퓨터에서 실행오늘 업데이트
설치
제작자의 README
README 열기
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
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
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요