Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
제작자가 쓴 설명(영어 원문)
Host-neutral MCP bridge for TypeSafe AI Jev judgments with typed review, routing, and gate tools.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
TYPESAFE_API_KEY비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요
{
"mcpServers": {
"typesafe": {
"command": "uvx",
"args": [
"typesafe-mcp"
],
"env": {
"TYPESAFE_API_KEY": "your-value"
}
}
}
}터미널에서 이 명령어를 실행하세요
claude mcp add typesafe --env TYPESAFE_API_KEY=your-value -- uvx typesafe-mcp실행하기 전에 빈 값을 채워 주세요.
프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"typesafe": {
"command": "uvx",
"args": [
"typesafe-mcp"
],
"env": {
"TYPESAFE_API_KEY": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"typesafe": {
"type": "stdio",
"command": "uvx",
"args": [
"typesafe-mcp"
],
"env": {
"TYPESAFE_API_KEY": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 8일 점검
레지스트리 이름이 GitHub 계정 Renwang-Huang 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
입력해야 할 값: TYPESAFE_API_KEY
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.5.2)은 2개월 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Python (uv)도 있어야 해요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, Tethered Trust
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:↓ 주간 다운로드i★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Fit, compatibility and recall checks for AI agents before they buy: verdicts, evidence, receipts.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
Typed decision tools for AI agents.
Classify · Score · Verify · Gate · Route · Review
MCP-native · Powered by TypeSafe Jev
Quick start · Why Arbitype? · Tools · Benchmarks · Documentation
Arbitype is an MCP-native typed decision layer for AI agents, powered by TypeSafe Jev. It turns probabilistic judgments into structured decision primitives that an agent or program can consume directly.
Arbitype is available on PyPI and the official MCP Registry.
[!NOTE]
Arbitype is an independent open-source project. It is not an official
TypeSafe AI product or an official integration for any particular agent host.
The fastest way to connect an MCP host is a local STDIO server launched by uvx:
export TYPESAFE_API_KEY="your-key"
uvx arbitype
For a pinned, reproducible launch:
uvx --from 'arbitype==0.7.0' arbitype
Or install the package into the current environment:
python -m pip install arbitype
arbitype
The API key stays in the process environment. It is not an MCP argument and is never printed to standard output.
Inspect detected hosts before writing anything:
arbitype setup --detect --dry-run
Then apply a reviewed plan:
arbitype setup codex
arbitype doctor --json
The setup flow is plan → unified diff → confirmation → backup → apply. Use claude, cursor, or vscode in place of codex. Detailed host formats, secret forwarding, --yes, --remove, ownership, and non-interactive behavior are documented in docs/HOST_SETUP.md.
At minimum, set TYPESAFE_API_KEY. To select a model explicitly:
export TYPESAFE_API_KEY="your-key"
export TYPESAFE_MODEL="jev-latest"
See the full configuration reference for endpoints, timeouts, retries, and request/response limits.
arbitype is the canonical distribution, Python package, and CLI. Existing TypeSafe MCP users should migrate to Arbitype; see docs/REGISTRY_MIGRATION.md.
For the safe migration from the historical distribution:
python -m pip uninstall typesafe-mcp
python -m pip install arbitype
| Surface | Canonical | Legacy compatibility |
|---|---|---|
| PyPI / CLI | arbitype | typesafe-mcp, typesafe-codex-mcp |
| Python imports | arbitype | typesafe_mcp, typesafe_codex_mcp |
| MCP tools | route, review | codex_route, codex_review |
Arbitype is designed around contracts and bounded decisions rather than free-form prose:
| Principle | What it means |
|---|---|
| Contract-first | Requests and provider responses are validated before they reach the agent. |
| Safe by default | Credentials stay out of MCP tool arguments and generated host configuration. |
| Agent-oriented | Purpose-built classify, verify, gate, route, review, and score primitives. |
| Portable | Zero third-party runtime dependencies and standard MCP STDIO. |
| Measured | Public tool-selection and decision-stability evaluation assets. |
The decision flow is:
free-form state
↓ TypeSafe Jev ↓ probabilistic judgment ↓ Arbitype ↓ typed decision + probability ↓ agent / code branch
Start with one of the small, runnable fixtures:
| Scenario | Tool | What it demonstrates |
|---|---|---|
| Support routing | route | Choose one next action without executing it. |
| PR verification | verify | Check several claims independently. |
| Release review | review / gate | Separate holistic review from thresholded checks. |
| Agent next step | route | Keep the next workflow action bounded. |
The example outputs are illustrative fixtures. They are not live model results, accuracy claims, or authorization decisions.
Arbitype advertises nine read-only, idempotent MCP tools:
| Tool | Use when | Result |
|---|---|---|
| evaluate | You need a custom typed Jev question set. | Raw typed Jev response. |
| classify | You need one choice from unordered labels. | Choice and probability distribution. |
| score | You need one ordered rating or level. | Weighted score and distribution. |
| check | You need a probability for one bounded criterion. | Noul yes/no probability. |
| verify | You need several named claims checked independently. | Noul answer per claim. |
| gate | You need checks and thresholds transformed into a signal. | pass, review, or fail. |
| route | You need one suggested next action. | One action; no action execution. |
| review | You need a holistic quality or risk assessment. | Review decision and evidence. |
| health | You need local diagnostics or an explicit live check. | Configuration and optional provider health. |
| Need | Use | Do not substitute |
|---|---|---|
| One unordered label | classify | route, which selects an action |
| One ordered rating | score | classify, which has no order |
| One bounded proposition | check | verify, which handles multiple claims |
| Several named claims | verify | review, which assesses a whole object |
| Checks plus thresholds | gate | review, which is holistic |
| One next action | route | classify, which returns a category |
| Whole diff, plan, release, or report | review | verify, which answers claim by claim |
Tool descriptions also state USE WHEN and DO NOT USE WHEN boundaries so hosts can select a primitive without hidden prompt conventions.
Probabilities and confidence are model signals, not proof. gate and review are advisory decision transformations, not authorization systems, security boundaries, or approval engines.
flowchart LR
host["AI Agent / MCP Host Codex · Claude · Cursor · VS Code"] arbitype["Arbitype Typed decision tools"] jev["TypeSafe Jev System One Model"] env["TYPESAFE_API_KEY process environment"]
host -->|MCP| arbitype arbitype -->|validated HTTPS| jev jev -->|typed probabilistic judgment| arbitype arbitype -->|structured decision| host env -. credential .-> arbitype
The public product is Arbitype; TypeSafe Jev is the current provider. Provider configuration intentionally keeps the TYPESAFE_* names because the credential and endpoint belong to TypeSafe.
Recorded on the public 120-case Jev-mediated tool-selection evaluation:
| Metric | Result |
|---|---|
| Tool-selection accuracy | 96.67% |
| Invalid-tool rate | 0% |
| Schema-valid rate | 100% |
This is a Jev-mediated evaluation over Arbitype's advertised MCP tool catalog. It is not a Codex, Claude, or Cursor host benchmark and is not a general model-performance guarantee.
Details and reproducible assets:
Arbitype is a local MCP adapter and typed decision layer. It is not:
It does not execute actions suggested by route, edit files, run shell commands, or treat model probabilities as proof. Read SECURITY.md before using live credentials.
The test suite uses local fakes and does not need an API key:
python3 -m unittest discover -s tests -v
python3 -m compileall -q . make check make release-check
The official MCP Python SDK interoperability smoke test is in scripts/official_sdk_smoke.py. A live Jev check is opt-in and paid:
TYPESAFE_API_KEY="your-key" arbitype doctor --live
Normal CI does not call the provider or run paid benchmarks.