Skip to main content
Glama
usebrainchain

brainchain-mcp

Official
by usebrainchain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to brainchain-mcp

No user-submitted related servers found.

    Related Servers

    • nexus

      bobuilds
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to post tasks with JSON-schema validation and run workers, facilitating agent-to-agent collaboration on the NexusToken network.
      71 PyPI
      1
      MIT

    • 4bl1ty MCP Server

      Brissux-Labs
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to hire verified humans for physical-world tasks by posting missions with budgets, managing claims and proof, and releasing escrow payments upon validation.
      1
      MIT

    • humanrail-mcp-server

      prime001
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to route tasks requiring human judgment (e.g., content moderation, refund decisions, data verification) to a vetted worker pool, with verified results returned via Lightning Network payments.
      MIT
    • work2own-mcp by work2own

      work2own-mcpofficial

      work2own
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to discover and complete quests and gigs, submit proof, and receive rewards in stock tokens or USDG. It also lets agents create and fund work, hire applicants, review submissions, and pay.
      23
      MIT

    • --

      eamwhite1
      A
      license
      Not graded
      quality
      A
      maintenance
      --
      1
      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.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools form a clean write/read pair: brainchain_post_task creates an order and brainchain_get_task reads it. Descriptions explicitly cross-reference each other and even tell the agent not to re-post when a reply says possiblyCharged, eliminating the main confusion risk.

    Naming Consistency5/5

    Both names follow the same brainchain_<verb>_<noun> pattern with a shared server prefix and snake_case throughout. No deviation or ambiguity in the convention.

    Tool Count3/5

    Two tools is thin, but here they are a minimal viable pairing for an asynchronous paid-task service (submit then poll), so it is defensible rather than arbitrary. Still, the surface feels sparse for a service that involves payments, refunds, and grading.

    Completeness3/5

    The core submit-and-retrieve lifecycle is covered, including refund and failure states in the status semantics. However, there is no way to list orders, cancel a task, check wallet balance or refund status independently, which leaves agents without recovery paths if an order id is lost.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources