jev mcp
Provides the Jev Impact dashboard and install script to visualize Prometheus-scraped impact metrics in your own Grafana instance.
Exposes Jev impact metrics from the local event log as Prometheus series via jev meter serve, allowing Prometheus scrapers to collect them.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@jev mcptriage this CI failure transcript"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
jev-toolkit
A small stdio MCP server for TypeSafe/Jev with three tools: typesafe_ask for
structured judgments, typesafe_rank for ordering supplied candidates by
relevance, and typesafe_verify for checking claims against supplied evidence.
Calls use the TypeSafe System One API and are recorded in a local event log.
Built with Effect and TypeSafe's SDK. Bun >= 1.3.14 is required.
Install
git clone git@github.com:jbt95/jev-toolkit.git
cd jev-toolkit
bun install --frozen-lockfile
scripts/install.sh
export TYPESAFE_API_KEY=…Register Jev in a user-level harness config with:
jev install opencode
jev install pi
jev install omp
jev install claude-codeThe Pi command installs pi-mcp-adapter and requires the Pi CLI and network
access. All commands preserve unrelated MCP settings and set JEV_HARNESS
automatically. They do not store TYPESAFE_API_KEY; make sure the harness
process provides it to the MCP server. See docs/mcp.md for
configuration paths and tool schemas.
Related MCP server: jevcore-mcp
Development
The four gates are:
bun run lint
bun run format:check
bun run typecheck
bun run testThe application and CLI run on Bun; the Oxlint RuleTester fixture suite uses
Node >= 22.18 because that external test API is Node-only. Tests are offline:
they use fake transports, temporary files, and localhost only. TYPESAFE_API_KEY
is read at call time and never logged. Verification
redacts credentials and never writes claim or evidence text to the event log;
rank rejects common code, diff, and transcript patterns, redacts credentials,
and never logs query or candidate text. Its pattern checks are conservative,
not a complete content classifier. Ask state is caller-provided and should be
redacted by the caller.
This server cannot be deployed
Maintenance
Related MCP Connectors
Agent-native notes, tasks, dev-docs, vaults, sync & handoffs. MCP + OpenAPI dual surface.
Control plane for autonomous software labor. Agents claim objectives over MCP with audit trail.
Guarded MCP server for agent-readable business truth, provenance, readiness, and discovery.
Build and run grounded business agents over MCP: agents, knowledge bases, skills, Storylines.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables Cursor agents to route subagent tasks and gate reads, writes, and shell commands through fast TypeSafe Jev judgments, exposing tools for choice, scoring, and noul decisions.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP hosts to query Jev's typed decision model—yes/no, choice, and score—with calibrated probabilities, while defaulting to an offline mock and disclosing all egress unless explicitly enabled.31Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to submit bounded semantic-uncertainty judgments to the pinned TypeSafe Jev API, with tools for yes/no, choice, and score evaluations plus optional evidence or context selection.MIT
- AlicenseNot gradedqualityBmaintenanceProvides MCP tools that wrap Jev's finite typed judgments to give agents a semantic decision-control layer for task routing, pre-execution risk gating, and completion verification, keeping final execution authority in code.MIT