Skip to main content
Glama
iliyalazarevwork-art

freelancehunt-mcp

by iliyalazarevwork-art
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to freelancehunt-mcp

No user-submitted related servers found.

    Related Servers

    • flru-mcp

      creator137
      F
      license
      C
      quality
      B
      maintenance
      Local MCP server for the FL.ru freelance marketplace that enables browsing projects, scoring relevance, saving proposal drafts, and dry-run proposal submission via natural language.
      17
      -

    • freehire

      strelov1
      A
      license
      A
      quality
      B
      maintenance
      Enables searching, filtering, and applying to IT jobs via MCP tools using a personal API key, mirroring the freehire CLI.
      19
      41 npm
      2
      MIT

    • Job Board MCP Server

      Danialesss
      F
      license
      A
      quality
      B
      maintenance
      Enables searching and retrieving job listings from multiple platforms through MCP.
      2
      -

    • jobfinder-mcp

      juanzjck
      F
      license
      A
      quality
      C
      maintenance
      Enables searching job listings, tracking applications, managing resumes, and tailoring resumes to job posts, all locally via MCP.
      20
      -

    • Upwork MCP Server

      rozetyp
      A
      license
      A
      quality
      C
      maintenance
      Enables searching Upwork jobs with real search filters like competition, verified payment, and budget/rate floors, and reading your profile, connects, proposals, and messages through a Chrome session. Also offers untested tools for managing proposals, messages, and contracts.
      18
      Apache 2.0
    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

    B3.4/5.0

    Scored across 31 tools

    Disambiguation4/5

    Most tools map cleanly to a distinct resource and action, and the generic *_action tools are separated by their target resource. There is minor overlap between workspace_action and complete_contest_workspace, and a few stubbed 404 tools add noise, but the descriptions generally resolve ambiguity.

    Naming Consistency4/5

    The set is predominantly snake_case verb_noun: list_*, get_*, create_project, update_project, add_bid, send_message. The *_action batch tools are a recognizable pattern, though they are noun_noun rather than verb_noun, and complete_contest_workspace / mark_feed_read deviate slightly.

    Tool Count2/5

    With 31 tools the surface is too large for the rubric's 25+ threshold. Several tools are documented but return 404 for normal tokens, so they inflate the count without adding usable capability.

    Completeness4/5

    Core lifecycles are well covered: projects support list/find/get/create/update/actions, bids support add/list/action, workspaces have list/get/action, and threads have list/get/send/action. Missing contest creation, working profile search, and the 404 stubs keep it from a perfect score.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources