Skip to main content
Glama
andrewconnell

senja-mcp

by andrewconnell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to senja-mcp

No user-submitted related servers found.

    Related Servers

    • X(Twitter) V2 MCP Server

      NexusX-MCP
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for interacting with the Twitter/X API v2, enabling AI assistants to retrieve tweets, post content, reply, quote, and more programmatically.
      1,020 npm
      13
      MIT

    • mcp-feedback-collector

      sanshao85
      A
      license
      Not graded
      quality
      D
      maintenance
      A MCP server that enables AI assistants to collect interactive user feedback with text and image support via a modern GUI.
      234
      MIT

    • Jilebi

      Datron
      A
      license
      Not graded
      quality
      B
      maintenance
      A plugin-based MCP server that enables AI assistants to interact with external systems through custom tools, resources, and prompts.
      4
      AGPL 3.0

    • MCP Gemini

      danjam
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that lets AI assistants use Google's Gemini models. Generate text, analyze images, review code, and more — with support for multi-turn conversations and web-grounded answers.
      52 npm
      1
      MIT

    • Reddit MCP Server

      Arindam200
      A
      license
      A
      quality
      F
      maintenance
      An MCP server that enables AI assistants to access and interact with Reddit content through features like user analysis, post retrieval, subreddit statistics, and authenticated posting capabilities.
      15
      301
      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.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct operation: listing all testimonials, fetching a single testimonial by ID, and creating a new one. There is no overlap or ambiguity between these three actions.

    Naming Consistency5/5

    All tool names follow the consistent verb_noun pattern: list_testimonials, get_testimonial, create_testimonial. The naming is predictable and uniform.

    Tool Count5/5

    With three tools covering the core actions for the testimonial domain, the count is well-scoped and appropriate for a simple resource-focused server.

    Completeness3/5

    The tool set covers list, get, and create, but lacks update and delete operations that would normally be expected for a complete testimonial lifecycle. This is a notable gap, though agents can still read and add testimonials.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources