mcp server
TaScan
Universal task protocol — manage projects, tasks, workers, QR codes, and reports.
Description as published by the maintainer. Source
- version 1.0.2
- slowing
slowing — Registry entry last updated 2026-03-03.
What this server can do
32 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
tascan_add_tasks(tasks, list_id)- Add one or more tasks to an event (task list). Supports bulk creation. IMPORTANT: Set response_type correctly — use "text" for info collection (names, phones, emails, notes), "photo" for visual verification (inspections, serial numbers, damage checks), "checkbox" only for simple confirmations. NOTE: To dispatch tasks to the Claude Code agent running on Mike's PC, use tascan_dispatch_to_agent instead — it routes directly to the agent's inbox with zero configuration needed. Required: list_id, tasks.
tascan_analyze_issue(issue_id, server_side_ai)- Step 1 of the Closed-Loop Autonomous Operations Protocol. Retrieves full issue context including worker info, message thread, project history, and recent similar issues. Use this data to reason about the root cause and generate a remediation plan. Also supports server-side AI analysis via POST (calls Anthropic API directly). Required: issue_id.
tascan_apply_template(list_id, template_slug)- Apply a pre-built template to a task list, adding all template tasks Required: list_id, template_slug.
tascan_auto_resolve(issue_id)- FULL Closed-Loop Autonomous Operations Protocol in one call. Server-side AI analyzes the issue, generates remediation tasks, creates a task list, and dispatches to the worker — all without human intervention. This executes Patent Claim 7: autonomous operations from issue detection through physical-world instruction delivery. Required: issue_id.
tascan_complete_task(notes, task_id, worker_id, response_value)- Complete a task on behalf of a worker. Inserts a completion record and timer event. Use this to simulate or record task completions via the API. Required: task_id, worker_id.
tascan_create_event(name, team_mode, project_id, description, multi_instance)- Create a new event (task list) within a project. Supports team_mode (shared completions) and multi_instance (each worker gets isolated copy — great for surveys, onboarding, info collection). team_mode and multi_instance cannot both be true. Required: project_id, name.
tascan_create_project(name, location)- Create a new TaScan project (top-level container for events) Required: name.
tascan_create_worker(name, email, phone)- Create a new worker (taskee) in the organization Required: name.
tascan_delete_event(list_id)- Delete an event (task list) and all its tasks and completions. This action is irreversible. Required: list_id.
tascan_delete_project(project_id)- Delete a project and all its events, tasks, and completions. This action is irreversible. Required: project_id.
tascan_delete_task(task_id)- Delete a specific task and its completions. This action is irreversible. Required: task_id.
tascan_dispatch_instruction(ai_agent, issue_id, send_sms, worker_id, instruction, remediation_tasks, recommendation_summary)- Step 3 of the Closed-Loop Autonomous Operations Protocol. Dispatches remediation to the worker via MULTI-CHANNEL delivery: (1) issue thread message, (2) in-app notification, (3) progress feed update, (4) SMS if phone on file, (5) optional remediation task list creation. Closes the loop from digital AI analysis to physical worker execution. Required: issue_id, instruction.
tascan_dispatch_to_agent(task, agent, priority)- PREFERRED tool for sending work to an AI agent. Dispatches a task to the agent's inbox — picked up and executed automatically. No list ID needed. Supports prefixes: CODE: SHELL: RESEARCH: WRITE: PLAN: for routing. Use "agent" param to target a specific agent (default: claude-code-local). Use tascan_list_agents to discover available agents. Required: task.
tascan_generate_qr(list_id)- Generate a QR code for a task list (event) that workers can scan to access tasks Required: list_id.
tascan_get_event(list_id)- Get details of a specific event (task list) including its tasks Required: list_id.
tascan_get_project(project_id)- Get details of a specific project Required: project_id.
tascan_get_report(list_id)- Get completion report for a task list (event) including task status, completions, workers, and photos Required: list_id.
tascan_get_task(task_id)- Get details of a specific task including completions Required: task_id.
tascan_list_agents- List all registered AI agents with their capabilities, inbox IDs, and status. Like reading input labels on a video matrix — discover which agents are available and what they can do before dispatching work.
tascan_list_events(project_id)- List all events (task lists) within a project Required: project_id.
tascan_list_issues(list_id)- List all issues for a task list (event). Returns open, acknowledged, and resolved issues with severity, type, and category. Use this to discover issues that need AI analysis via tascan_analyze_issue. Required: list_id.
tascan_list_projects- List all TaScan projects in the organization
tascan_list_tasks(list_id)- List all tasks in an event (task list) Required: list_id.
tascan_list_templates(category)- List available task templates (built-in and saved)
tascan_list_workers- List all workers (taskees) in the organization
tascan_recommend_fix(ai_agent, issue_id, recommendation, structured_recommendation)- Step 2 of the Closed-Loop Autonomous Operations Protocol. Post an AI-generated recommendation to an issue thread. Accepts both a text recommendation and an optional structured_recommendation object with task definitions for auto-dispatch. The recommendation is persisted in the AI audit trail. Required: issue_id, recommendation.
tascan_register_agent(id, name, type, model, inbox_id, location, worker_id, description, capabilities)- Register a new AI agent in the agent registry. The agent will appear in tascan_list_agents and can receive dispatched tasks. Self-registration for AI agents joining the TaScan network. Required: id, name, type, inbox_id, capabilities.
tascan_send_task_email(list_id, message, subject, task_id, to_name, to_email, include_qr)- Send a branded TaScan task notification email via SendGrid. Can notify anyone about a specific task list or task. Includes QR code, task summary, and "Open in TaScan" button. Required: to_email, list_id.
tascan_update_event(name, list_id, team_mode, timer_mode, description, multi_instance)- Update an event / task list (name, description, team_mode, multi_instance, timer_mode). team_mode and multi_instance cannot both be true. Required: list_id.
tascan_update_project(name, status, end_date, location, project_id, start_date)- Update a project (name, location, status, dates) Required: project_id.
tascan_update_task(title, task_id, sort_order, description, response_type, requires_photo, is_safety_checkpoint)- Update a task (title, description, response_type, flags, sort_order) Required: task_id.
tascan_update_worker(name, email, phone, worker_id)- Update a worker profile (name, phone, email) Required: worker_id.
Last successful function declaration observed on . Source: https://tascan-live-event.netlify.app/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://tascan-live-event.netlify.app/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.2 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-03-03 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-03-03 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 32 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | tascan-live-event.netlify.app | |
| mcp endpoint status | ok | The server listed 32 functions when asked. | as of probe | tascan-live-event.netlify.app |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json