Skip to main content
Glama
Blackshield-Company

bounty-mcp

by Blackshield-Company
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to bounty-mcp

No user-submitted related servers found.

    Related Servers

    • bounty-mcp

      weiseer
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to find and query real-time GitHub coding bounties with built-in scam filtering, supporting listing, matching, and detailed bounty retrieval.
      4
      17 npm
      Apache 2.0

    • taskbounty-mcp-server

      eliottreich
      A
      license
      B
      quality
      A
      maintenance
      Marketplace where AI coding agents fix GitHub bugs for cash bounties. Posters draft and fund bounties from chat (Stripe Checkout); solvers browse open work, request repo access, submit PRs, and get paid in USDC, ETH, or BTC. 11 tools.
      27
      899 npm
      1
      MIT

    • opengit-mcp

      opengitteam
      A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to search an index of open source repos and tools by what they do, their callable interface (MCP, CLI, SDK, API, etc.) and OG score, plus fetch repo details, category listings, and weekly trending projects.
      4
      0
      1
      MIT

    • Market.dev MCP Server

      market-dot-dev
      A
      license
      Not graded
      quality
      F
      maintenance
      Integrates with the Market.dev API to search for open source experts and projects. It enables users to find contributors and developers based on skills, location, or specific library and framework involvement.
      3
      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

    A3.8/5.0

    Scored across 3 tools

    Disambiguation3/5

    The two source-specific tools (search_github_bounties, search_opire_rewards) are clearly distinct, but search_bounties is an aggregator that overlaps functionally with both. Descriptions do explain the difference (combined dedupe vs. per-source), which saves it from being truly confusing, but an agent must read carefully to decide whether to call the aggregate or the individual sources.

    Naming Consistency4/5

    All three names are snake_case with the same verb 'search_', forming a predictable pattern. The minor deviation is that search_bounties lacks a source qualifier even though it is a superset of the other two, which makes it slightly ambiguous against search_github_bounties.

    Tool Count4/5

    Three tools for a narrowly scoped bounty-discovery server is reasonable and each has a defensible role. The only inefficiency is that the aggregate tool largely subsumes the two source-specific ones, so the effective surface is closer to one-and-a-half tools.

    Completeness3/5

    The server covers discovery/search only: no detail lookup for a specific bounty, no filtering parameters exposed (keyword/amount filtering is done internally for Opire), and no pagination or repo-scoped search. Agents can work around this by using the returned URLs, but the surface stops at listing.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources