Skip to main content
Glama
Photalia

rikkahub-history-mcp

by Photalia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to rikkahub-history-mcp

No user-submitted related servers found.

    Related Servers

    • Discord Message Finder MCP

      DonghwanJeong
      F
      license
      A
      quality
      D
      maintenance
      Read-only MCP server for finding Discord messages. It enables searching guild messages, locating messages from jump URLs, and reading context around results.
      7
      1
      -

    • Reddit MCP Server

      jimbolo
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to scan, search, and read Reddit posts and comments using Reddit's public JSON endpoints, with no API credentials required.
      10 npm
      MIT
    • supragents-mcp by SuprAgents

      supragents-mcpofficial

      SuprAgents
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only research MCP server that provides search and browsing tools for Hacker News, Reddit, and Product Hunt. Works with zero API keys for basic use.
      MIT

    • HoYoLAB-MCP

      cyrne1-7208
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only access to HoYoLAB and HoYoWiki APIs, enabling search and retrieval of posts, wiki entries, and article content converted to Markdown.
      2
      AGPL 3.0

    • reddit-mcp

      hamzashahbaz
      A
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server that connects to the Reddit Data API to search posts, browse subreddits, read comments, view user profiles, and check trending content through the Model Context Protocol.
      2 npm
      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

    A4.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing recent conversations, searching across history, and retrieving context around a specific hit. There is no overlap or ambiguity in their roles.

    Naming Consistency4/5

    All names use snake_case and follow a similar noun-based pattern, but 'recent_conversations' is not a verb+noun like the other two. The inconsistency is minor and does not hinder understanding.

    Tool Count5/5

    With three tools, the set is tightly scoped to read-only history browsing. Each tool provides a distinct and necessary function without redundancy.

    Completeness3/5

    The tools cover listing, searching, and viewing context, but there is no way to retrieve a full conversation from a recent list or search result. This leaves a notable gap for agents that need the complete thread.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources