Browser History Analysis MCP
Related Servers
Alternatives to Browser History Analysis MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP 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.3MIT
- AlicenseAqualityBmaintenanceA personal MCP server that analyzes your Spotify streaming history locally, enabling queries, artist insights, and recommendations using a local SQLite database.7MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP Server that enables AI assistants to interact with your local browsers.1,849 npm54MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that fetches web pages, extracts clean markdown (reducing token count), caches results, and provides searchable reading history.MIT
- AlicenseNot gradedqualityDmaintenanceA Python MCP server that loads and analyzes HAR files locally, providing structured summaries to AI assistants to avoid token explosion and sensitive content filtering.Apache 2.0
- AlicenseAqualityDmaintenanceA local MCP server that collects structured human input via browser forms and maintains a searchable history dashboard.33 npmMIT
TDQS
Scored across 7 tools
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.
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.
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.
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.