TypeSafe AI Jev MCPサーバー
コミット 2026年10月25日Jev意思決定モデルを型定義されたツールとして公開し、ルーティング、トリアージ、リスクスコアリングのための構造化された回答と較正された確率を提供します。
別名 devbux/typesafe-mcp
- スター
- 0
- ツール
- 6
- ダウンロード数(30日間)
- —
- 最新バージョン
- —
- 最終コミット
- 2026年10月25日
- ライセンス
- MIT
TypeSafe AI Jev MCPとは
Jev意思決定モデルを型定義されたツールとして公開し、ルーティング、トリアージ、リスクスコアリングのための構造化された回答と較正された確率を提供します。 6個のツールを提供しており、jev_decide, jev_choice, jev_scoreなどがあります。
プロジェクトのREADMEから生成された概要
TypeSafe AI Jev MCP server について
エージェント型ワークフローを構築する開発者は、このサーバーを使用してJev意思決定モデルを統合し、自然言語ではない構造化された出力を得ることができます。会話形式のテキストを生成する代わりに、ツールはルーティング、トリアージ、リスクスコアリングなどの特定のタスクに対して、較正された確率と型定義された回答を提供します。これは、AIが文章ではなく正確なデータを返す必要がある「チャットではなく決定する」ステップに最適です。
サーバーはstdioを介してローカルで動作し、Claude Desktop、Cursor、VS CodeなどのMCPクライアントと互換性があります。実行には、TYPESAFE_API_KEY環境変数を通じて提供されるTypeSafe AIのAPIキーが必要です。ユーザーはnpxまたはbunxを使用してサーバーを実行できます。このシステムは、指示用の構造化されたJSONや、base64エンコードされたアセットとして渡される画像を含む、複雑な入力をサポートしています。
具体的なツールには、1回の呼び出しで複数の質問を行うjev_decide、ラベル付きの選択肢から選択するjev_choice、順序付きのスケールを使用するjev_score、真偽を判定するjev_noul、画像内のバウンディングボックスを特定するjev_boxが含まれます。また、利用可能なモデルバージョンを表示するjev_list_modelsも提供されています。
できること
- 1サポートチケットの自動ルーティングエージェントは1回の呼び出しで、チケットを部署ごとに分類し、緊急度スコアを割り当て、返金される可能性を予測できます。
プロジェクトの README から作成されています。すべてのユースケースは、その引用と照らし合わせて確認されています。
TypeSafe AI Jev MCPツール 6
READMEから検出jev_decidejev_choicejev_scorejev_nouljev_boxjev_list_models
| jev_decide | — | |
| jev_choice | — | |
| jev_score | — | |
| jev_noul | — | |
| jev_box | — | |
| jev_list_models | — |
設定
TYPESAFE_API_KEY
| 名前 | 説明 | 種類 |
|---|---|---|
| TYPESAFE_API_KEY | — |
自動チェック
実行日 2026年11月14日完全なレポート →まだ検証されていません。サーバーには80点のスコア、重大な問題がないこと、および検証に必要な十分なデータが必要です。 チェックの仕組み · 点数を上げるための改善点
- ソースリポジトリがリンクされており、アクセス可能devbux/typesafe-mcp is public and reachablegithub.com/devbux/typesafe-mcp ↗合格
- パッケージがこのリポジトリをソースとして指定未チェック
- ビルドの来歴 (Sigstore 証明)未チェック
- オープンソースライセンス (OSI)MITspdx.org/licenses/MIT.html ↗合格
- 過去1年以内にコミットまたはリリースありLast commit or release 2026-10-25github.com/devbux/typesafe-mcp ↗合格
- OpenSSF Scorecard未チェック
- パッケージ名が有名なパッケージに酷似していない未チェック
- パッケージおよびその依存関係に重大な勧告なし未チェック
- モデルへの隠れた指示がない6 tool descriptions and the README read; no override phrases, credential paths or hidden characters合格
- 破壊的なツールがラベル付けされているNo tool named like delete, drop or exec合格
- リモートエンドポイントが MCP ハンドシェイクに応答未チェック
README
GitHubで見るtypesafe-mcp
A standard Model Context Protocol (MCP)
server that exposes TypeSafe AI's Jev decision model as typed tools —
publishable to npm and runnable anywhere with npx or bunx.
npx -y @devbux/typesafe-mcp
What is Jev?
Jev is TypeSafe AI's System One decision model. It never generates prose. Instead, you give it:
- a
state— a situation described as text or structured JSON, and - a set of typed questions about that state,
and Jev returns typed answers with calibrated probabilities:
| Question type | You define | Jev returns |
|---|---|---|
choice |
2–255 labelled options (each with an optional description) | the chosen option, a confidence value, and a probability for every option |
score |
an ordered scale of level descriptions (at least 2) | a numeric score on your scale, confidence, and per-level probabilities |
noul |
a proposition (optionally with true/false descriptions) | a calibrated probability (0..1) that the proposition is true |
box |
what to find, and in which image | the target's bounding-box edges (top, bottom, left, right as fractions 0..1) and a confidence value |
Questions can also read images: pass pictures in an assets map and
reference them from the state, instructions, or criteria — see
Images. instructions and criteria accept structured JSON
(objects/arrays), not just strings.
Because the output is structured and calibrated rather than free text, Jev is well suited to routing, triage, moderation, risk scoring, prioritisation, and any other "decide, don't chat" step inside an agent workflow.
Requirements
- Node.js >= 18 (or Bun) to run the server.
- A TypeSafe AI API key (see Getting an API key).
Install & run
The server speaks MCP over stdio, so you normally don't run it by hand — your MCP client launches it. The commands below are how clients (or you, for a quick smoke test) start it.
npx (Node)
TYPESAFE_API_KEY=your-key npx -y @devbux/typesafe-mcp
bunx (Bun)
TYPESAFE_API_KEY=your-key bunx @devbux/typesafe-mcp
Global install (npm)
npm install -g @devbux/typesafe-mcp
TYPESAFE_API_KEY=your-key typesafe-mcp
Global install (Bun)
bun add -g @devbux/typesafe-mcp
TYPESAFE_API_KEY=your-key typesafe-mcp
The server starts even when
TYPESAFE_API_KEYis not set, so clients can still list its tools; each tool call then returns a clear error naming the missing variable instead of crashing.
Getting an API key
Create an API key in the TypeSafe console at
typesafe.ai, then expose it to the server as the
TYPESAFE_API_KEY environment variable. Never commit your key to source
control.
MCP client configuration
Generic (mcpServers JSON)
Most MCP clients (Claude Desktop, and many others) accept a configuration
like this — see also examples/mcp-config.json:
{
"mcpServers": {
"typesafe": {
"command": "npx",
"args": ["-y", "@devbux/typesafe-mcp"],
"env": {
"TYPESAFE_API_KEY": "YOUR_TYPESAFE_API_KEY"
}
}
}
}
Using Bun instead:
{
"mcpServers": {
"typesafe": {
"command": "bunx",
"args": ["@devbux/typesafe-mcp"],
"env": {
"TYPESAFE_API_KEY": "YOUR_TYPESAFE_API_KEY"
}
}
}
}
Claude Code
claude mcp add typesafe \
-e TYPESAFE_API_KEY=YOUR_TYPESAFE_API_KEY \
-- npx -y @devbux/typesafe-mcp
Cursor / VS Code
Cursor and VS Code use the same mcpServers JSON shape above (Cursor:
.cursor/mcp.json or Settings → MCP; VS Code: .vscode/mcp.json uses a
top-level "servers" key with the same per-server fields). Paste the generic
config and replace the placeholder key.
Configuration
| Environment variable | Default | Description |
|---|---|---|
TYPESAFE_API_KEY |
(unset) | Bearer API key for the TypeSafe AI API. Required for tool calls; the server still starts without it. |
TYPESAFE_BASE_URL |
https://api.typesafe.ai |
Base URL of the TypeSafe AI API. |
TYPESAFE_JEV_MODEL |
jev-latest |
Jev model id to request. Can be overridden per call with the tools' optional model argument. Use jev_list_models to see what is available. |
Tools
All tools return the Jev API response as JSON text content. Errors (missing
API key, HTTP 401/403/429/5xx, network failures, timeouts) are returned as MCP
tool errors (isError) with a clear message that includes the HTTP status —
never your API key.
| Tool | Inputs | Output |
|---|---|---|
jev_decide |
state (string | JSON object | JSON array), questions (map of name → typed question, at least 1), optional model, assets, long_context |
All answers in one call: { answers, model, usage } |
jev_choice |
state, instructions, options (object: label → description or null, 2–255), optional model, assets, long_context |
One Choice answer under the name answer |
jev_score |
state, instructions, levels (array of level descriptions, at least 2, ordered low → high), optional model, assets, long_context |
One Score answer under the name answer |
jev_noul |
state, instructions, optional criteria ({ "true": ..., "false": ... } descriptions), optional model, assets, long_context |
One Noul answer (probability 0..1) under the name answer |
jev_box |
state, instructions (what to find, and in which image), optional assets, model (default jev-1.14.0), long_context |
One Box answer (box edges + confidence) under the name answer |
jev_list_models |
(none) | { models: [{ name, description, release_date }] } |
assets and long_context are described under Images and
Long context.
Question shapes for jev_decide
{
"type": "choice",
"instructions": "Which department should handle this?",
"criteria": { "billing": "Payments and invoices", "technical": null }
}
{
"type": "score",
"instructions": "How urgent is this?",
"criteria": ["not urgent", "low", "medium", "high", "critical"]
}
{
"type": "noul",
"instructions": "Is a refund likely to be requested?"
// "criteria" is optional for noul and omitted when not provided
}
{
"type": "box",
"instructions": "the coffee mug in `kitchen_photo`"
// box takes no criteria; it needs an image in the request and Jev 1.14
}
Images
An image can go anywhere text can go in a request: in the state, in a
question's instructions, and in its criteria. Every decision tool accepts
an optional assets argument — a map from a reference string to an
image, base64-encoded:
{
"state": "Doorbell camera frame: doorbell_img",
"questions": {
"person_at_door": {
"type": "noul",
"instructions": "Is a person visible in doorbell_img?"
},
"person_where": {
"type": "box",
"instructions": "the person in `doorbell_img`"
}
},
"assets": {
"doorbell_img": { "data_base64": "<base64, no data: prefix>", "format": "jpg" }
},
"model": "jev-1.14.0"
}
Rules from the TypeSafe docs:
- Write each asset's reference wherever the image belongs (whole value or
inside a longer string). Every asset must be referenced at least once, or
the API returns
400— this server checks that before sending. Use distinctive references (a UUID is safest): references match as plain text, so a short one likecatcould also match insidecategory. - Formats: PNG or JPEG only, still images. Each image: at most 16 MiB, each side 280–1568 px; the request body and all images together are capped at 32 MiB. Images are never resized by the API — prepare them (upright, within the limits) before sending.
- Images are an opt-in "danger zone" feature: the server automatically sends
the
TypeSafe-Danger-Zone-Images: trueheader whenever a request has assets or a Box question. TypeSafe marks these features experimental — formats and limits may change between releases. - Jev 1.13 and 1.14 both accept images. Box questions need Jev 1.14:
send
jev-1.14.0orjev-previewas the model (jev_boxdefaults tojev-1.14.0). A Box answer is always a box, even when the target is absent — pair it with anoulpresence check when that matters. - The API also accepts multipart uploads; MCP tool calls carry JSON, so this server always uses the base64 form.
Long context
Jev's default context limits are 64k tokens per request and 32k per
question. Any decision tool accepts long_context: true, which sends the
TypeSafe-Danger-Zone-Long-Context: true header and raises both limits to
262k tokens. TypeSafe marks this experimental too: it is slower and less
accurate, so use it only when a request does not fit the default limits.
Worked example
A support ticket comes in. In one jev_decide call you can route it,
rate its urgency, and estimate refund risk:
Request (tool jev_decide):
{
"state": "Customer writes: 'I was charged twice for my subscription this month and I want my money back today. This is the second billing problem in three months.'",
"questions": {
"department": {
"type": "choice",
"instructions": "Which department should handle this ticket?",
"criteria": {
"billing": "Charges, invoices, payments and refunds",
"technical": "Product bugs and technical problems",
"sales": "Pricing, plans and new purchases"
}
},
"urgency": {
"type": "score",
"instructions": "How urgent is this ticket?",
"criteria": ["not urgent", "low", "medium", "high", "critical"]
},
"refund_likely": {
"type": "noul",
"instructions": "Is this customer likely to request a refund?"
}
}
}
Response (shape; exact values come from the live model):
{
"answers": {
"department": {
"type": "choice",
"choice": "billing",
"confidence": 0.91,
"probabilities": { "billing": 0.91, "technical": 0.06, "sales": 0.03 }
},
"urgency": {
"type": "score",
"score": 4,
"confidence": 0.8,
"probabilities": { "1": 0.02, "2": 0.05, "3": 0.13, "4": 0.55, "5": 0.25 }
},
"refund_likely": {
"type": "noul",
"noul": 0.72
}
},
"model": "jev-1.13.0",
"usage": { "input_tokens": 120, "output_tokens": 45 }
}
Development
git clone https://github.com/devbux/typesafe-mcp.git
cd typesafe-mcp
npm install
npm run dev # run the server from source with tsx (stdio)
npm run typecheck # tsc --noEmit
npm test # vitest (fake fetch — no live network calls)
npm run build # bundle to dist/index.js with tsup
npm start # run the built server
Project layout:
src/
index.ts stdio bootstrap
server.ts MCP server + the six jev_* tools (zod-validated)
config.ts environment parsing (TYPESAFE_*)
jev/
client.ts typed JevClient for POST /v1/systemone and GET /v1/models
types.ts request/response types for the Jev API
test/
client.test.ts JevClient + config unit tests
Publishing
Releases are published to npm by the Publish to npm GitHub Action
(.github/workflows/publish.yml):
- Bump the version in
package.json, updateCHANGELOG.md, and push. - Create a GitHub Release for the new version tag (or run the workflow
manually with
workflow_dispatch). - The workflow runs typecheck, tests, and build, then publishes with
npm publish --provenance --access public.
Notes:
- The workflow expects an
NPM_TOKENrepository secret (an npm automation token for an account/organisation that owns the@devbuxscope). - Provenance is enabled (
id-token: writepermission +--provenance), so each published version is linked to its GitHub Actions build. - This is a scoped package (
@devbux/typesafe-mcp);publishConfig.accessis set topublicinpackage.jsonso releases are publicly installable. prepublishOnlyalso runs typecheck, tests, and build for manual publishes.
License
MIT © 2026 devbux
TypeSafe AI Jev MCPのよくある質問
TypeSafe AI Jev MCPが提供するツールは
6個のツールを提供しており、jev_decide, jev_choice, jev_score, jev_noul, jev_boxなどがあります。
サーバーの実行には何が必要ですか?
Node.js version 18以上(またはBun)と、TypeSafe AIのAPIキーが必要です。