Skip to main content
Glama

Related Servers

Alternatives to Forge MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to discover new Upwork jobs posted in the last 30 minutes, manage job feeds and filters, and retrieve job details through MCP, with Telegram sign-in and no API key.
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to search and manage Freelancehunt projects, bids, profiles, reviews, messages, and workspaces, with local filtering by keywords, budget, bid count, and employer quality.
      31
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to search and retrieve job postings from Telegram's public job board through standardized MCP tools (search_jobs and get_job), with keyword, location, remote, and date filtering. It works read-only with any MCP host and returns normalized job details such as title, company, apply URL, and posting date.
      MIT
    • 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables tracking a job-search pipeline through MCP tools, a resource, and a prompt, providing stale-application alerts, weekly reviews, and gated follow-up drafting with human approval.
      MIT

    TDQS

    C2.3/5.0

    Scored across 31 tools

    Disambiguation2/5

    Several tool clusters overlap heavily: act_now/hot_leads/chase_leads all surface fresh NEW leads to act on, scan_for_leads/hunt_jobs both scan boards for leads, and pause_weak_boards/board_advice both deprioritize paid=0 boards. Descriptions hint at nuances (age, SLA, push vs track) but an agent could easily misselect within these pairs.

    Naming Consistency3/5

    Casing is consistently snake_case, but the verb/noun pattern is mixed: some tools are verb_noun (capture_lead, record_payment, draft_proposal) while many others are bare noun phrases (pipeline_status, hot_leads, follow_ups, win_journal, rate_advice). Readable but not a predictable convention.

    Tool Count2/5

    31 tools is heavy for a lead-hunting/pipeline server, and the count is inflated by overlapping capabilities (multiple lead-surfacing, board-advice, and outreach tools) rather than distinct operations. Bloat suggests several tools could be merged or parameterized.

    Completeness4/5

    The lifecycle is well covered: capture/scan leads, qualify (red flags, pricing, rate advice), outreach/proposals, pipeline status, payments, board ROI, and win analytics. Only minor gaps (e.g., no explicit lead delete/archive or contact management) that agents can work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues