arsenkin-mcp
Related Servers
Alternatives to arsenkin-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to prepare job-tailoring prompts, export tailored resumes to Google Docs, inspect job details, and retry pending evaluations through JSON-RPC 2.0 tools.-

Dreamwork MCP Serverofficial
AlicenseBqualityBmaintenanceEnables 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.7112MIT- AlicenseNot gradedqualityBmaintenanceProvides access to Adzuna's global job-board aggregation, enabling job search, salary analysis, and regional stats via natural language queries.9 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables 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
- AlicenseNot gradedqualityCmaintenanceIntegrates with Lightcast APIs to search job titles, extract skills from text, and access career data for analysis.5MIT
- AlicenseNot gradedqualityBmaintenanceEnables querying the O*NET occupation taxonomy, including keyword search, occupation details, skills, and associated tools and technology.5 npmMIT
TDQS
Scored across 18 tools
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.
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.
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.
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.