Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to ycli

No user-submitted related servers found.

    Related Servers

    • Enlace

      Caelos-Palacio
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes four stdio tools that let an agent research an application's documented interface, produce a validated single-use plan, and execute read-only operations against public HTTP JSON APIs, static HTML/JSON/text sources, and host-configured CLIs. Runs in-process with no listening port, accounts, or model dependency, returning bounded results while keeping inputs and outputs inside a host-enforced research-plan-execute lifecycle.
      MIT

    • finance-agents

      memefactorydev-design
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes named core, finance, supplier, intake, orders and reports tools over HTTP so Claude Code subagents can run a self-hosted finance back office: reading and coding supplier invoices, posting bills to the owner's QuickBooks, matching the bank, keeping the cashflow outlook, reconciling supplier statements and drafting reports and emails. Every write passes a posting gate and no payment, approval or customer invoice can be issued by an agent.
      MIT

    • Multi-MCP AI Assistant

      iarsingh
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes a single HTTP endpoint that aggregates tool definitions from GitHub, Kubernetes, and database namespaces, letting clients list available tools and invoke them by name. It provides health-check, tool-discovery, and tool-call routes for local, read-only experimentation without calling hosted models or applying production changes.
      MIT

    • openapi-mcp

      beernathan87
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes selected operations of an existing REST/OpenAPI app as MCP tools with generated schemas, permission annotations, and a risk class, requiring explicit opt-in before anything is listed and a second flag for destructive calls. Enforces security-first guardrails such as environment-injected auth, a single confined base URL, timeouts, response caps, rate limiting, and a local test console for trying tools.
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    C2.9/5.0

    Scored across 457 tools

    Disambiguation2/5

    Many tools overlap heavily: issue list/search/count/suggest, worklog list/search/global, wiki comment list/thread variants, multiple DataLens chart get/update/delete tools split by chart type, and direct vs inherited permission tools. Detailed descriptions often label siblings, but with 457 tools the boundaries blur and misselection is likely.

    Naming Consistency3/5

    Most names follow a snake_case service_resource_action pattern, but there are notable deviations such as tracker_me_get, status_get, schema_get, tracker_bulk_issues_list versus tracker_issues_update_bulk, and inconsistent noun/verb ordering. The pattern is still mostly readable, but not uniformly applied.

    Tool Count1/5

    457 tools is an extreme mismatch for any server, far beyond the 3-15 well-scoped range and well past the 25+ threshold. The surface spans Tracker, Wiki, Forms, and DataLens with many experimental and rarely used operations, making the set unwieldy.

    Completeness3/5

    Core CRUD coverage exists for many resources, but there are conspicuous gaps: dashboards have create and one widget tool but no list/get/delete, several org-global objects have no delete endpoint, and some binary download operations are CLI-only. Agents can work around some gaps, but notable dead ends remain.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources