Skip to main content
Glama
mukiwu

jev-search-mcp

by mukiwu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to jev-search-mcp

No user-submitted related servers found.

    Related Servers

    • codex-web-search-mcp

      dhicoc
      A
      license
      A
      quality
      A
      maintenance
      Zero-dependency MCP server that wraps OpenAI Codex's standalone search endpoint into codex_web_search and codex_web_research tools for Claude Code, enabling real-time web search and multi-step deep research independent of the underlying model.
      2
      34 npm
      2
      MIT

    • agentfetch

      SID1ART
      A
      license
      Not graded
      quality
      D
      maintenance
      An open-source web retrieval MCP server that fetches, crawls, and searches the web, returning clean markdown for AI agents. It integrates with Claude MCP, LangChain, and other frameworks for agentic web access.
      1
      MIT

    • Nexus MCP Server

      adawalli
      A
      license
      Not graded
      quality
      D
      maintenance
      A production-ready Model Context Protocol server that brings AI-powered web search directly into development environments, providing intelligent search results with proper citations in Claude Desktop, Cursor, or any MCP-compatible client.
      108 npm
      23
      MIT

    • uvxwebsearchmcp

      DanielNMC
      A
      license
      Not graded
      quality
      B
      maintenance
      A zero-config web search and fetch MCP server for LLM agents, featuring multi-backend metasearch, persistent rolling cache, and structured error envelopes for retry-friendly interactions.
      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.9/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool exists, so there is no possibility of selecting the wrong tool. The tool's purpose is clearly distinct by default.

    Naming Consistency5/5

    The single tool name 'jev_search' follows a clear verb_noun pattern and aligns with the server name. With only one tool, there are no inconsistencies to evaluate.

    Tool Count4/5

    A single tool is appropriate for a dedicated search server, but the count is below the typical 3-15 range. The tool is comprehensive enough to avoid feeling thin.

    Completeness5/5

    The tool fully covers the search workflow, including source selection, time windows, and relevance scoring. No additional operations are needed for the server's stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources