Skip to main content
Glama
0xamirreza

arvancai

by 0xamirreza
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to arvancai

No user-submitted related servers found.

    Related Servers

    • meshive-mcp by meshive

      meshive-mcpofficial

      meshive
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-capable agents to manage Meshive GPU Cloud resources, including account, workspaces, pods, storage, GPUs, templates, serverless deployments, tasks, assets, machines, and billing history.
      Apache 2.0

    • Cursor Cloud MCP

      BenItBuhner
      A
      license
      C
      quality
      C
      maintenance
      Enables any MCP client to triage cloud agents, projects, conversations, transcripts, pull requests, and files, including listing agents, reading transcripts, following runs, and sending follow-ups, using an API key or browser sign-in.
      29
      MIT

    • cloudflare-mcp

      Steph-ux
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a unified MCP interface to manage Cloudflare services including DNS, compute (Workers, KV, D1), storage (R2), AI, security, Radar, and a universal API gateway for any Cloudflare v4 endpoint.
      MIT

    • Bruno MCP Server

      brianconway
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables API development directly from MCP clients by creating and editing collections, running requests through the real CLI, generating documentation, and starting mock servers.
      74 npm
      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 130 tools

    Disambiguation3/5

    The server has many product-specific tools with clear prefixes (vod, live, vads, caas, ai, edge, storage), but generic invoke_*_api tools overlap heavily with the named tools, and similarly named operations exist across products (e.g., list_buckets vs list_ai_buckets vs list_storage_api_buckets, multiple get_domain variants). Descriptions give exact endpoints, but an agent could still misselect when product context is absent.

    Naming Consistency4/5

    Nearly all tools use snake_case verb_noun, but consistency is only mostly maintained: some tools carry product prefixes (list_vod_videos), some do not (list_domains, list_servers), and version suffixes appear (list_servers_v3 vs list_servers). The generic invoke_*_api tools follow a predictable pattern, and S3 head_* verbs are conventional. These are minor deviations rather than chaotic naming.

    Tool Count2/5

    130 tools is far beyond typical scoped MCP server size, and many named tools are made redundant by generic invoke_*_api tools that already cover large API surfaces. While the server spans many products, the count is overwhelming and likely to burden tool selection and agent reliability.

    Completeness4/5

    The surface is extremely broad across CDN, DNS, VOD, Live, VADS, IaaS, CaaS, AI, Edge, and Storage, with CRUD for many resources and generic API invokers to fill undocumented or missing operations. However, some named product areas lack full lifecycle operations (e.g., VOD channels/videos) and rely on generic invokers, so coverage is strong but not seamless.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources