AI 클라이언트가 단일 항목 또는 최대 1000행의 배치 데이터에 대해 보정된 yes/no 판단, 객관식 선택 또는 수치 점수를 얻을 수 있도록 합니다.
다른 이름 foreverworks/mcps, @foreverworks/mcp-typesafe
- 스타
- 5
- Tools
- 3
- 다운로드, 30일
- 678
- 최신 버전
- 0.1.3
- 마지막 커밋
- 2026년 11월 16일
- 라이선스
- MIT
TypeSafe MCP란?
AI 클라이언트가 단일 항목 또는 최대 1000행의 배치 데이터에 대해 보정된 yes/no 판단, 객관식 선택 또는 수치 점수를 얻을 수 있도록 합니다. 3개 도구를 제공합니다. 예: health, ask, ask_batch.
프로젝트 README에서 생성된 요약
TypeSafe MCP server 정보
TypeSafe는 AI 어시스턴트가 Jev 모델을 통해 보정되고 타입이 지정된 판단을 얻을 수 있는 인터페이스를 제공합니다. 사용자는 yes/no 확률, 최대 255개의 옵션 중 객관식 선택 또는 사용자 정의 척도에 따른 수치 점수를 요청할 수 있습니다. 이 MCP server는 AI가 다단계 추론이나 텍스트 생성을 수행할 필요 없이 트랜잭션, 이메일, 리뷰와 같은 대규모 데이터 세트를 분류해야 하는 개발자를 위해 설계되었습니다.
사용자는 ask 도구를 사용하여 단일 항목을 처리하거나 ask_batch를 통해 최대 1000행의 배치를 한 번에 처리할 수 있습니다. 이 서버는 JSONL 파일에서 데이터를 읽는 것을 지원하며 전체 결과를 outbox 디렉토리에 자동으로 저장할 수 있습니다. 사용하려면 TypeSafe 계정과 TYPESAFE_API_KEY_FILE 환경 변수를 통한 API key가 필요합니다. 이 서비스는 읽기 전용이며 비용은 입력 토큰에 따라 결정되고 응답은 보통 약 0.5초 내에 도착합니다.
활용 사례
- 1트랜잭션 배치 분류AI가 수백 개의 신용카드 트랜잭션을 식료품 또는 교통과 같은 특정 카테고리로 분류할 수 있습니다.
- 2지원 커뮤니케이션 분류개발자는 이 서버를 사용하여 수신된 이메일의 긴급도를 판단하고 올바른 부서에 배정할 수 있습니다.
- 3고위험 고객 식별고객 리뷰를 평가하여 이탈 가능성이 가장 높은 특정 개인을 찾을 수 있습니다.
- 4특정 데이터 행 필터링대규모 데이터 세트에서 특정 기준이나 신뢰도 임계값을 충족하는 항목만 추출할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
TypeSafe MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 TypeSafe MCP 설치
$ claude mcp add --env 'TYPESAFE_API_KEY_FILE=<TYPESAFE_API_KEY_FILE>' typesafe -- npx -y @foreverworks/mcp-typesafeCursor에 TypeSafe MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"typesafe": {
"command": "npx",
"args": [
"-y",
"@foreverworks/mcp-typesafe"
],
"env": {
"TYPESAFE_API_KEY_FILE": "<TYPESAFE_API_KEY_FILE>"
}
}
}
}VS Code에 TypeSafe MCP 설치
.vscode/mcp.json
{
"servers": {
"typesafe": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@foreverworks/mcp-typesafe"
],
"env": {
"TYPESAFE_API_KEY_FILE": "<TYPESAFE_API_KEY_FILE>"
}
}
}
}VS Code CLI에 TypeSafe MCP 설치
$ code --add-mcp '{"name":"typesafe","type":"stdio","command":"npx","args":["-y","@foreverworks/mcp-typesafe"],"env":{"TYPESAFE_API_KEY_FILE":"<TYPESAFE_API_KEY_FILE>"}}'Claude Desktop에 TypeSafe MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"typesafe": {
"command": "npx",
"args": [
"-y",
"@foreverworks/mcp-typesafe"
],
"env": {
"TYPESAFE_API_KEY_FILE": "<TYPESAFE_API_KEY_FILE>"
}
}
}
}Codex에 TypeSafe MCP 설치
$ codex mcp add typesafe --env 'TYPESAFE_API_KEY_FILE=<TYPESAFE_API_KEY_FILE>' -- npx -y @foreverworks/mcp-typesafeCodex config.toml에 TypeSafe MCP 설치
~/.codex/config.toml
[mcp_servers.typesafe] command = "npx" args = ["-y", "@foreverworks/mcp-typesafe"] [mcp_servers.typesafe.env] TYPESAFE_API_KEY_FILE = "<TYPESAFE_API_KEY_FILE>"
Gemini CLI에 TypeSafe MCP 설치
$ gemini mcp add -s user -e 'TYPESAFE_API_KEY_FILE=<TYPESAFE_API_KEY_FILE>' typesafe npx -- -y @foreverworks/mcp-typesafeGemini settings.json에 TypeSafe MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"typesafe": {
"command": "npx",
"args": [
"-y",
"@foreverworks/mcp-typesafe"
],
"env": {
"TYPESAFE_API_KEY_FILE": "<TYPESAFE_API_KEY_FILE>"
}
}
}
}TypeSafe MCP 도구 3
README에서 감지됨healthaskask_batch
| health | — | |
| ask | — | |
| ask_batch | — |
구성
TYPESAFE_API_KEY_FILE필수Path of a file holding your TypeSafe API key.
| 이름 | 설명 | 유형 |
|---|---|---|
| TYPESAFE_API_KEY_FILE | Path of a file holding your TypeSafe API key. | 필수 |
자동 검사
2026년 11월 12일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능통과
- 오픈 소스 라이선스 (OSI)통과
- 최근 1년 내 커밋 또는 릴리스통과
- 패키지 이름이 인기 패키지와 유사하지 않음통과
- 원격 엔드포인트가 HTTPS 사용검사되지 않음
- 파괴적인 도구에 라벨 표시됨통과
- 모델에 대한 숨겨진 지침 없음통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음통과
README
GitHub에서 보기TypeSafe MCP server
Ask TypeSafe's Jev for typed, calibrated judgments from
your AI assistant: how likely a yes/no statement is to hold, which of your
options fits, or where something sits on your own scale. Put the same
questions to one state or to up to 1000 rows at once, so the assistant can
triage postings, transactions or emails without reading each one. Every tool
is a read: nothing changes anywhere, and no tool is money.
You need a TypeSafe account and an API key from its console. Calls are billed by input tokens, a fraction of a cent each, and Jev answers in about half a second.
What you can ask
- "Go through the 300 postings in postings.jsonl and list the remote senior roles, with how sure Jev is of each."
- "Is this support email urgent, and which team should take it: billing, technical or sales?"
- "Sort last month's 600 card transactions into groceries, transport, software or other, and count each."
- "Rate these 40 reviews on how likely the customer is to leave, and show me the ten most at risk."
- "Which of these passages answer 'how do I reset my password'? Flag the ones Jev is unsure about for me to read."
Install
With Claude Code:
claude mcp add typesafe -e TYPESAFE_API_KEY_FILE="<path to API key file>" -- npx -y @foreverworks/mcp-typesafe
Claude Desktop (Settings, Developer, Edit Config) and most other clients read the same command as JSON:
{
"mcpServers": {
"typesafe": {
"command": "npx",
"args": ["-y", "@foreverworks/mcp-typesafe"],
"env": {
"TYPESAFE_API_KEY_FILE": "<path to API key file>"
}
}
}
}
Each runs the published package on Node 22.19 or newer. VS Code and the Claude Desktop bundle ask for TYPESAFE_API_KEY_FILE as they add the server. Cursor reads it from your environment instead (${env:TYPESAFE_API_KEY_FILE}), so set it before you start Cursor. Configuration says what it holds.
From a clone
git clone https://github.com/foreverworks/mcps.git && cd mcps
npm ci && npm run build
claude mcp add typesafe -e TYPESAFE_API_KEY_FILE="<path to API key file>" -- node "$PWD/servers/typesafe/dist/index.js"
In a JSON configuration, the command is node and its one argument the full path of servers/typesafe/dist/index.js. To share one running copy between several clients over HTTP, see docs/deploying.md.
Configuration
| Variable | Required | Meaning |
|---|---|---|
TYPESAFE_API_KEY_FILE |
yes | File holding the API key. For a local run, TYPESAFE_API_KEY may hold the key itself instead. |
TYPESAFE_MODEL |
no | The model a call uses when it names none. Default jev-latest, which tracks the newest Jev. |
TYPESAFE_BASE_URL |
no | Default https://api.typesafe.ai. |
TYPESAFE_OUTBOX_DIR |
no | Where ask_batch with save writes its JSONL. Default outbox/ in the state folder. Files are written 0640, so a deployment can share the folder with the user's group. |
TYPESAFE_STATE_DIR |
no | The state folder; the default is in docs/configuration.md. |
Without a key the server still starts and lists its tools, and each call
answers a config error naming the variable. ask_batch reads an
items_file from MCP_FILE_ROOTS; that and the other variables every server
shares are in docs/configuration.md.
Getting an API key
- Sign in at https://console.typesafe.ai and open Keys.
- Create a key and write it to a file only you (or the server's user) can read.
- Point
TYPESAFE_API_KEY_FILEat that file.
Give each deployment its own key, so you can revoke one alone and tell them apart on the console's usage page. Only a key from TypeSafe's own console works; a reseller's key works only through the reseller's gateway.
First run
Ask your assistant to run TypeSafe's health check. It answers with the API
it talks to, the default model, and the models your key reaches. A missing key
shows up here as config, a refused one as auth, before any batch starts.
Tools
read changes nothing; every tool here is a read (billing by input tokens is metering, not a payment).
| Tool | Access | What it does |
|---|---|---|
health |
read | Whether the key is present and accepted, and which models it reaches. |
ask |
read | Every question about one state in one round trip; the answers as TypeSafe returns them, less a Score's legend. |
ask_batch |
read | The same questions over up to 1000 states, typed in or from a file, 8 in flight by default: a summary per question and compact rows, with save the full rows as JSONL in the outbox. Optional act, review or abstain verdicts from your thresholds, and where, top and counts to list only the rows that matter. |
A question is a noul (the probability that a yes/no statement holds), a
choice (one of 2 to 255 options, with a probability for each) or a score
(the state placed on 2 to 10 levels you order from lowest to highest).
Troubleshooting
config. No key: set TYPESAFE_API_KEY_FILE to a file holding a key from
console.typesafe.ai/keys, or TYPESAFE_API_KEY for a local run.
auth. TypeSafe refused the key. Check it still exists at
console.typesafe.ai/keys, and replace the file if it was revoked.
input. The question cannot be answered as asked; the message names the
field (a choice needs at least two options, a score 2 to 10 levels). Above 20
rows, every row needs an id.
rate_limited. TypeSafe is still throttling or overloaded after the
server's own retries. Wait a minute, or send the batch with a lower
concurrency.
api. Any other refusal, a 5xx that outlived its retries, or no connection
(status 0). Retry once; if it persists, run health and read the server's log.
drift. TypeSafe answered in a shape this server does not know (its SDK's
types may have moved on). Please report it.
How it works
The network. An evaluation has no side effect, so every request
(POST /v1/systemone, GET /v1/models) may repeat: a 5xx or a dropped
connection is tried again, and a 429 or 529 ("overloaded") waits as a rate
limit, as TypeSafe's SDK does. A call times out after a minute. Every answer
is checked against the SDK's types (@typesafe-ai/sdk, types only, in
src/domain/schema.ts).
Batches. A batch goes on past a failed row and reports it, but stops at a failure that would fail every row (no key, a refused key), so a thousand rows do not each earn a 401. Answers join their rows by id, required above 20 rows: a position is only safe to join on while you can check the rows by eye.
Rows from a file. Instead of typing rows into items, pass items_file:
JSONL with one {"id", "state"} object per line, or a JSON array of them, by
path inside MCP_FILE_ROOTS (or as content_base64 with its sha256, from a
script). The rows never pass through a model, so they cannot change on the
way; a malformed row fails the call with its line number before anything is
sent. The reply names the file's sha256 and size.
Verdicts. With thresholds for a question, each row's answer gets act
(sure enough to act on), review (a person should look) or abstain (do not
use it), from the answer's certainty: for a noul |p - 0.5| x 2 (p 0.95 and
p 0.05 are both 0.9), for a choice or a score the confidence TypeSafe returns.
The certainty is rounded down to three places, the number the row shows, and
must be strictly above act_above to act and above review_above to be
reviewed. Once thresholds are tuned, pin model to a versioned Jev:
jev-latest can move under them.
Choosing rows. where lists only the answered rows meeting every
condition you give per question: true or false for a noul (a yes is
p >= 0.7, a no p <= 0.3, as the summary counts them), labels for a choice,
min and max on the value a row shows, and verdict. top keeps the k
rows with the highest p or score for one question, and counts tallies the
answers of the rows where kept; the summary still covers every row. Every
condition is checked before a request is sent, so a label that is not an
option fails the call, not a thousand rows.
npx tsx scripts/smoke.ts drives the built server against the real API, for
a few thousand input tokens: health, one ask per question type, a
five-row batch saved to the outbox, and one input failure that never reaches
TypeSafe.
Limitations
- Judgments only. Jev writes no text and does no multi-step reasoning.
Keep rules, lookups and arithmetic in code, and threshold the probabilities
(
thresholdsdoes it per question). wherejoins conditions with "and" only. For "or", read the rows from a saved JSONL, or ask a question that states the alternatives.- At most 1000 rows a call; split a larger set.
- A batch's reply lists every row unless
listsays otherwise. For a large batch, passlist: "none"or"failed"withsave, and read the JSONL.
Other servers for TypeSafe
Searched 2026-10-15. TypeSafe publishes none: its GitHub organisation has the SDKs, agent skills and an n8n node. Two community servers are on npm:
typesafe-mcp: stdio under Bun, the key in an environment variable, batches over files matched by a glob, with an act, review or abstain verdict per answer.@y0usaf/typesafe-mcp: stdio, oneevaluatetool.
This one exists for what neither offers: it also runs over HTTP as a service
of its own, with its key in a file the calling client never reads; it saves a
batch's full answers as JSONL in an outbox and names the file's SHA-256; and
it follows the conventions every server in this repository shares. Its
verdicts and its where, top and counts follow typesafe-mcp's, with
thresholds set per question rather than per call.
TypeSafe MCP 질문
TypeSafe MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --env 'TYPESAFE_API_KEY_FILE=<TYPESAFE_API_KEY_FILE>' typesafe -- npx -y @foreverworks/mcp-typesafe를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
TypeSafe MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
TypeSafe MCP는 어떤 도구를 제공하나요?
3개 도구를 제공합니다. 예: health, ask, ask_batch.
TypeSafe에서 어떤 종류의 답변을 받을 수 있나요?
'noul'(yes/no 문장의 확률), 'choice'(2개에서 255개 사이의 옵션 중 하나) 또는 'score'(2에서 10 단계 사이의 값)를 받을 수 있습니다.
한 번에 몇 개의 행을 처리할 수 있나요?
단일 배치 요청으로 최대 1000행까지 처리할 수 있습니다.
TypeSafe를 사용하면 데이터가 변경되나요?
아니요, 서버에서 제공하는 모든 도구는 읽기 전용 작업입니다.