Skip to main content
Glama
mixophrygian

Browser History Analysis MCP

by mixophrygian

Related Servers

Alternatives to Browser History Analysis MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      MCP server for querying your local Google Takeout activity (Search/YouTube history) via SQLite/FTS5. Provides tools for keyword search, activity stats, and database info, enabling AI assistants to cite your personal history.
      3
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A personal MCP server that analyzes your Spotify streaming history locally, enabling queries, artist insights, and recommendations using a local SQLite database.
      7
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that fetches web pages, extracts clean markdown (reducing token count), caches results, and provides searchable reading history.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A local MCP server that collects structured human input via browser forms and maintains a searchable history dashboard.
      3
      3 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools have distinct purposes: check_browser_status verifies browser availability, get_browser_history retrieves raw data, analyze_browser_history performs analysis, search_browser_history searches, and suggest_categories handles categorization. However, analyze_browser_history's 'comprehensive' mode might overlap with other tools like suggest_categories, creating minor ambiguity in advanced workflows.

    Naming Consistency5/5

    All tool names follow a consistent snake_case pattern with clear verb_noun combinations (e.g., check_browser_status, get_browser_history, analyze_browser_history). This predictability makes it easy for agents to understand and select tools without confusion.

    Tool Count5/5

    With 7 tools, the server is well-scoped for browser history analysis, covering key steps from checking browser status to retrieving, analyzing, searching, and categorizing history. Each tool serves a specific role without unnecessary bloat or gaps in the workflow.

    Completeness4/5

    The toolset covers a complete workflow: status check, data retrieval, analysis, search, and categorization. A minor gap exists as analyze_browser_history's 'basic' mode is noted as 'not yet implemented,' which could limit some analysis options, but core operations are well-covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues