Productivity · Remote MCP server
TaScan
36 MCP tools for projects, tasks, workers, QR/NFC tags, and AI remediation. Task. Scan. Done.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.snowbikemike/tascan-mcp- Version
- 3.0.0
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-08-18
- Updated
- 2026-08-18
- Publisher
- snowbikemike (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/snowbikemike) · how
- Website
- tascan.io
- Repository
- github.com/snowbikemike/tascan-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://app.tascan.io/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- tascan 3.19.0 · protocol 2025-06-18
- Tools discovered
105 - show names
tascan_list_projects,tascan_create_project,tascan_get_project,tascan_update_project,tascan_delete_project,tascan_create_event,tascan_list_events,tascan_get_event,tascan_update_event,tascan_delete_event,tascan_add_tasks,tascan_dispatch_to_agent,tascan_list_agents,tascan_register_agent,tascan_list_tasks,tascan_get_task,tascan_get_receipt,tascan_update_task,tascan_reply_with_list,tascan_add_subtasks,tascan_list_subtasks,tascan_update_subtask,tascan_complete_subtask,tascan_delete_subtask,tascan_delete_task,tascan_complete_task,tascan_list_workers,tascan_create_worker,tascan_update_worker,tascan_generate_qr,tascan_apply_template,tascan_list_templates,tascan_get_report,tascan_query_responses,tascan_list_issues,tascan_analyze_issue,tascan_recommend_fix,tascan_dispatch_instruction,tascan_auto_resolve,tascan_send_sms,tascan_schedule_sms,tascan_list_scheduled_sms,tascan_cancel_scheduled_sms,tascan_get_sms_status,tascan_send_task_email,tascan_register_tag,tascan_list_tags,tascan_get_scan_history,tascan_search_marketplace,tascan_invite_workerand 55 more- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | tascan-mcp | 3.0.0 | stdio |
How to connect TaScan
TaScan is a remote MCP server: there is nothing to install. Its endpoint is https://app.tascan.io/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: tascan-mcp version 3.0.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y tascan-mcp@3.0.0. It reads these environment variables: TASCAN_API_KEY (required, secret) and TASCAN_API_URL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"tascan-mcp": {
"command": "npx",
"args": [
"-y",
"tascan-mcp@3.0.0"
],
"env": {
"TASCAN_API_KEY": "<secret>",
"TASCAN_API_URL": "<value>"
}
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| TangoShared task queue for humans and AI agents: leases, handoffs, approvals and signed receipts. | Remote · HTTPLive check: sign-in required |
| Tanjiren MCP ServerHosted MCP server for task-first delegation to remote workstations and workers. | Remote · HTTPLive check: ✗ no handshake |
| TapBrowser MCP for logged-in tasks. Uses your Chrome - credentials stay local. Zero-token replay. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| TaprootPersistent memory layer for AI tools. Save and recall notes across Claude and other MCP clients. | Remote · HTTPLive check: sign-in required |
| TasgWork management where AI agents are first-class members: tasks, projects, memory over hosted MCP. | Remote · HTTPLive check: sign-in required |
| Task Board Todo KanbanA todo and task board in kanban form, driven from chat with full CRUD. | Remote · HTTPLive check: ✓ handshake |
| Task CheckpointMCP server that checkpoints long agent tasks: roll back to any step, resume in a new session. | Local · stdio |
| Task Graph MCPMCP server for agent task workflows with phases, prompts, gates, and multi-agent coordination. | Local · stdio |