TypeSafe
NPM · @FOREVERWORKS/MCP-TYPESAFE
Get calibrated yes or no answers, choices and scores from TypeSafe's Jev, for one item or 1000 rows.
Available components
Last scanned (10 hours ago)
Scores higher than 58% of npm servers
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 7 of 24 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to foreverworks/mcps). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability57
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1104 tokens (~368/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.89 ▲ functional
- 3 Nov 26 67
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@foreverworks/mcp-typesafe@0.1.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | foreverworks/mcps |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/foreverworks/mcps/.github/workflows/release.yml@refs/tags/release-2026-11-03.2 |
| Rekor log index | 3658026600 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:510c04969de8796f55a03fe8f697f7124ef90620b7575e4a511b6c077732f3a6b3e935f1ce1668e67fe8833978b5f7d829e564e98d2e5aa96f00972fb |
Background: How many MCP packages publish verified provenance →
Dependencies 24 packages
| Packages resolved | 24 |
|---|---|
| Stale | 7 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ask Ask Jev ~241
Ask TypeSafe's Jev, a System One model, typed questions about one state and get calibrated answers: a `noul` is the probability that a yes/no statement holds, a `choice` picks one of your options with a probability each, a `score` places the state on your ordered levels. Jev writes no text and does no multi-step reasoning: use it for fast, narrow judgments (routing, triage, relevance, a policy check) whose probabilities you then threshold. One narrow judgment per question; a no-match option where nothing may fit. A probability near 0.5 means undecided, not medium. About 0.5 s a call.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | – | A model from health. Default: the server's, jev-latest. |
| questions | object | yes | Your question id -> question. Every independent judgment about the same state goes in one call: they run together and cannot see each other. |
| state | – | yes | What is judged: text, or JSON with named fields (a record, a thread, a posting with its metadata) the questions can point at, e.g. `posting.location`. |
No output schema declared.
No examples provided.
ask_batch Ask Jev over many states ~745
The same questions over up to 1000 states, several requests at a time: triage postings, transactions, emails or passages without reading them all yourself. Replies with a summary per question (choice: counts; noul: mean and how many are >= 0.7 and <= 0.3; score: mean, min, max) and each row's compact answers (a noul's probability, a choice's pick and confidence, a score and its confidence). For a large batch pass list 'none' or 'failed' with save true: every row's full answers go to a JSONL file in the outbox and the reply names it with its sha256 and size. A row that fails is reported and the rest go on. Rows already in a file go as items_file, not typed into items: that keeps them out of your context and exactly as written. thresholds turn each answer into act, review or abstain; where lists only the rows that meet conditions, top only the k highest by a question, and counts tallies the answers (and verdicts) of the rows where keeps: over a large batch they keep the reply to the rows that matter. A client that asks for progress hears the rows done; cancelling stops the rows not yet asked.
| Name | Type | Req | Description |
|---|---|---|---|
| concurrency | integer | – | Requests in flight at once. |
| counts | boolean | – | Also tally each question's answers (a noul's yes/no/between, a choice's picks, a score's nearest levels) and verdicts over the rows where keeps. |
| items | array | – | The rows, typed into the call. Give items or items_file. |
| items_file | object | – | The rows as a UTF-8 file instead of items: JSONL, one {"id", "state"} object per line, or one JSON array of them; at most 1000, every row with an id above 20. The reply names its sha256 and size. Nev… |
| list | string | – | Which rows the reply lists; the summary always covers every row. |
| model | string | – | A model from health. Default: the server's, jev-latest. |
| probabilities | boolean | – | Also list each row's full distribution per choice and score. |
| questions | object | yes | Your question id -> question. Every independent judgment about the same state goes in one call: they run together and cannot see each other. |
| save | boolean | – | Also write every row's full answers to the outbox as JSONL. |
| thresholds | object | – | Question id -> thresholds: each row's answer to that question gets a verdict, act, review or abstain, taken on its certainty (a noul's |p - 0.5| x 2, a choice's or a score's confidence, rounded down… |
| top | object | – | Only the k rows (of those where keeps) with the highest value for one question, highest first. |
| where | object | – | Question id -> condition; the reply lists only the answered rows meeting every one, and says how many matched. E.g. {"urgent": true, "team": ["billing"], "mood": {"min": 1.5}}. Checked against the qu… |
No output schema declared.
No examples provided.
health Health ~36
Check that the TypeSafe API key is present and accepted, and list the models it can use. Run this before concluding the MCP is broken.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the TypeSafe MCP server?
TypeSafe runs locally as an npm package, launched with npx -y @foreverworks/mcp-typesafe. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @foreverworks/mcp-typesafe
claude mcp add com-foreverworks-typesafe -- npx -y @foreverworks/mcp-typesafe
What is the TypeSafe MCP server?
TypeSafe is an MCP server listed in the public MCP registry as com.foreverworks/typesafe. Get calibrated yes or no answers, choices and scores from TypeSafe's Jev, for one item or 1000 rows. This page covers its npm package (@foreverworks/mcp-typesafe).
Is the TypeSafe MCP server safe to use?
TypeSafe scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the TypeSafe MCP server expose?
TypeSafe exposes 3 tools: ask, ask_batch, health. Their descriptions and schemas cost roughly 1,022 tokens of context every time the server is loaded.
Is the TypeSafe MCP server still maintained?
TypeSafe is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the TypeSafe MCP server under?
TypeSafe declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.