Skip to main content
Glama
ronantakizawa

Search History MCP Server

by ronantakizawa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Search History MCP Server

No user-submitted related servers found.

    Related Servers

    • blackmount-mcp by BlackMount-ai

      blackmount-mcpofficial

      BlackMount-ai
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to access and search local browser history, bookmarks, open tabs, and downloads for personalized context.
      MIT

    • HistoryMCP

      Jovillios
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides AI assistants access to browser history from SQLite databases, enabling reading and analysis of the last 100 visited URLs.
      -

    • MyChatArchive MCP Server

      1ch1n
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables semantic search across your local AI conversation history (ChatGPT, Claude, etc.) and provides tools to retrieve context, capture thoughts, and get profile summaries.
      65
      AGPL 3.0

    • AI Memory MCP

      optimaquantum
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to semantically search your entire local conversation history from Claude Desktop, ChatGPT and Claude Code, and to retrieve, browse, ingest and report on those conversations. All embeddings run locally, so no cloud, API keys, or data leave your machine.
      1
      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

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_most_visited retrieves frequently visited sites by visit count, get_recent_history retrieves entries by recency, and search_history performs keyword searches. There is no overlap in functionality, making tool selection unambiguous for an agent.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (get_most_visited, get_recent_history, search_history) using snake_case throughout. The naming is predictable and readable, with no deviations in style or convention.

    Tool Count4/5

    Three tools are reasonable for a search history server, covering core use cases: frequency analysis, recency retrieval, and search. However, it feels slightly thin as it lacks tools for operations like deleting history or getting specific entries by ID, which could enhance completeness.

    Completeness3/5

    The tools cover basic querying (frequency, recency, search) but lack update or delete operations, which are common in history management. There is no tool for getting a specific entry by URL or ID, creating potential dead ends for agents needing precise retrieval beyond search.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources