Skip to main content
Glama
Sign In
bitra

bitra

Official
by BijectiveLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to bitra

No user-submitted related servers found.

    Related Servers

    • CavalRe MCP Server

      RedRobotKK
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents to execute complex DeFi strategies safely and atomically with double-entry ledger accounting and atomic basket swaps.
      1
      -

    • AgentBroker MCP Server

      agentbroker-tech
      F
      license
      Not graded
      quality
      D
      maintenance
      AI-native cryptocurrency exchange built for autonomous agents. Register, deposit USDC, select a strategy, and trade 8 crypto pairs (BTC, ETH, SOL + more) programmatically — no KYC required. Includes sandbox with 10,000 virtual USDC for testing.
      -

    • forge-agent-gate

      forgeorbital
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI agents to execute prediction-market trades through a risk-control gateway that enforces signed mandates and generates proof trails for accountability.
      0
      MIT

    • Guardian MCP

      Dozie2001
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to propose stock, ETF, and crypto trades through Alpaca paper trading while enforcing deterministic policy rules and recording every decision in an audit trail.
      13 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

    A4.2/5.0

    Scored across 10 tools

    Disambiguation4/5

    Each tool targets a distinct pipeline stage or artifact (cost floor, dataset audit, event observation, registration, validation, run listing, run report, ladder, ledger), and descriptions explicitly route between near-pairs (list_runs vs read_run_report, show_ledger vs search_ledger). The only real overlap is the ledger pair, which is clearly signposted as whole-picture vs. query-specific, so misselection risk is low but not zero.

    Naming Consistency5/5

    Every tool follows a strict snake_case verb_noun pattern: show_ladder, list_runs, read_run_report, audit_dataset, check_cost_floor, check_registration, observe_events, search_ledger, show_ledger, validate_trades. The verb choices (show/list/read/audit/check/observe/search/validate) map predictably to what each tool does, with no casing or style deviations.

    Tool Count5/5

    Ten tools is well within the ideal band and each maps to a genuine stage of the research lifecycle: cost check, dataset audit, event observation, registration inspection, validation, plus run/ledger/ladder inspection. No tool looks redundant or padded.

    Completeness3/5

    The surface is deliberately read-only: there is no way to seal a pre-registration (only check one), write a verdict to the kill ledger, promote/demote a strategy, or launch a backtest/replay, all of which the descriptions reference as existing elsewhere. Core read and validation workflows are covered, but agents hitting the write side of the lifecycle will dead-end and must fall back to other surfaces.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled

    Resources