Skip to main content
Glama
AIddlx

mcp-test-stepfun

by AIddlx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-test-stepfun

No user-submitted related servers found.

    Related Servers

    • Kondukt by kondukt-dev

      Konduktofficial

      kondukt-dev
      A
      license
      Not graded
      quality
      C
      maintenance
      A developer toolkit for MCP servers that enables testing, validation, debugging, and scaffolding, and can be used as an MCP server for AI agents.
      10 npm
      5
      MIT

    • MCP Everything

      s2005
      A
      license
      Not graded
      quality
      D
      maintenance
      A test server implementing all features of the MCP protocol, including prompts, tools, resources, and sampling, designed for testing MCP clients rather than practical applications.
      MIT

    • Postmancer

      hijaz
      A
      license
      Not graded
      quality
      D
      maintenance
      A standalone MCP server for API testing and management, allowing AI assistants to interact with RESTful APIs through natural language.
      10 npm
      28
      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

    C2.6/5.0

    Scored across 9 tools

    Disambiguation1/5

    Three tools (capture_screen, take_screenshot, get_screen_image) appear to do the same thing, and push_server_onetime and push_server_persistent are deprecated duplicates of push_server. This creates significant ambiguity, making it hard for an agent to choose the correct tool.

    Naming Consistency2/5

    Tool names use snake_case but verb choice is inconsistent: 'capture', 'take', 'get' are used interchangeably for similar actions. Additionally, 'validate_date' is an unrelated utility that breaks the device-management naming pattern.

    Tool Count3/5

    At 9 tools, the count is within a reasonable range, but several tools are redundant or deprecated, making the set feel padded. The effective number of distinct, useful tools is smaller, so the scope is borderline.

    Completeness2/5

    The device-management domain is partially covered (connect, info, screen capture), but there are missing lifecycle operations like disconnect or file transfer, plus an unrelated date validation tool. Deprecated tools are left in, indicating an incomplete cleanup and an unclear domain boundary.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources