Skip to main content
Glama
zai-one

arsenkin-mcp

by zai-one

Related Servers

Alternatives to arsenkin-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables AI clients to browse public job listings, save and rank roles into a pipeline, tailor resumes and cover letters, submit applications, and track replies, interviews, and escalations over time. Works anonymously for job browsing or with a scoped API key for full account, apply, and recruiter-outreach capabilities.
      71
      12
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides access to Adzuna's global job-board aggregation, enabling job search, salary analysis, and regional stats via natural language queries.
      9 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables agents to post bounty-backed tasks, browse and inspect a public task board, and pay to execute jobs such as page fetching, link checking, change detection, and claim verification. Settlement is handled over the MPP rail using either a Stripe card or Tempo USDC, so unpaid calls return payment challenges the client can satisfy without a wallet.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying the O*NET occupation taxonomy, including keyword search, occupation details, skills, and associated tools and technology.
      5 npm
      MIT

    TDQS

    A3.9/5.0

    Scored across 18 tools

    Disambiguation4/5

    The single vs batch variants (estimate/batch_estimate, prepare/batch_prepare, submit/batch_submit) are clearly paired and differentiated by scope, and descriptions explicitly state 'which when' and ordering. arsenkin_status vs arsenkin_task_status and get_result vs result_table vs export_result could momentarily overlap, but descriptions clearly separate account health, job polling, raw results, compact tables, and file export.

    Naming Consistency4/5

    All names use the arsenkin_ prefix and snake_case throughout, with consistent verb_noun forms (get_result, batch_estimate, check_update, request_hash_lookup). There is minor variance between bare nouns (projects, limits, status) and verb-led names, but the pattern is predictable and readable.

    Tool Count4/5

    18 tools is slightly heavy but justified by the full paid-job lifecycle (discover, estimate, approve, submit, poll, fetch, export, cancel) with mirrored single/batch pairs. Each tool has a distinct stage or purpose, so few feel redundant.

    Completeness4/5

    The surface covers the lifecycle end-to-end: catalog, estimate, approval, submit, poll, result retrieval/table/export, limits, diagnostics, ledger lookup, and cancellation. Minor gaps like listing all prior jobs or re-running a saved job are largely workable via task_status and projects.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues