Skip to main content
Glama
AzielEliab

trades-runtime

by AzielEliab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to trades-runtime

No user-submitted related servers found.

    Related Servers

    • SDAR MCP Tasks Provider

      zhouwen-giser
      A
      license
      Not graded
      quality
      B
      maintenance
      A language-neutral runtime for the SEP-2663 task lifecycle and io.sdar/taskExecution Provider Profile, delegating resource facts and side effects to versioned gRPC/Protobuf adapters. Implemented in strict TypeScript, it provides durable scheduling, recovery, and a full test suite for conformance.
      1
      Apache 2.0
    • NeuroLink by juspay

      NeuroLinkofficial

      juspay
      A
      license
      Not graded
      quality
      A
      maintenance
      TypeScript AI SDK with a built-in MCP client: 58+ MCP servers over 4 transports (stdio, HTTP, SSE, WebSocket), 24+ LLM providers behind one interface, streaming, tool calling, RAG, voice (TTS/STT/realtime), and task scheduling.
      7,368 npm
      139
      MIT

    • Flow Weaver MCP Server

      synergenius-fw
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants and MCP-compatible editors to scaffold, edit, validate, compile, run, debug, and diff durable TypeScript workflows directly through conversation.
      7 npm
      Apache 2.0

    • Seiza

      SabilMurti
      F
      license
      Not graded
      quality
      B
      maintenance
      A native TypeScript AI orchestration engine and MCP server that coordinates autonomous sub-agents for complex coding tasks using DAG-based parallel execution and multi-agent consensus validation, with a real-time web dashboard.
      1
      -
    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

    A3.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool exposes a distinct concern: skill documentation, health status, usage statistics, and citation data. Health and stats are both read-only, but their descriptions clearly separate service health from view/download counts.

    Naming Consistency5/5

    All tools follow the same snake_case prefix pattern: trades_runtime_ followed by a specific noun (skill, health, stats, cite). This is consistent and predictable.

    Tool Count5/5

    Four tools is a well-scoped set for a runtime information server. Each tool covers a meaningful public-facing aspect without unnecessary bloat.

    Completeness5/5

    The server surfaces all expected public runtime concerns: usage instructions, health, statistics, and citation metadata. There are no obvious gaps for the stated read-only purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources