Skip to main content
Glama
KhiipAI

Khiip

Official
by KhiipAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to Khiip

No user-submitted related servers found.

    Related Servers

    • braintube-mcp

      lildaddyo
      F
      license
      A
      quality
      B
      maintenance
      Persistent knowledge-base MCP server. Semantic search with source citations over saved YouTube videos, podcasts, articles and PDFs — one endpoint for every MCP-capable AI client.
      28
      -

    • Lookout

      SylphxAI
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server enabling local-first web search, fetch, extract, and caching with citeable excerpts, no API key required. Supports research workflows for agents and apps.
      16 npm
      MIT
    • io.github.lsmman/fetchive by lsmman

      io.github.lsmman/fetchiveofficial

      lsmman
      A
      license
      A
      quality
      B
      maintenance
      MCP server for extracting links from text dumps, checking duplicates, extracting YouTube transcripts (with fallbacks including speech-to-text), and preparing workspace-ready page payloads for your note-taking or saving tools. It does not write to your workspace; it hands off prepared content to your existing tools.
      11
      1
      MIT

    • x-bookmarks-mcp

      p0ki
      A
      license
      Not graded
      quality
      D
      maintenance
      Fully local, privacy-first MCP server that turns exported X/Twitter bookmarks into a searchable, enriched knowledge base for Claude Desktop and Claude Code.
      2
      MIT

    • wigolo

      KnockOutEZ
      A
      license
      A
      quality
      A
      maintenance
      Provides local-first web intelligence over MCP with tools for search, fetch, crawl, extract, cache, find-similar, research, and autonomous agent loops, requiring no API keys.
      10
      839 npm
      5,245
      AGPL 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

    A4.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a distinct purpose: capturing a URL, fetching a capture, listing captures, semantic recall, refetching dimensions, and checking daemon status. No overlap in functionality.

    Naming Consistency4/5

    Tools follow a verb_noun pattern with snake_case (e.g., capture_url, get_capture). 'daemon_status' is a noun phrase but still clear and consistent in style. Minor deviation from verb-first naming.

    Tool Count5/5

    6 tools is well-scoped for a URL capture and retrieval server. Each tool addresses a core operation without unnecessary redundancy.

    Completeness4/5

    Covers create, read, list, search, and update (via refetch). Missing a delete tool, which is a notable gap for a complete lifecycle, but the core workflows are covered.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources