agentsoukofficial
A
licenseNot graded
qualityC
maintenanceEnables AI agents to create identities, list and find services, handle payments in USDC, and manage reputation through a decentralized marketplace.
2 npm
1
MIT
nadbounty-mcp
by Sofiia7
Related Servers
Alternatives to nadbounty-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceAI agents hire people for work they can't finish alone (data curation, red-teaming, scraping, transcription), paid via non-custodial USDC escrow on Base. Returns unsigned transactions and holds no keys.1Apache 2.0
- AlicenseAqualityBmaintenanceEnables reading live market state on Arc (chainId 5042) including launchpads, LP APRs, RPC consensus, token screens, honeypot simulations, and an agent directory.1213 npmMIT
- AlicenseAqualityDmaintenanceEnables AI agents to find and query real-time GitHub coding bounties with built-in scam filtering, supporting listing, matching, and detailed bounty retrieval.462 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables agents to propose and manage Gibwork bounties for human help, wait for and review submissions, and request owner-approved escrow funding, payouts, refunds, and audit verification through a signing vault.MIT
- AlicenseAqualityCmaintenanceLets agents query anchored ground-level capture data, verify provenance, and commission new captures, paying per request in USDC on Base or Arc via x402.7MIT
TDQS
A3.8/5.0
Scored across 13 tools
Disambiguation4/5
Most tools target clearly distinct resources/actions (bounties, contests, identities, keys, balances, network). The main overlap is get_identity_reputation vs get_agent_reputation, both reputation lookups, but the descriptions distinguish gate totals from the full picture, and get_bounty vs list_open_bounties vs get_my_bounties are differentiated by scope. Only minor confusion is likely.
Naming Consistency4/5
The set mostly follows a verb_noun snake_case pattern (list_open_bounties, get_bounty, get_contest, generate_contest_keypair, encrypt_contest_entry, decrypt_contest_entry). The deviations are the noun-only names 'network' and 'balances', which are minor and still readable. Overall consistent with one or two stylistic exceptions.
Tool Count4/5
13 tools is a reasonable, well-scoped number for a bounty/contest domain and none feel redundant. The count leans slightly low relative to the breadth implied (writes, submissions, contest lifecycle), suggesting some operations are absent rather than excessive.
Completeness2/5
The surface is largely read + crypto (list/get/balances/identity/reputation/encrypt/decrypt) but the descriptions repeatedly reference mutation tools that are not present (post_bounty, enter_contest, approve_bounty, submit delivery, pin_text, respond/claim). Missing create/take/submit/approve lifecycle operations will cause agent dead ends despite get_pending_actions pointing at tools to call.
Maintenance
ActivityActive
ResponsivenessLimited data