Skip to main content
Glama
yeison-liscano

Simple HTTP MCP Server

by yeison-liscano
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Simple HTTP MCP Server

No user-submitted related servers found.

    Related Servers

    • JSON-RPC

      xiaobenyang-com
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server based on OpenRPC, providing JSON-RPC function invocation and method discovery services.
      2
      1
      Apache 2.0

    • bun-mcp-server

      supershaneski
      A
      license
      Not graded
      quality
      B
      maintenance
      A lightweight HTTP-based MCP server built with Bun, enabling tool discovery and execution via JSON-RPC 2.0 over HTTP.
      15
      MIT

    • mcp-app

      echomodel
      F
      license
      Not graded
      quality
      D
      maintenance
      Framework for building and running MCP servers as HTTP services. Define tools as pure Python functions, wire up with two lines, run with one command.
      -

    • data-mcp

      Tattzy25
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server generated from an OpenAPI Specification, exposing tools via HTTP. It allows clients to invoke API operations using JSON-RPC 2.0 requests.
      4
      Artistic 2.0

    • remote-mcp

      mo3tssem
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables building and running MCP servers over streamable HTTP, exposing tools to AI assistants like Cursor, with examples of mounting multiple servers in FastAPI.
      -
    Install Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_called_tools retrieves internal tool usage history, get_time provides current time, get_weather fetches weather data for a location, and tool_that_access_request handles request access. There is no overlap in functionality, making tool selection unambiguous.

    Naming Consistency3/5

    Three tools follow a consistent 'get_*' verb_noun pattern (get_called_tools, get_time, get_weather), but tool_that_access_request deviates with a noun_verb structure and lacks the 'get' prefix. This mixed convention reduces predictability, though the names remain readable.

    Tool Count4/5

    With 4 tools, the count is reasonable for a simple HTTP server, avoiding bloat. However, the scope feels slightly thin as it lacks common HTTP operations like making requests or handling responses, which might be expected for such a server.

    Completeness2/5

    The tool set is severely incomplete for an HTTP server domain. It includes utility functions (time, weather) and internal tracking (called tools, request access) but lacks core HTTP operations such as send_request, get_response, or manage_connections, leaving obvious gaps that will hinder agent workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources