
Arbitype
io.github.Renwang-HuangPublished by GitHub account Renwang-Huangv0.7.0Updated Oct 24, 2026
Typed decision tools for AI agents, powered by TypeSafe Jev.
Overview
Arbitype is a local MCP server that gives an assistant typed decision tools — classify, score, check, verify, gate, route and review — backed by the TypeSafe Jе
- What you can do
- Classify, score and check: pick one label from unordered options, give an ordered rating, or get a probability for a single bounded criterion, each with a distribution. Verify and review: check several named claims independently, or get a holistic quality or risk assessment with evidence. Gate and route: turn checks and thresholds into pass, review or fail, or get one suggested next action without executing it. Evaluate and health: run a custom typed question set, or inspect local configuration and optionally provider health.
- When to use it
- Use it when an agent needs a bounded, structured judgment instead of free-form prose — for example routing a support request to one next action, verifying claims in a pull request, or gating a release against thresholds. It suits workflows that want a probability attached to a decision.
- Requirements
- Runs as a local stdio process, launched with uvx or installed from PyPI, so Python tooling is needed. Requires the TYPESAFE_API_KEY environment variable; an optional TYPESAFE_MODEL variable selects the model. It calls the TypeSafe Jev provider over HTTPS, so network access is required.
Installation
In SourceWeft
- Open Arbitype in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Arbitype
Typed decision tools for AI agents.
Classify · Score · Verify · Gate · Route · Review
MCP-native · Powered by TypeSafe Jev
[CI] [Latest release] [Arbitype on PyPI] [MIT license] [Python 3.10 or newer] [MCP 2026-07-28] [Arbitype listed in the MCP Registry]
Quick start · Why Arbitype? · Tools · Benchmarks · Documentation
What is Arbitype?
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.
Quick Start
The fastest way to connect an MCP host is a local STDIO server launched by uvx:
For a pinned, reproducible launch:
Or install the package into the current environment:
The API key stays in the process environment. It is not an MCP argument and is never printed to standard output.
Host setup
Inspect detected hosts before writing anything:
Then apply a reviewed plan:
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.
Configuration
At minimum, set TYPESAFE_API_KEY. To select a model explicitly:
See the full configuration reference for endpoints, timeouts, retries, and request/response limits.
Compatibility
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:
Why Arbitype?
Arbitype is designed around contracts and bounded decisions rather than free-form prose:
The decision flow is:
Real Use Cases
Start with one of the small, runnable fixtures:
The example outputs are illustrative fixtures. They are not live model results, accuracy claims, or authorization decisions.
Tools
Arbitype advertises nine read-only, idempotent MCP tools:
Tool Selection Guide
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.
Architecture
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.
Benchmark Snapshot
Recorded on the public 120-case Jev-mediated tool-selection evaluation:
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:
Security Boundaries
Arbitype is a local MCP adapter and typed decision layer. It is not:
- a sandbox for untrusted code;
- an authorization or identity system;
- a prompt-injection firewall;
- a security approval boundary; or
- an official TypeSafe AI product.
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.
Documentation
- Host setup
- Configuration reference
- MCP Registry migration
- Supply-chain posture
- Observability proposal
- Testing
- Benchmarks
- Contributing
- Security
- Official MCP Registry entry
- Glama listing (indexing and metadata refresh may lag publication)
Development
The test suite uses local fakes and does not need an API key:
The official MCP Python SDK interoperability smoke test is in scripts/official_sdk_smoke.py. A live Jev check is opt-in and paid:
Normal CI does not call the provider or run paid benchmarks.
Source: README.md at commit e0c3bc3
Tools
0Version history
2- v0.7.0LatestSep 22, 2026
- v0.6.0Sep 22, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts