Skip to main content
Glama
jethroHuang

Fetch API MCP Server

by jethroHuang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to Fetch API MCP Server

No user-submitted related servers found.

    Related Servers

    • Violett MCP Server

      luis0794
      F
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides tools for fetching and posting HTTP data, with built-in prompts for URL summarization and API analysis.
      2
      -

    • Curl MCP Server

      neeraj15022001
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that provides secure curl command execution capabilities, allowing AI assistants to make HTTP requests with configurable parameters and built-in security protections.
      4
      -

    • 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

    • OpenAPI MCP Server

      oneWalker
      A
      license
      Not graded
      quality
      D
      maintenance
      A server that implements the Model Context Protocol (MCP) with StreamableHTTP transport, enabling standardized interaction with model services through a RESTful API interface.
      335 npm
      2
      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

    D1.7/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'request' stands alone with no other tools to confuse it with.

    Naming Consistency5/5

    A single tool inherently has perfect naming consistency, as there are no other tool names to compare it against. The name 'request' is clear and follows no conflicting patterns.

    Tool Count2/5

    A single tool for an API server is too few for the apparent scope, as typical API interactions require multiple operations like GET, POST, PUT, DELETE. This minimal set is insufficient for comprehensive coverage.

    Completeness1/5

    The tool surface is severely incomplete for an API server domain. With only a generic 'request' tool and no descriptions, it lacks specific operations (e.g., for different HTTP methods or endpoints), making it impossible to perform standard CRUD workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources