arsenkin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PUBMED_EMAIL | Yes | Your email address (required by NCBI) | |
| PUBMED_API_KEY | No | Optional API key for higher rate limits |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| arsenkin_profile_catalogA | List job profiles, payload fields and examples. Use first to build a payload; which profile when: arsenkin://guide/tools. Cost: free, no provider call. |
| arsenkin_local_diagnosticsA | Explain local worker heartbeat, your queue and budget. Use when jobs stay queued. Cost: free, no provider call. |
| arsenkin_check_updateA | Check for a newer server release; never installs. Cost: free, 24h cache. |
| arsenkin_result_tableA | Build compact SERP URL/host frequency or cluster tables from a saved result. Use for reports instead of raw results. Cost: free, no new paid calls. |
| arsenkin_statusA | Check Arsenkin account/API availability. Use when jobs fail; for limits use |
| arsenkin_limitsA | Read total and spent Arsenkin limits. Use before prepare/submit to show what is left. Cost: free. |
| arsenkin_projectsA | Read saved Arsenkin Projects data: projects, regions, competitors, keywords, saved positions, charts. Use for tracked-project reports; never starts checks. Cost: free. |
| arsenkin_estimateA | Validate one job payload and estimate its cost. Use before |
| arsenkin_batch_estimateA | Plan, coalesce and price a multi-request batch. Use before |
| arsenkin_request_hash_lookupA | Look up whether an identical request is already in the ledger. Use before resubmitting after an unknown outcome. Cost: free. |
| arsenkin_prepareA | Create a bounded approval for one paid job. Use after the user saw the estimate; then |
| arsenkin_batch_prepareA | Create one bounded approval for a batch. Use after |
| arsenkin_submitA | Queue an approved paid job; returns job_id without waiting. Use only after the user's explicit OK; poll |
| arsenkin_batch_submitA | Queue an approved batch job; the worker coalesces and polls. Use after explicit OK; poll |
| arsenkin_task_statusA | Read durable status of your job. Use to poll after submit; when done use |
| arsenkin_get_resultA | Return the stored result of your job (can be large). Use for small jobs; for compact tables use |
| arsenkin_export_resultA | Export a saved job as bounded JSONL/CSV with provenance. Use for spreadsheets/files. Cost: free, no provider call. |
| arsenkin_cancelA | Request cancellation of your queued/running job. Use when the user aborts; already spent limits may not return. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| semantic_core | Semantics -> clusters -> positions with Arsenkin (paid steps approved one by one). |
| cluster_keywords | Cluster a keyword list by SERP similarity with cost approval. |
| index_check | Check whether URLs are indexed in Yandex/Google (paid, with approval). |
| text_relevance | Analyse SERP-based text requirements (LSI, highlights, meta tags) for a query. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| arsenkin_playbook | |
| arsenkin_toolsets | |
| arsenkin_guide_clustering-params | |
| arsenkin_guide_errors | |
| arsenkin_guide_projects | |
| arsenkin_guide_tools | |
| arsenkin_guide_tool-map |
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.