Skip to main content
Glama
jkudish

jev-mcp

by jkudish
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to jev-mcp

No user-submitted related servers found.

    Related Servers

    • jevbook MCP by jevbook

      jevbook MCPofficial

      jevbook
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to fact-check claims, conduct verified research, make typed decisions with calibrated probabilities, and scan token risks through a hosted server with no API key required.
      MIT

    • jev

      maxkimambo
      A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to query files, logs, and search results through TypeSafe Jev's typed, probabilistic answers, so they retrieve only the needed conclusion instead of raw context. Supports classification, scoring, yes/no checks, extraction, page ranking, and injection screening.
      11
      467 npm
      MIT

    • grounded-reasoning

      ALEXaquarius
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs and agents to verify multi-hop relational claims before asserting them, using zero-token relation-algebra proofs with precision guarantees. It supports opt-in calibration guards for entity normalization and relation transitivity.
      83 PyPI
      1
      MIT

    • jev-mcp

      rashedInt32
      A
      license
      A
      quality
      B
      maintenance
      Enables typed, calibrated judgment calls through classify, score, check, and batched ask tools, each returning full probability distributions for programmatic decisions.
      5
      467 npm
      7
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a clearly distinct input/output contract (e.g., verify vs. noul vs. audit vs. compare), and descriptions explicitly cross-reference when to use alternatives (gate vs. review, find vs. rerank). Overlaps are mitigated rather than ambiguous.

    Naming Consistency4/5

    All tools use consistent snake_case with the jev_ prefix, but jev_noul deviates from the otherwise uniform verb-based operation naming (verify, gate, screen, find, etc.), a minor inconsistency.

    Tool Count5/5

    12 tools sit well within the 3-15 range and each maps to a distinct reasoning primitive (verification, screening, retrieval, classification, decision, review, etc.), so none feels redundant.

    Completeness5/5

    The surface covers a full cognitive toolchain: input screening, extraction, auditing, verification, comparison, retrieval/find/rerank, classification, decision, patch review, and gated completion. No obvious lifecycle gap for the stated Jev reasoning domain.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources