Skip to main content
Glama
yryuu

MCP API Requester

by yryuu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to MCP API Requester

No user-submitted related servers found.

    Related Servers

    • MCP API Server

      fikri2992
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to make HTTP requests (GET, POST, PUT, DELETE) to external APIs through standardized MCP tools.
      4
      2
      MIT

    • fetch-url-raw

      cinit
      A
      license
      Not graded
      quality
      B
      maintenance
      A stateless MCP server that provides a configurable HTTP client tool for LLM agents, supporting custom methods, headers, bodies, timeouts, redirects, response size limits, DNS overrides, and TLS verification.
      MIT

    • Web Request MCP Server

      KS-GEN-AI
      A
      license
      A
      quality
      D
      maintenance
      A TypeScript-based MCP server that enables AI assistants to execute HTTP requests with full control over methods, headers, and body content. It facilitates seamless interaction with web APIs and endpoints through a versatile tool that handles automatic JSON formatting and response truncation.
      1
      MIT

    • mcp-http-request

      pavex
      F
      license
      A
      quality
      D
      maintenance
      Universal HTTP client tool for LLM agents. Enables Claude and other MCP-compatible agents to perform GET, POST, PUT, DELETE, and other HTTP requests to any URL, including localhost and internal network addresses.
      2
      -

    • mcp2api

      megamen32
      F
      license
      Not graded
      quality
      C
      maintenance
      Converts any MCP server into simple HTTP endpoints, enabling AI agents that only support HTTP (like ChatGPT Custom GPT or web_fetch) to use MCP tools.
      -
    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/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool exists, so there is no possibility of confusion or overlapping purposes. The single tool's purpose is clearly defined as making arbitrary HTTP requests.

    Naming Consistency5/5

    With a single tool named 'make_request', the naming follows a clear verb_noun pattern. There are no other tools to create inconsistency.

    Tool Count4/5

    The server has just one tool, which is slightly below the typical 3-15 range, but for a focused HTTP request utility this is reasonable. The tool is general-purpose and well-suited to the server's stated purpose.

    Completeness5/5

    The single tool covers the full scope of making HTTP requests: all methods, custom headers, body, and returns status, headers, and body. There are no obvious gaps in the server's intended functionality.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources