Skip to main content
Glama
aizukanne

ihyee-mcp

by aizukanne
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to ihyee-mcp

No user-submitted related servers found.

    Related Servers

    • mult-fetch-mcp-server

      lmcc-dev
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables AI assistants to fetch web content in multiple formats (HTML, JSON, text, Markdown) with intelligent content extraction, chunk management, and browser automation support.
      5
      52 npm
      15
      MIT

    • o3-search MCP

      yoshiko-pg
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables web search capabilities using OpenAI's o3 model, allowing AI assistants to perform text-based web searches and return AI-powered results.
      1
      112 npm
      288
      MIT

    • MCP2Tavily

      mcp2everything
      F
      license
      C
      quality
      D
      maintenance
      An MCP protocol server that enables web search functionality using the Tavily API, allowing AI assistants to perform internet searches in real-time.
      4
      4
      -

    • web-fetch-mcp

      xiaozhuABCD1234
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides web scraping and Bing search capabilities, supporting both static and dynamic content through Puppeteer. It allows AI assistants to extract page summaries, SEO metadata, and full text with automatic detection for headless browser rendering.
      GPL 3.0
    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

    A3.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: ihyee_fetch for direct URL content extraction, ihyee_render for JavaScript-heavy pages requiring full browser rendering, and ihyee_search for web search with result extraction. There is no overlap or ambiguity between these functions.

    Naming Consistency5/5

    All tool names follow a consistent 'ihyee_' prefix with descriptive suffixes (fetch, render, search) in snake_case. The naming pattern is uniform and predictable across all tools.

    Tool Count4/5

    Three tools is a reasonable count for a web content extraction server, covering core scenarios (direct fetch, JS rendering, search). It might feel slightly thin if advanced features like batch processing or filtering are expected, but it's well-scoped for the apparent purpose.

    Completeness4/5

    The toolset covers key web content extraction workflows: fetching from URLs, handling JavaScript-heavy pages, and searching the web. Minor gaps might include operations like caching, content filtering, or handling specific formats (e.g., PDFs), but the core domain is adequately addressed.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources