AgentTasker MCP Server
PYPI · AGENT-TASKER-MCP-SERVER · SCANNED SEP 21
Minimal stdio MCP server for parallel task execution by AI agents.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 151 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability53
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 354 tokens (~177/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the AgentTasker MCP Server server?
AgentTasker MCP Server runs locally as a PyPI package, launched with uvx agent-tasker-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · agent-tasker-mcp-server
claude mcp add s3brr-agent-tasker-mcp -- uvx agent-tasker-mcp-server
{
"mcpServers": {
"s3brr-agent-tasker-mcp": {
"command": "uvx",
"args": [
"agent-tasker-mcp-server"
]
}
}
} {
"servers": {
"s3brr-agent-tasker-mcp": {
"command": "uvx",
"args": [
"agent-tasker-mcp-server"
]
}
}
} codex mcp add s3brr-agent-tasker-mcp -- uvx agent-tasker-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"s3brr-agent-tasker-mcp": {
"type": "local",
"command": [
"uvx",
"agent-tasker-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add s3brr-agent-tasker-mcp --command uvx --arg agent-tasker-mcp-server
mcp_servers:
s3brr-agent-tasker-mcp:
command: "uvx"
args: ["agent-tasker-mcp-server"] {
"McpServers": {
"s3brr-agent-tasker-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"agent-tasker-mcp-server"
]
}
}
} assistant mcp add s3brr-agent-tasker-mcp -t stdio -c uvx -a agent-tasker-mcp-server
{
"mcpServers": {
"s3brr-agent-tasker-mcp": {
"command": "uvx",
"args": [
"agent-tasker-mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −2
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −2
- Stability: pass → 0.80 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed pypi/agent-tasker-mcp-server@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
execute ~301
Run one task and return its result.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Request body |
| code | string | – | Python code |
| command | string | – | Command |
| content | string | – | File content |
| extract_headings | boolean | – | Include headings |
| extract_links | boolean | – | Include links |
| fetch_max_chars | integer | – | Chars per fetched page |
| fetch_top_results | integer | – | Fetch top result pages |
| headers | object | – | Headers |
| include_html | boolean | – | Include raw HTML |
| link_include_pattern | string | – | Regex for kept links |
| max_body_bytes | integer | – | Max response bytes |
| max_links | integer | – | Max links |
| max_results | integer | – | Max results |
| max_text_chars | integer | – | Max extracted chars |
| method | string | – | HTTP method |
| mode | string | – | w or a |
| name | string | – | Task name |
| output_mode | string | – | full or compact |
| path | string | – | File path |
| providers | array | – | Discovery providers |
| query | string | – | Search query |
| retries | integer | – | Retry count |
| retry_backoff_seconds | integer | – | Retry backoff seconds |
| task_type | string | yes | Task type |
| timeout | integer | – | Timeout seconds |
| url | string | – | Target URL |
| verify_ssl | boolean | – | Verify SSL |
No output schema declared.
No examples provided.
execute_batch ~38
Run many tasks in parallel and return ordered results.
| Name | Type | Req | Description |
|---|---|---|---|
| output_mode | string | – | full or compact |
| tasks | array | yes | Task definitions |
No output schema declared.
No examples provided.
What is the AgentTasker MCP Server server?
AgentTasker MCP Server is listed in the public MCP registry as io.github.S3bRR/agent-tasker-mcp. Minimal stdio MCP server for parallel task execution by AI agents. This page covers its PyPI package (agent-tasker-mcp-server).
Is the AgentTasker MCP Server server safe to use?
AgentTasker MCP Server scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AgentTasker MCP Server server expose?
AgentTasker MCP Server exposes 2 tools: execute, execute_batch. Their descriptions and schemas cost roughly 339 tokens of context every time the server is loaded.
Is the AgentTasker MCP Server server still maintained?
AgentTasker MCP Server is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the AgentTasker MCP Server server under?
AgentTasker MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.