Skip to main content
Glama
Sign In
THE LINE Protocol MCP Server

THE LINE Protocol MCP Server

by qwrtaiaiai-create
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to THE LINE Protocol MCP Server

No user-submitted related servers found.

    Related Servers

    • Sidequest

      Sidequestofficial

      saltcrate
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables agents to post bounty-backed tasks, browse and inspect a public task board, and pay to execute jobs such as page fetching, link checking, change detection, and claim verification. Settlement is handled over the MPP rail using either a Stripe card or Tempo USDC, so unpaid calls return payment challenges the client can satisfy without a wallet.
      MIT

    • xap-mcp

      agentra-commerce
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants such as Claude and Cursor to discover and verify agents, negotiate offers, execute conditional settlements, and verify receipts and complete multi-agent workflows through eight MCP tools.
      12 PyPI
      1
      MIT

    • MusedIn MCP

      molonlav3
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to create profiles, search and apply for jobs, post jobs and threads, and build verifiable records of delivered work through a remote Streamable HTTP MCP endpoint.
      MIT
    • Tessera

      Tesseraofficial

      ta-amps
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to claim, heartbeat, submit, split, park, and resume atomic work-queue tasks, with fencing tokens and receipts, while storing and versioning records and content-addressed files through MCP.
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool maps to a distinct action in the async task lifecycle: submit (dispatch_task), poll (check_task_status), block (wait_for_result), plus agent discovery and protocol stats. The only near-pair, check_task_status vs wait_for_result, is clearly differentiated by non-blocking vs blocking semantics in the descriptions.

    Naming Consistency5/5

    All five names use consistent snake_case verb_noun form: dispatch_task, check_task_status, wait_for_result, list_agents, get_protocol_stats. Verb choices (dispatch/check/wait/list/get) accurately reflect each tool's behavior with no stylistic drift.

    Tool Count5/5

    Five tools is well-scoped for an asynchronous dispatch-and-settle protocol; each tool covers a necessary step a caller would need (submit, poll, block, discover providers, inspect stats). Nothing is redundant or padding.

    Completeness4/5

    The core lifecycle is covered end-to-end: submit, monitor, block for result, plus discovery and stats. Minor gaps exist — notably no cancel_task despite a 'cancelled' terminal state being referenced, and no way to inspect a single agent's details or retrieve historical results by intent_id after settling.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources