Skip to main content
Glama
JEdward7777

js-translation-helps-proxy

by JEdward7777
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to js-translation-helps-proxy

No user-submitted related servers found.

    Related Servers

    • iLEAP MCP

      bernard357
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query product footprints, inspect transport activity data, and submit events from iLEAP-conformant endpoints through natural language, using MCP tools over Streamable-HTTP or stdio.
      1
      MIT

    • Bible MCP Server

      geosp
      F
      license
      A
      quality
      F
      maintenance
      Enables AI assistants to retrieve Bible passages from multiple translations (ESV, NIV, KJV, NASB, NKJV, NLT, AMP, MSG). Supports querying single or multiple passages and provides both MCP protocol integration and REST API endpoints.
      1
      10
      -

    • ptx-mcp

      Nathan22Miles
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides tools to read and compare scripture text from local Paratext project folders, enabling natural-language queries for verses, chapters, books, and cross-project comparisons.
      281 npm
      1
      ISC

    • MCP Chat

      MeeraMendhe
      F
      license
      A
      quality
      D
      maintenance
      A command-line interface application enabling interactive chat with AI models via the Anthropic API. It supports document retrieval, command-based prompts, and extensible tool integrations through the MCP architecture.
      2
      -
    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 8 tools

    Disambiguation4/5

    Most tools target distinct resource types (scripture, notes, questions, words, word links, academy), making them easy to differentiate. However, the fetch tools' filter parameters overlap with the dedicated search tool, creating minor ambiguity about which tool to use for discovery.

    Naming Consistency4/5

    The majority follow a consistent 'fetch_<resource>' pattern (fetch_translation_notes, fetch_scripture, etc.), but 'get_system_prompt' and 'search_biblical_resources' break the pattern, mixing 'get' and 'search' verbs with 'fetch'.

    Tool Count5/5

    With 8 tools, the count is well within the ideal range for a domain-specific proxy. Each tool represents a distinct core capability, and none feel redundant or excessive.

    Completeness5/5

    The set covers all major translation help resources—scripture, notes, questions, words, word links, and academy articles—plus a cross-resource search tool. This provides a comprehensive read-only surface with no obvious gaps for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources