Skip to main content
Glama
jkudish

jev-mcp

by jkudish
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to jev-mcp

No user-submitted related servers found.

    Related Servers

    • jev-mcp

      rashedInt32
      A
      license
      A
      quality
      C
      maintenance
      Enables typed, calibrated judgment calls through classify, score, check, and batched ask tools, each returning full probability distributions for programmatic decisions.
      5
      1
      MIT

    • Proofworks

      0x06cf
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to verify claims deterministically by computing arithmetic, ratios, and dates and matching statements against provided sources, returning a confidence ladder of certain, source-backed, or unverifiable.
      MIT

    • Sentinel

      MikeLegemah5799
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to score their outgoing responses against groundedness and prompt-injection risks mid-turn, returning allow, warn, or block verdicts before the response reaches the user.
      9 npm
      -

    • askjev

      pZacca
      A
      license
      A
      quality
      C
      maintenance
      Enables agents to get fast, calibrated probabilistic answers from Jev (Typesafe AI) to yes/no, scale, or choice questions about provided material, without using a generative model.
      1
      MIT

    • double-check-mcp

      jonathanxuu
      A
      license
      A
      quality
      B
      maintenance
      Enables production-grade answer verification for LLM agents by independently re-checking answers with a configurable verifier model, enforcing confidence policies, and producing Ed25519-signed, auditable verification results with optional web search and knowledge-base evidence.
      3
      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.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: verifying claims against evidence, screening text for prompt injection and relevance, and ranking candidates against a query. There is no meaningful overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow the same 'jev_' prefix plus a single verb in snake_case: jev_verify, jev_screen, jev_find. The pattern is uniform and predictable.

    Tool Count5/5

    Three tools is a reasonable, focused scope for this server. Each tool covers a distinct high-level capability and none feel redundant or excessive.

    Completeness4/5

    The set covers the main apparent workflows: verification, guardrail screening, and semantic finding. Minor gaps could exist around configuration or explanation, but the core surface feels complete for its focused purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources