Skip to main content
Glama
LucasDelgado

Chop MCP TypeScript

by LucasDelgado
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Chop MCP TypeScript

No user-submitted related servers found.

    Related Servers

    • MCP REST API Server

      vinaykp
      F
      license
      Not graded
      quality
      D
      maintenance
      A server implementation of the Model Context Protocol (MCP) that provides REST API endpoints for managing and interacting with MCP resources.
      -

    • 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.
      207
      2
      MIT

    • 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.
      6
      Apache 2.0

    • Accela MCP

      Donatoni
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that wraps the Accela Construct API as a curated, capability-grouped tool set for Accela Civic Platform, safe by default with read-only access.
      1
      Apache 2.0

    • ConnectWise API Gateway MCP

      jasondsmith72
      F
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that provides a comprehensive interface for interacting with the ConnectWise Manage API, simplifying API discovery, execution, and management for both developers and AI assistants.
      7
      18
      -
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    D1.5/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to confuse it with. The tool's purpose, while not described, is inherently distinct by being the sole option.

    Naming Consistency3/5

    With a single tool, consistency cannot be assessed across multiple tools, but the tool name 'obtener-setup' uses a Spanish verb ('obtener') with a hyphenated noun, which is readable but lacks a pattern to evaluate against other tools. This places it in the middle of the scale due to the inability to judge consistency.

    Tool Count2/5

    One tool is generally too few for most server purposes, as it suggests a very limited or trivial scope, making it difficult to perform meaningful operations. For a server named 'Chop MCP TypeScript', which might imply code or development tasks, a single tool feels insufficient and mismatched.

    Completeness1/5

    The server has only one tool with no description, making it impossible to infer the domain or assess coverage. With no clear purpose or additional tools, the surface is severely incomplete and will likely cause agent failures due to lack of functionality.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources