Skip to main content
Glama

Related Servers

Alternatives to JEV Research MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to run local-first web research: intent-routed search across independent engines with reranking, a multi-stage fetch/crawl ladder, and document extraction. Results come back as signed-cursor, citation-bearing evidence envelopes, with an optional separately enabled profile for browser click/type actions.
      AGPL 3.0
    • 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
      959 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to retrieve verified web evidence via headless Chromium rendering, sitemap navigation, and search candidate discovery, returning clean Markdown, structured JSON, and verbatim quoted proof.
      15 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to perform cheap web recall by discovering candidates via You.com and ranking them with TypeSafe Jev, returning a small scored URL list with prompt-injection risk flags over MCP and REST.
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to perform web research over MCP: search with a real browser, fetch JS-rendered pages, download PDFs and convert them to Markdown, then search and page through large documents using bounded previews so the context window isn't flooded.
      BSD Zero Clause

    TDQS

    A3.5/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so there is no possibility of confusing it with another. Its purpose (answer a coding question with sourced evidence) is unambiguous.

    Naming Consistency4/5

    With a single tool named 'research', there is no pattern to violate, but it is a bare noun rather than a verb_noun convention. Consistency is trivially satisfied.

    Tool Count3/5

    One tool for an entire research server is borderline thin; a single rich entry point can work, but there is no separate way to list sources, refine results, or fetch a specific document. It sits at the low end of reasonable scoping.

    Completeness3/5

    The tool covers the core research lifecycle (query, sources, evidence, provenance, modes), but notable gaps remain: no way to retrieve or expand a specific source, no follow-up/refinement operations, and no metadata or health operation. Agents can work around these but with friction.