Skip to main content
Glama
Sign In
routstr-mcp

routstr-mcp

by ashen0x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to routstr-mcp

No user-submitted related servers found.

    Related Servers

    • lightningprox-mcp

      unixlamadev-spec
      A
      license
      A
      quality
      B
      maintenance
      Pay-per-request AI with Bitcoin Lightning: Claude, GPT, Gemini, DeepSeek, Mistral and more. Load a prepaid spend token, no account or provider API keys. You only pay for successful calls.
      5
      223 npm
      2
      MIT

    • SatRank

      proofoftrust21
      A
      license
      Not graded
      quality
      D
      maintenance
      Lightning Network trust oracle for AI agents. Provides real-time node reachability checks, trust scores, and personalized pathfinding for 17,000+ Lightning nodes via 12 MCP tools.
      3 npm
      AGPL 3.0
    • OffRouter MCP

      OffRouter MCPofficial

      offrouter
      A
      license
      A
      quality
      C
      maintenance
      Enables agents to send prompts to multiple hosted language models with prompts encrypted on the local machine to a verified GPU-TEE enclave key, returning answers with per-call costs and signed receipts. Also supports side-by-side model comparison, balance and spend checks, and on-demand enclave attestation verification.
      5
      318 npm
      MIT

    • Maximum Sats MCP

      joelklabo
      A
      license
      A
      quality
      D
      maintenance
      Provides tools for AI agents to access Bitcoin, Lightning Network, and Nostr knowledge, including real-time network statistics and Web of Trust reputation data. It features an integrated Lightning Network payment system for micro-transactions and query-based interactions.
      12
      6 npm
      2
      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

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a clearly distinct action: discovery (find_models), single-model query (ask), multi-model comparison (council), and wallet inspection (balance). The only close pair, ask vs council, is explicitly separated by 'one model' vs '2 to 5 models at once'. An agent can select correctly from names alone.

    Naming Consistency3/5

    Names mix verbs (ask, find_models) with bare nouns (council, balance), so there is no predictable verb_noun pattern. Each name is still short and readable, but the convention is inconsistent across the set.

    Tool Count4/5

    Four tools is on the thin side but each maps to a genuine step in the workflow: find a model, query one, compare several, check funds. Nothing is redundant and nothing feels bolted on.

    Completeness3/5

    The read/query lifecycle is covered, but there is no tool to actually add sats to the balance (only a description of 'how to add more'), and no request/cost history for auditing spend. These gaps force agents into dead ends for anything beyond a one-shot query.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources