Skip to main content
Glama
Gliana-Labs

GlianaAI MCP Server

Official
by Gliana-Labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to GlianaAI MCP Server

No user-submitted related servers found.

    Related Servers

    • omnicall-mcp

      ColinHughes2121
      F
      license
      Not graded
      quality
      C
      maintenance
      Keyless, pay-per-call AI gateway: 248 LLMs plus image/video/voice/music generation and live crypto, DeFi, markets, web-search and research tools through one MCP server. Pay per call in USDC via x402 on Base/Solana — no API key, no signup, free tier.
      -
    • NEX MCP Server by NEXAITECHAU

      NEX MCP Serverofficial

      NEXAITECHAU
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables any MCP client to access 11 AI inference and data tools, including chat, code, vision, embeddings, crypto prices, weather, geolocation, currency exchange, and WHOIS, with a free tier and paid USDC-on-Base endpoints.
      Apache 2.0
    • halowerk-mcp by halowerk

      halowerk-mcpofficial

      halowerk
      A
      license
      A
      quality
      C
      maintenance
      Provides access to 70 paid APIs as MCP tools with per-call and session budgets, paying via x402/USDC on Base without requiring an account or login. Includes a built-in allowlist of hosts and safe defaults to prevent unintended payments.
      14
      24 npm
      MIT

    • StatePulse API

      Ahmed-Achtatar
      A
      license
      Not graded
      quality
      B
      maintenance
      55+ pay-per-call tools for AI agents over MCP: live telemetry, blockchain/on-chain checks, environmental, transit, finance, and network utilities. No API key or signup — agents pay per request with x402 USDC micropayments (Base and Solana).
      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

    A4.3/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct concern: listing models vs. listing utility tools, pricing vs. schema vs. generation, and single-model generation vs. multi-model recipes. There is no meaningful overlap that would confuse an agent.

    Naming Consistency3/5

    Most tools follow a verb_noun pattern (list_models, get_price, get_schema, list_tools), but 'generate' is verb-only and 'tool' and 'recipe' are bare nouns. The mix is readable but not uniformly consistent.

    Tool Count5/5

    Seven tools is well-scoped for a server that covers both AI model access and utility tool execution. Each tool has a clear role without redundancy or bloat.

    Completeness4/5

    Core workflows (list, price, schema, generate, run utility, run recipe) are covered. However, file upload for media inputs is only available via an external HTTP endpoint, not an MCP tool, and there is no wallet management tool, leaving minor gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources