Skip to main content
Glama
Sign In
nakasyou

twitter_api_safe_relay_mcp

by nakasyou
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to twitter_api_safe_relay_mcp

No user-submitted related servers found.

    Related Servers

    • dot bridge

      rkz211
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables an agent to send arbitrary HTTPS API requests (GET, HEAD, POST, PUT, PATCH, DELETE, uploads) to saved services using stored auth keys, with request previews, idempotent write recording, and built-in Cookiejar site creation and deployment. Requests are pinned to the saved origin and auth header, with the service itself deciding what each request may do.
      MIT
    • Alidade MCP by alidade-ai

      Alidade MCPofficial

      alidade-ai
      A
      license
      A
      quality
      A
      maintenance
      Forwards every tool call to a hosted MCP backend and, when supplied with your own X API bearer token, fills in the text and engagement metrics of X posts returned by mention and semantic searches so agents see readable posts instead of bare IDs. Without a token it behaves exactly like the hosted server.
      12
      393 npm
      MIT

    • MCP Relay Server

      econ-watch
      F
      license
      Not graded
      quality
      D
      maintenance
      Exposes provider-specific tools and relays HTTP requests to configured providers like Supabase, Vercel, and Context7, enabling interaction with multiple external APIs through a unified MCP interface with configurable authentication and access controls.
      -

    • Gostman

      kunalgoesbyken
      A
      license
      A
      quality
      A
      maintenance
      API client for coding agents. Sends saved HTTP, GraphQL and gRPC requests, runs collections with their checks, and creates or edits requests over stdio or loopback HTTP, with secret values redacted and calls limited to an allowlist of hosts.
      16
      56
      MIT

    • Earl

      mathematic-inc
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to safely interact with external services (HTTP, GraphQL, gRPC, Bash, SQL) using HCL templates and OS keychain secrets, preventing prompt injection by keeping request details from the LLM.
      113
      Apache 2.0

    • ONE

      VirtechSRL-ai
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to connect once to self-hosted, user-owned upstream accounts and then discover and invoke granted tools through a single authenticated endpoint. Each client receives its own key with deny-by-default tool grants, while sensitive calls require durable human approval and credentials stay encrypted and never forwarded upstream.
      Apache 2.0
    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.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes: one fetches/curates request templates from the catalog, the other executes a single request against the relay. There is no overlap or ambiguity between them.

    Naming Consistency3/5

    Both tools use a similar 'twitter_' prefix, but one uses 'request' and the other 'request_catalog', which is a mild inconsistency in granularity. The names are readable but the pattern isn't perfectly parallel—'twitter_api_request' vs 'twitter_request_catalog' mixes the placement of 'api' and 'request'.

    Tool Count2/5

    Two tools feels extremely thin for a Twitter/X API surface, which is vast (timelines, tweets, users, friendships, DMs, media, trends). While the catalog tool cleverly bundles the numerous request types into a searchable interface, the overall surface is still very limited given the breadth of the domain.

    Completeness3/5

    The two-tool design is a clever pattern: the catalog surfaces templates for any operation and the executor handles them, so in principle the coverage is as deep as the catalog. However, there are no helper tools for authentication setup, session management, or error diagnosis, and the design forces agents to do two calls for every single operation, creating friction.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources