Skip to main content
Glama
adrianba

edge-history-mcp

by adrianba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to edge-history-mcp

No user-submitted related servers found.

    Related Servers

    • Teams MCP

      hahsanayub
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server enabling AI assistants to interact with Microsoft Teams, users, chats, and organizational data via Microsoft Graph APIs.
      613 npm
      MIT

    • MCP Selenium Server

      sapangupta63
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server implementation that enables browser automation through standardized MCP clients, supporting features like navigation, element interaction, and screenshots across Chrome, Firefox, and Edge browsers.
      635 npm
      MIT

    • Bing Search MCP Server

      Adityas7netapp
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      A Model Context Protocol server that provides AI-grounded Bing search capabilities using the Azure AI Project Client. It enables intelligent web searches with automated citation tracking and URL extraction for seamless AI integration.
      -
    • AdsPower LocalAPI MCP Server by AdsPower

      AdsPower LocalAPI MCP Serverofficial

      AdsPower
      A
      license
      C
      quality
      C
      maintenance
      A Model Context Protocol server that enables LLMs to interact with AdsPower browser LocalAPI, allowing for operations like creating, opening, updating, and managing browser profiles with custom fingerprints.
      2
      27
      392 npm
      139
      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

    A4.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools are clearly distinct: list_profiles handles profile enumeration, get_history returns raw detailed visit entries, and get_history_summary provides an aggregated domain-level view. The descriptions explicitly explain when to use each, eliminating ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern. list_profiles and get_history use clear action-object phrasing, and get_history_summary extends get_history logically. No mixed conventions or vague verbs.

    Tool Count5/5

    With only three tools, the server is tightly scoped to browsing history retrieval. Each tool earns its place: profile discovery, raw history access, and summarization. The count is neither too thin nor bloated for the purpose.

    Completeness5/5

    The server covers the full read-only lifecycle for Edge history: discovering profiles, fetching detailed history with pagination and time filtering, and obtaining summaries. No obvious gaps exist within the narrow domain; the tools together handle typical use cases.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources