Skip to main content
Glama
luis0794

Violett MCP Server

by luis0794
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Violett MCP Server

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

    • Swagger/OpenAPI MCP Server

      gulbaki
      A
      license
      D
      quality
      D
      maintenance
      A Model Context Protocol server that enables LLMs to explore and interact with API specifications by providing tools for loading, browsing, and getting detailed information about API endpoints.
      4
      12 npm
      14
      ISC

    • 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
      -

    • OpenAPI MCP Server

      rahgadda
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol Server that enables LLMs to interact with and execute REST API calls through natural language prompts, supporting GET/PUT/POST/PATCH operations on configured APIs.
      318 PyPI
      6
      Apache 2.0

    • Fetch API MCP Server

      jethroHuang
      A
      license
      D
      quality
      D
      maintenance
      A Model Context Protocol server that enables sending customizable HTTP requests with support for various methods, headers, and data formats, returning parsed responses automatically.
      1
      2 npm
      1
      ISC
    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

    B3.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: fetch_url performs HTTP GET requests to retrieve content, while post_data performs HTTP POST requests to send data. There is no overlap or ambiguity between them, as they target different HTTP methods and actions.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern: fetch_url and post_data. The naming is predictable and readable, with no deviations in style or convention, making it easy for agents to understand their functions.

    Tool Count2/5

    With only 2 tools, the server feels thin for a general-purpose HTTP client. While it covers basic GET and POST operations, it lacks other common HTTP methods (e.g., PUT, DELETE, PATCH) and related utilities (e.g., headers, authentication), making it under-scoped for typical HTTP tasks.

    Completeness2/5

    The tool surface is severely incomplete for an HTTP server. It only supports GET and POST, missing essential operations like PUT, DELETE, PATCH, and configuration tools for headers or authentication. This will cause agent failures when more complex HTTP interactions are needed.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources