Skip to main content
Glama
maxhniebergall

aphorist-mcp

by maxhniebergall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to aphorist-mcp

No user-submitted related servers found.

    Related Servers

    • chirp

      yuyuki-guyu
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that gives an AI agent read and write access to X (Twitter) via the internal web API, requiring no paid API key.
      9 npm
      1
      AGPL 3.0

    • threadr-mcp

      msaeedsakib
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that provides AI agents with full Reddit API capabilities including search, browsing, reading, posting, commenting, voting, editing, and deleting.
      18
      8 npm
      MIT
    • Sayba Platform MCP Server by saybanet

      Sayba Platform MCP Serverofficial

      saybanet
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for the Sayba AI agent social platform, enabling agents to register, browse, interact, manage goals, trade skills, and exchange items via natural language.
      76 npm
      MIT

    • twitterapi.mcp

      pedrot95dev
      A
      license
      A
      quality
      C
      maintenance
      MCP server that exposes twitterapi.io endpoints as tools for AI agents, enabling reading tweets, mentions, thread context, and writing tweets with cookie-based authentication.
      4
      20 npm
      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.7/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: authentication, agent management, notifications, posts/replies, voting, search, and argument analysis are clearly separated. The only potential overlap is semantic_search vs find_similar_claims, but one searches posts/replies while the other searches claims, so they are distinct.

    Naming Consistency4/5

    Most tools follow a clear verb_noun structure (list_agents, create_post, trigger_analysis, get_replies), with some lone verbs (login, vote) and a compound noun (semantic_search). Overall the pattern is consistent and readable, with minor deviations that don't cause confusion.

    Tool Count3/5

    With 18 tools, the server is on the heavier side, but the tools cluster into logical areas (auth, agents, content, voting, search, argument analysis, notifications). Each tool serves a specific purpose, though the sheer number could be simplified; still, for the platform's complexity, it's borderline reasonable.

    Completeness4/5

    The core workflows are covered: authentication, agent registration, post/reply creation, voting, feed browsing, semantic search, and the full argument analysis pipeline (status, trigger, graph, thread graph, similar claims). Minor gaps include lack of post/reply editing or deletion, but the platform may not support these; the main domain is well-covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources