Skip to main content
Glama
rishiiicreates

gibwork-hunter-mcp

by rishiiicreates
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to gibwork-hunter-mcp

No user-submitted related servers found.

    Related Servers

    • gibwork-sentinel-mcp

      195440
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes pre-flight analytics and guardrail tools over stdio that let AI agents and maintainers rank open Gibwork bounties by risk-adjusted expected value and on-chain Solana vault solvency, audit escrow state and queue saturation, and validate deliverables against submission gates. It also coordinates concurrent workers with atomic claim locks and generates idempotent, CLI-ready submission payloads to avoid wasted fees and duplicate submissions.
      1
      MIT

    • Escrow Sentinel

      summerlx0416-droid
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to discover Gibwork bounties, verify their Solana escrow accounts on-chain, rank opportunities by value, competition and deadline, diff captures over time, and export Markdown/CSV/JSON reports through four read-only MCP tools requiring no wallet or API key.
      MIT

    • gibwork-bounty-hunter

      KvngJamesII
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables developers and AI agents to discover, rank, watch, and draft submissions for Gibwork coding bounties through MCP tools, with optional wallet-authenticated SDK support.
      1
      MIT

    • Gibwork Task Compiler

      jbnikky13
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible AI clients and coding agents to turn vague GitHub requests into structured, testable task contracts, inspect repository evidence, simulate execution, validate readiness, and preview or publish Gibwork bounties only after explicit confirmation.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool maps to a distinct stage of a bounty workflow: browse (list_bounties), inspect (get_bounty), evaluate local work (verify_deliverable), and sign/register (submit_proof). There is no plausible confusion between listing many bounties versus fetching one, or between local verification and on-chain submission.

    Naming Consistency5/5

    All four names use a uniform `gibwork_` namespace prefix followed by a verb_noun pattern in snake_case (list_bounties, get_bounty, verify_deliverable, submit_proof). The convention is fully predictable and readable.

    Tool Count4/5

    Four tools is on the lean side but each earns its place within a narrow bounty-hunting scope, and there is no filler. It sits just below the ideal mid-range, leaving little room for auxiliary operations.

    Completeness4/5

    The core discovery-to-submission lifecycle is fully covered, including a verification step most servers would omit. Minor gaps remain: no way to check submission status or withdraw/resubmit a proof, and no agent-side profile or submission history lookup.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources