MCP.Market

Jev Decision MCP server

by amidabuddha·io.github.amidabuddha/jev-decision-mcp·v0.3.0·1 stars

Typed Jev decisions in one tool: choice, score, yes/no probabilities via any compatible endpoint.

B83/100grade B
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
Growing

1 stars124 downloads/wk

Reviews

Write one

Nobody has reviewed Jev Decision yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Jev Decision tools (1)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • jev_decide

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

no findings
  • Code scan7 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 3 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Jev Decision compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 65% of 48,255 servers
Tools
1
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
1
more than 65% of 28,688 servers
Downloads a week
124
more than 67% of 12,191 servers with a package

What its tools let an agent do: 1 read

Release history: 4 versions in the registry since 2026-09-23, latest 2026-10-17, typically one every 1 day.

Install Jev Decision in Claude Code, Cursor or VS Code

Runs npx -y jev-decision-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add jev-decision-mcp -- npx -y jev-decision-mcp
Add to Cursor

What the publisher says

From the Jev Decision repository's README, as published. We do not edit it. Read it on GitHub

Jev Decision MCP

A local stdio MCP server exposing one tool, jevdecide**, for typed decisions through the official TypeSafe API. Written in TypeScript with the official MCP and TypeSafe SDKs.

Independent community project; not affiliated with TypeSafe. Licensed under MIT.

Batch independent questions over the same context in one call. Answers retain their question IDs. The MCP returns judgments and token usage; the caller owns thresholds, escalation, and action execution.

Install from npm

Requires Node.js 22 or newer. The published package runs without cloning or building:

npx -y jev-decision-mcp@0.1.2

Set TYPESAFEAPIKEY in your MCP host's environment. For hosts that use mcpServers JSON configuration:

{
  "mcpServers": {
    "jev": {
      "command": "npx",
      "args": ["-y", "jev-decision-mcp@0.1.2"]
    }
  }
}

Node.js and npm must be installed and available on the host's PATH. If the host cannot resolve npx, use its platform-specific launcher or absolute path as documented by that host. GUI applications may have a different PATH from your terminal.

The server communicates over stdio; starting it in a terminal waits for an MCP client rather than opening a web page. The npm installation does not read a .env from the caller's working directory.

Package: jev-decision-mcp on npm.

Connect to Codex

For the npm package, merge this into your Codex config.toml:

[mcp_servers.jev]
command = "npx"
args = ["-y", "jev-decision-mcp@0.1.2"]
env_vars = ["TYPESAFE_API_KEY"]
tool_timeout_sec = 45

Set TYPESAFEAPIKEY in the environment that launches Codex; envvars forwards its existing value to the server. Keep the host tool timeout above JEVTIMEOUT_MS / 1000. See official Codex MCP configuration.

Setup from source

Requires Node.js 22 or newer.

git clone https://github.com/amidabuddha/jev-decision-mcp.git
cd jev-decision-mcp
npm ci
# Copy .env.example to .env and set TYPESAFE_API_KEY.
npm run build

Obtain the key from TypeSafe Console. Use an official TypeSafe key, rather than an OpenRouter or third-party gateway key.

.env is excluded by .gitignore. The server reads the .env beside this README even when started from another working directory. Existing process environment variables take precedence. Restart the MCP server after editing .env.

The server starts without a key so a host can discover the tool. Calls then return MISSINGAPIKEY. API traffic is fixed to https://api.typesafe.ai/v1/systemone; TYPESAFEBASEURL does not override it. State and questions are sent to TypeSafe and may incur API charges. The server does not persist inputs or decisions and disables SDK logging. Upstream error bodies are not exposed because they may echo submitted data.

Connect a local source build

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Jev Decision: common questions

Is Jev Decision MCP server safe?
Mostly: it is graded B (83/100). Read the Jev Decision safety report
How do I install Jev Decision?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Jev Decision need an API key?
Yes. The registry entry asks for API_KEY.
Is Jev Decision maintained?
The last commit was 4 days ago (2026-10-31). The latest release is v0.3.0.
What can I use instead of Jev Decision?
Servers from other publishers that do the same job: Ask Jev MCP server.
How does Jev Decision compare with other MCP servers?
safety score 83/100 (higher than 65% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Jev Decision

Same job from other publishers: the closest match first, then the best rated.

  • Ask Jev
    Evaluate state with typed choice, score, and probability questions.
    A