# Snowbikemike Tascan MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.snowbikemike%2Ftascan-mcp
Registry id: `mcp-registry/io.github.snowbikemike/tascan-mcp`
Status: live (checked 2026-10-27T02:31:52.280Z)

## Measurements (30 days)

- Uptime: 99.98%
- Checks: 5026
- Outages (90 days): 10

## Install

```json
{
  "mcpServers": {
    "snowbikemike-tascan-mcp-server": {
      "type": "http",
      "url": "https://app.tascan.io/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http snowbikemike-tascan-mcp-server https://app.tascan.io/mcp
```

## Tools (142)

- `tascan_add_subtasks`: Add one or more subtasks to a task (bulk). Subtasks support typed responses: "number" for per-set data (reps, weight, distance), "text" for notes, "choice" for 
- `tascan_add_tasks`: 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, e
- `tascan_analyze_issue`: Step 1 of the Closed-Loop Autonomous Operations Protocol. Retrieves full issue context including worker info, message thread, project history, and recent simila
- `tascan_append_chat_messages`: Append 1 or 2 text turns (each a role, user or assistant, and its content) to a chat thread of an admin of your org (POST /chat/threads/:id/messages), the way t
- `tascan_apply_qr_style`: Apply a saved QR look (qr_style_id, or null to clear) to a project, list, task or site (target + id: PUT on that item), or make it the default for a purpose (ta
- `tascan_apply_template`: Apply a pre-built template to a task list, adding all template tasks
- `tascan_assess_condition`: Run an AI condition assessment of an asset from a photo. The model scores 0-100 with the asset's full assessment history in context, so it reads degradation ove
- `tascan_auto_resolve`: FULL Closed-Loop Autonomous Operations Protocol in one call. Server-side AI analyzes the issue, generates remediation tasks, creates a task list, and dispatches
- `tascan_cancel_scheduled_sms`: Cancel a scheduled text that has not been sent yet (status pending). A row already sending, sent, failed or cancelled is refused (409) — a sent text cannot be r
- `tascan_claim_run`: Claim a fan-out seat task as a LOCAL subagent run (POST /runs/claim -> claim_agent_run(p_runner='local')). Only admitted when instance starts with "<your regist
- `tascan_clone_project`: Duplicate a project's STRUCTURE (POST /projects/:id/clone): its task lists (not a work order's own lists), their tasks (never coordination cards) with response 
- `tascan_complete_subtask`: Complete a subtask, optionally recording a typed response_value (e.g. the weight or reps for that set). Each completion is timestamped, so consecutive set compl
- `tascan_complete_task`: Complete an ORDINARY task on behalf of a worker. Inserts a completion record and timer event. Coordination-cycle tasks (a CODE:/REVIEW: build or review, a Decis
- `tascan_condition_history`: Get an asset's longitudinal condition history — score trend over time, every assessment with grade, delta, findings, and who assessed it. The per-serial-number 
- `tascan_control_fanout`: Control a running fan-out (POST /coord/fanouts/:id/control). pause holds every unclaimed seat and stops re-firing; resume releases them; cancel supersedes every
- `tascan_create_cycle`: Start an unattended build-review-decide cycle (protocol v0.2). Queues T1 CODE: (or SHELL:) with your build_brief on the AI Inbox and T2 REVIEW: with your review
- `tascan_create_event`: 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,
- `tascan_create_fanout`: Create a fan-out: 1-30 seats (RESEARCH by default, or LOCAL subagent seats) plus one synthesizer under ONE cycle root (POST /coord/fanouts). No Decision cards, 
- `tascan_create_invoice`: Create a client invoice and get its shareable link. Two ways to bill: (a) pass explicit line_items, or (b) pass project_id or task_list_ids plus hourly_rate (qu
- `tascan_create_project`: Create a new TaScan project (top-level container for events). number is optional (the next P-number is assigned when omitted; a number already used in the org i
- `tascan_create_site`: Create a site (a job location) in the organization: name (1-200 characters) and optionally address, lat + lng (together), client_company and external_key (uniqu
- `tascan_create_worker`: Create a new worker (taskee) in the organization
- `tascan_create_zone`: Create a geofenced work zone. Delivery zones route workers who open the project Site Gate (geo.html?project=...) to this zone's task list when GPS places them i
- `tascan_delegate_to_agent`: Mint a time-limited, NARROWER child API key (POST /delegations, roadmap #11) — only read/write scopes may be requested; full, agent:dispatch, agent:dispatch:cod
- `tascan_delete_chat_thread`: Delete a chat thread and its messages (DELETE /chat/threads/:id), the way the Simple page does; a receipted ledger event is written first. Write tier.
- `tascan_delete_event`: Delete an event (task list) and all its tasks and completions. This action is irreversible.
- `tascan_delete_project`: Delete a project that has NO history, after typing its name. Refused 409 project_has_history (with the counts) when it has any task or subtask completion, actio
- `tascan_delete_subtask`: Delete a subtask and its completions. This action is irreversible.
- `tascan_delete_task`: Delete a specific task and its completions. This action is irreversible.
- `tascan_delete_worker`: Tombstone a worker record (is_active=false). REFUSES if the worker has any task/subtask completions or payments — merge those into the real worker with tascan_m
- `tascan_dispatch_instruction`: 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 
- `tascan_dispatch_to_agent`: 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. REQUIRES the a
- `tascan_dispatcher_action`: Record a chief-of-staff dispatcher action on a coordination cycle as a receipt (protocol v0.2 D6, POST /coord/cycles/:root/dispatcher-actions): hand_review_appr
- `tascan_evidence_policy`: Read or author a task's evidence policy (protocol v0.2 V9b, GET|PUT /evidence/policy/:task_id — one route, two methods, so one tool). action=get evaluates the p
- `tascan_find`: Cross-entity search: find projects (by name, project number or customer job number in external_refs; each with its status), task lists, tasks, workers, conditio
- `tascan_find_duplicate_workers`: Find candidate same-person worker records with per-signal match detail (Patent 4 §6.25(b) signals: phone reuse, name similarity, GPS pattern correlation). Turns
- `tascan_finish_run`: Finish a claimed local run (POST /runs/:run_id/finish). outcome='completed' stores `document` (and optional `verification`) as the seat's own build artifacts un
- `tascan_generate_qr`: Generate a QR code for a task list (event) that workers can scan to access tasks. TaScan draws the QR itself (an SVG, also returned as a data: URI in qr_image_u
- `tascan_generate_report`: Mint a shareable report and get its link. Types: completion (full proof-of-work for one list: tasks, responses, subtasks, photos, GPS + place names, timing, QR 
- `tascan_get_access`: Read the access object of a task list (list_id) or a task (task_id): access_level (open, assigned or secured; a task-level value wins over its list), the effect
- `tascan_get_budget`: Read THIS credential's own per-key action budget (GET /budget): daily limits (sms, invites, payment-request cents per day and per request, dispatch, human pages
- `tascan_get_build`: Manifest of a stored build bundle by build_ref (protocol v0.2 build_artifacts): the exact files the executor produced for the cycle's artifact_paths, each with 
- `tascan_get_build_diff`: Store an already-computed diff for one file of a build bundle against a base commit (protocol v0.2 item 6, POST /coord/builds/:build_ref/diff — the parser has n
- `tascan_get_build_file`: Read one file from a stored build bundle by build_ref and path (protocol v0.2 build_artifacts) — the exact bytes the executor produced, not a working-tree read.
- `tascan_get_cycle_report`: The audit report of one coordination cycle by its root task id (protocol v0.2, get_cycle_report): every step task (build, review, checkpoint, integrate, questio
- `tascan_get_device`: Get one device by id: kind, name, status, location zone, credential rotation timestamps, revocation reason, and the last 20 evidence_events ids it produced. Nev
- `tascan_get_event`: Get details of a specific event (task list) including its tasks
- `tascan_get_fanout`: Read a fan-out (GET /coord/fanouts/:id?view=). view=status (default): state, seat counts, spend, cap, synth_deadline_at, poll_after_s. view=report: the full cyc
- `tascan_get_org`: Read the organization profile (GET /org): id, name, industry, logo, time zone and the admin phone MASKED to its last 4 digits (a tool never sees the full number
- `tascan_get_org_plan`: Your organization's plan (GET /org/plan), read-only: plan (free, pro, ...) and whether billing is exempt. Billing changes happen in the TaScan portal only. Read
- `tascan_get_project`: Get details of a specific project
- `tascan_get_receipt`: Fetch the signed Action Receipt (Ed25519 JWS) for one completed task by completion_id (tascan_get_task -> completions[].id). Returns a readable summary (what, w
- `tascan_get_report`: Get completion report for a task list (event) including task status, completions, workers, and photos. Set include_responses to also return the actual submitted
- `tascan_get_scan_history`: Scan accountability data. Two modes: (1) tag_id — scans of a registered NFC tag; (2) task_list_id or project_id — every QR/link page-open stamp: when the code w
- `tascan_get_signature_bundle`: Fetch the signature bundle for one signed document by signature assertion id (the signature_assertion_id inside the response value of a completed signature task
- `tascan_get_site`: Read one site with the projects and task lists linked to it. Read tier.
- `tascan_get_sms_status`: Check delivery status of a previously sent TaScan SMS by its Twilio SID (returned by tascan_send_sms). Shows queued/sent/delivered/undelivered/failed plus carri
- `tascan_get_task`: Get details of a specific task including completions and subtasks. Each completion carries photo_url (raw storage path, stable) and photo_signed_url (short-live
- `tascan_get_task_trail`: Read a task's trail messages (protocol v0.2 trail_messages, GET /tasks/:id/messages): question, answer, handoff and note/discussion entries, last 100, newest la
- `tascan_get_timesheet`: A task list's timesheet (GET /lists/:id/timesheet), read-only: each shift (who, clock in, clock out, breaks, hours; an open shift and a never-clocked-out one ar
- `tascan_get_usage`: Read your organization's usage and quota snapshot for a billing period (GET /usage): SMS, email and AI call counts against their plan limits, the 100-receipt-pe
- `tascan_get_worker`: Ungated, plain read of one worker row: name, contact, org, points, streaks, timestamps. (tascan_get_worker_passport is the rich stats view; this is the boring l
- `tascan_get_worker_passport`: Get a worker's verified work passport — task counts, lists worked, photos submitted, GPS-verified hours, points, streaks, and earned merit badges, all computed 
- `tascan_heartbeat_run`: Extend a claimed local run's lease and mark it running (POST /runs/:run_id/heartbeat -> heartbeat_agent_run). ok false with reason not_live means the run is no 
- `tascan_invite_worker`: Invite a marketplace worker to a task list — the consented intro. TaScan texts the worker from its own number ("<Your org> wants you for <list>. Reply YES to sh
- `tascan_issues_inbox`: The org-wide issues inbox (GET /issues): every task issue across projects, newest first, filtered by status (OPEN, ACKNOWLEDGED, IN_PROGRESS, RESOLVED, CLOSED, 
- `tascan_link_site`: Link a site to a project (project_id) or to a task list shown at the site (list_id) — exactly one. Both must be in your organization. Linking twice is a no-op. 
- `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 
- `tascan_list_assets`: List registered condition-ledger assets with their latest condition scores. Use to recover an asset_id for tascan_assess_condition or tascan_condition_history.
- `tascan_list_chat_threads`: List the Ask TaScan chat threads of your org's admins (GET /chat/threads, newest first; admin_id narrows to one admin), or read one thread with its messages (th
- `tascan_list_connectors`: List the organization's connectors (GET /integrations), e.g. the Salesforce Work Order bridge: provider, instance URL, the project and list new work lands on (w
- `tascan_list_cycles`: List coordination-cycle roots in the organization (protocol v0.2, GET /coord/cycles): root id, title, status, task_type, project, build_ref, deploy_id and the T
- `tascan_list_delegations`: List delegated child keys (GET /delegations): this key's own direct children (id, label, scopes, active/revoked, depth, expires_at) — never the raw credential. 
- `tascan_list_devices`: List registered devices (RFID portals, barcode guns, PLCs, cameras, robots, tools, sensors) in the organization. Filter by status (active/revoked) or kind; pagi
- `tascan_list_events`: List all events (task lists) within a project
- `tascan_list_insights`: List AI Insights (GET /insights): the audit engine's suggestions for your org (ai_suggestions), pending by default; status applied, dismissed, explained, expire
- `tascan_list_invites`: List marketplace invites you have sent and their status (pending / accepted / declined / expired / failed). Accepted invites include the worker's name and phone
- `tascan_list_invoices`: List invoices for the org (newest first) with status, client, total, due date and share link. Filter by status (draft/sent/paid/overdue/cancelled) or project.
- `tascan_list_issues`: 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 nee
- `tascan_list_payments`: List gig payments and their lifecycle status: awaiting_completion (pledged, work not verified yet), ready_to_pay (verified — pay link sent to payer), paid, canc
- `tascan_list_projects`: List TaScan projects in the organization (each with its number, e.g. P-00001, external_refs, report_options and its calendar_url, webcal_url, map_url and wallet
- `tascan_list_qr_styles`: Your saved QR looks (GET /qr-styles) with the per-purpose defaults, or, given task_id, list_id, project_id or site_id (and/or purpose share, placard, asset, rec
- `tascan_list_reports`: List existing report links for a list or project (completion / service / project / evidence), newest first, with client acknowledgment status for service report
- `tascan_list_scheduled_sms`: List your org's scheduled texts (default: pending + sending, soonest first; status=sent|failed|cancelled to see history). Each row shows send_at, status, attemp
- `tascan_list_sites`: List the organization's sites (job locations: name, address, lat/lng, client company, external key). Filters: active (true, the default, false or all), q (name,
- `tascan_list_subtasks`: List the subtasks of a task, including completion state, stored response values, and completion timestamps (per-set timing).
- `tascan_list_tags`: List all registered NFC tags in the organization with their linked projects/task lists and scan counts
- `tascan_list_tasks`: List the tasks in an event (task list). status "open" returns only tasks with no completion yet: use it when checking for work to do, so a long list is not re-r
- `tascan_list_templates`: List available task templates (built-in and saved)
- `tascan_list_verifications`: Read a task completion's verification verdicts and job queue (Verification Layer V2, GET /completions/:completion_id/verifications): completion_verifications ro
- `tascan_list_workers`: List workers (taskees) in the organization. Supports filtering by name/email/phone substring, contact-info presence, and last-activity date. Each row includes c
- `tascan_list_zones`: List geofenced work zones, optionally filtered by project. Shows center, radius, routing target, and zone-lock status.
- `tascan_merge_workers`: Merge duplicate worker records into one canonical identity (Patent 4 identity consolidation). Reassigns every reference (completions, timer events, points, paym
- `tascan_mint_completion_report`: Mint (or reuse) a task list's completion report and get its link (POST /lists/:id/completion-report): the same stable link tascan_generate_report type completio
- `tascan_nudge_worker`: Nudge a worker by text about a task list (POST /lists/:id/nudge), through the same guards as the Simple page's nudge: the list must be yours, the recipient must
- `tascan_org_analytics`: Read organization-wide analytics: view org (GET /analytics/org, the get_org_analytics rollup) or view resolutions (GET /analytics/resolutions, paginated AI issu
- `tascan_post_evidence`: Post one evidence event into the evidence ledger (protocol v0.2 V9a, POST /evidence): an actor did an action to an object at a point in time, optionally with a 
- `tascan_post_message`: Post a message on a task trail (protocol v0.2 trail_messages): kind question, answer, handoff or discussion. A message never completes a task, never satisfies a
- `tascan_project_digest`: One call that gives a chat client (ChatGPT, Claude) a whole TaScan project in about 2,000 words: the project, every task list with task counts, open decisions a
- `tascan_project_insights`: A project's progress and insights (GET /projects/:id/insights), counted like the portal's panel: per task list done of total (people's tasks), open issues by li

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.