TaScan

REMOTE · TASCAN-LIVE-EVENT.NETLIFY.APP · 2 COMPONENTS · SCANNED AUG 3

Universal task protocol — manage projects, tasks, workers, QR codes, and reports.

Available components

remote · tascan-live-event.netlify.app 76 npm · tascan-mcp 35

+8 this week 76 76 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security89

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability71

AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 2585 tokens (~80/item across 32 items; 32 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 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

Capabilities40

Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · tascan-live-event.netlify.app

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http snowbikemike-tascan-mcp https://tascan-live-event.netlify.app/mcp

# ~/.codex/config.toml

[mcp_servers.snowbikemike-tascan-mcp]
url = "https://tascan-live-event.netlify.app/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "snowbikemike-tascan-mcp": {
      "type": "remote",
      "url": "https://tascan-live-event.netlify.app/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add snowbikemike-tascan-mcp --url https://tascan-live-event.netlify.app/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  snowbikemike-tascan-mcp:
    url: "https://tascan-live-event.netlify.app/mcp"

// mcp.json

{
  "mcpServers": {
    "snowbikemike-tascan-mcp": {
      "type": "http",
      "url": "https://tascan-live-event.netlify.app/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

3 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
1 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 +4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
28 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 67

First indexed and scored.

Show 6 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 2026 · Probed https://tascan-live-event.netlify.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=*.netlify.app,O=Netlify\, Inc,L=San Francisco,ST=California,C=US	CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US	16 Feb 2026	19 Mar 2027	ECDSA 256	SHA256-RSA	cd5d0afb0611b5bd9d692535c0ca7c4
SANs: *.netlify.app, netlify.app
CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US (CA)	CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US	30 Mar 2021	29 Mar 2031	RSA 2048	SHA256-RSA	cf5bd062b5602f47ab8502c23ccf066

DNSSEC insecure

Validation of tascan-live-event.netlify.app. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
app.	present	23684	8	Verified
netlify.app.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result	Challenged, unverified
Enforced	On tool calls
HTTP status	200

WWW-Authenticate challenge Bearer resource_metadata="https://app.tascan.io/.well-known/oauth-protected-resource"

Bearer resource_metadata="https://app.tascan.io/.well-known/oauth-protected-resource"

Header	Value
strict-transport-security	max-age=31536000; includeSubDomains; preload

Protected resource metadata

Document	https://app.tascan.io/.well-known/oauth-protected-resource
Retrieved	Yes
Problem	metadata_resource_mismatch
Resource	https://app.tascan.io/mcp
Authorisation server	https://app.tascan.io

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://tascan-live-event.netlify.app/mcp	Verified	200
http (plaintext)	http://tascan-live-event.netlify.app/mcp	HTTPS enforced	301	https://tascan-live-event.netlify.app/mcp

MCP tools — 32 exposed · ~2,585 tokens

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.

Tool Tokens

tascan_add_tasks ~136

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.

Input Output Examples

Name	Type	Req	Description
list_id	string	yes	Task list (event) ID
tasks	array	yes	Array of tasks to create

No output schema declared.

No examples provided.

tascan_analyze_issue ~119

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).

Input Output Examples

Name	Type	Req	Description
issue_id	string	yes	Issue ID to analyze
server_side_ai	boolean	—	If true, the server calls Anthropic API directly for AI analysis (default: false — returns raw data for MCP client to analyze)

No output schema declared.

No examples provided.

tascan_apply_template ~63

Apply a pre-built template to a task list, adding all template tasks

Input Output Examples

Name	Type	Req	Description
list_id	string	yes	Task list (event) ID
template_slug	string	yes	Template slug (e.g. "conference-load-in", "warehouse-receiving")

No output schema declared.

No examples provided.

tascan_auto_resolve ~82

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.

Input Output Examples

Name	Type	Req	Description
issue_id	string	yes	Issue ID to auto-resolve

No output schema declared.

No examples provided.

tascan_complete_task ~93

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.

Input Output Examples

Name	Type	Req	Description
notes	string	—	Optional completion notes
response_value	string	—	Response value (for text/number/choice tasks)
task_id	string	yes	Task ID to complete
worker_id	string	yes	Worker ID performing the completion

No output schema declared.

No examples provided.

tascan_create_event ~117

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.

Input Output Examples

Name	Type	Req	Description
description	string	—	Event description
multi_instance	boolean	—	Multi-instance — each worker gets isolated copy
name	string	yes	Event name
project_id	string	yes	Project ID
team_mode	boolean	—	Team mode — shared completions

No output schema declared.

No examples provided.

tascan_create_project ~43

Create a new TaScan project (top-level container for events)

Input Output Examples

Name	Type	Req	Description
location	string	—	Project location / venue
name	string	yes	Project name

No output schema declared.

No examples provided.

tascan_create_worker ~48

Create a new worker (taskee) in the organization

Input Output Examples

Name	Type	Req	Description
email	string	—	Email
name	string	yes	Worker name
phone	string	—	Phone number

No output schema declared.

No examples provided.

tascan_delete_event ~46

Delete an event (task list) and all its tasks and completions. This action is irreversible.

Input Output Examples

Name	Type	Req	Description
list_id	string	yes	Task list (event) ID to delete

No output schema declared.

No examples provided.

tascan_delete_project ~41

Delete a project and all its events, tasks, and completions. This action is irreversible.

Input Output Examples

Name	Type	Req	Description
project_id	string	yes	Project ID to delete

No output schema declared.

No examples provided.

tascan_delete_task ~36

Delete a specific task and its completions. This action is irreversible.

Input Output Examples

Name	Type	Req	Description
task_id	string	yes	Task ID to delete

No output schema declared.

No examples provided.

tascan_dispatch_instruction ~234

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.

Input Output Examples

Name	Type	Req	Description
ai_agent	string	—	Name of the AI agent dispatching (default: TaScan AI)
instruction	string	yes	Clear, actionable instruction for the worker to execute
issue_id	string	yes	Issue ID this instruction relates to
recommendation_summary	string	—	One-line summary for the task list description
remediation_tasks	array	—	Optional array of tasks to create as a remediation task list. Each: { title, description, response_type, requires_photo, is_safety_checkpoint, sort_order }
send_sms	boolean	—	Send SMS to worker (default: true if phone on file)
worker_id	string	—	Target worker ID (defaults to the worker who reported the issue)

No output schema declared.

No examples provided.

tascan_dispatch_to_agent ~164

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.

Input Output Examples

Name	Type	Req	Description
agent	string	—	Agent ID or name to dispatch to (default: claude-code-local). Use tascan_list_agents to see options.
priority	string	—	Priority level (default: normal)
task	string	yes	The task description. Prefix with CODE: SHELL: RESEARCH: WRITE: PLAN: for routing, or just plain text.

No output schema declared.

No examples provided.

tascan_generate_qr ~44

Generate a QR code for a task list (event) that workers can scan to access tasks

Input Output Examples

Name	Type	Req	Description
list_id	string	yes	Task list (event) ID

No output schema declared.

No examples provided.

tascan_get_event ~38

Get details of a specific event (task list) including its tasks

Input Output Examples

Name	Type	Req	Description
list_id	string	yes	Task list (event) ID

No output schema declared.

No examples provided.

tascan_get_project ~27

Get details of a specific project

Input Output Examples

Name	Type	Req	Description
project_id	string	yes	Project ID

No output schema declared.

No examples provided.

tascan_get_report ~46

Get completion report for a task list (event) including task status, completions, workers, and photos

Input Output Examples

Name	Type	Req	Description
list_id	string	yes	Task list (event) ID

No output schema declared.

No examples provided.

tascan_get_task ~30

Get details of a specific task including completions

Input Output Examples

Name	Type	Req	Description
task_id	string	yes	Task ID

No output schema declared.

No examples provided.

tascan_list_agents ~49

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.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tascan_list_events ~31

List all events (task lists) within a project

Input Output Examples

Name	Type	Req	Description
project_id	string	yes	Project ID

No output schema declared.

No examples provided.

tascan_list_issues ~67

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.

Input Output Examples

Name	Type	Req	Description
list_id	string	yes	Task list (event) ID

No output schema declared.

No examples provided.

tascan_list_projects ~19

List all TaScan projects in the organization

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tascan_list_tasks ~34

List all tasks in an event (task list)

Input Output Examples

Name	Type	Req	Description
list_id	string	yes	Task list (event) ID

No output schema declared.

No examples provided.

tascan_list_templates ~45

List available task templates (built-in and saved)

Input Output Examples

Name	Type	Req	Description
category	string	—	Filter by category (e.g. "live-events", "hospitality", "logistics")

No output schema declared.

No examples provided.

tascan_list_workers ~22

List all workers (taskees) in the organization

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tascan_recommend_fix ~176

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.

Input Output Examples

Name	Type	Req	Description
ai_agent	string	—	Name of the AI agent posting (default: TaScan AI)
issue_id	string	yes	Issue ID to recommend a fix for
recommendation	string	yes	The AI-generated recommendation text (clear, actionable instructions)
structured_recommendation	object	—	Optional structured recommendation with tasks for auto-dispatch. Format: { recommendation_summary, confidence_score, tasks: [{ title, description, response_type, requires_photo, is_safety_checkpoint,…

No output schema declared.

No examples provided.

tascan_register_agent ~201

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.

Input Output Examples

Name	Type	Req	Description
capabilities	array	yes	Task type prefixes this agent handles (e.g. ["RESEARCH", "WRITE"])
description	string	—	What this agent does
id	string	yes	Unique agent ID (e.g. "my-agent-1")
inbox_id	string	yes	Task list ID this agent monitors for new tasks
location	string	—	Where the agent runs (e.g. "AWS us-east-1")
model	string	—	Model powering this agent (e.g. "claude-sonnet-4-6")
name	string	yes	Display name (e.g. "Research Bot")
type	string	yes	Agent type
worker_id	string	—	TaScan worker ID for this agent

No output schema declared.

No examples provided.

tascan_send_task_email ~154

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.

Input Output Examples

Name	Type	Req	Description
include_qr	boolean	—	Include QR code for the task list in the email (default: true)
list_id	string	yes	Task list (event) ID
message	string	—	Optional custom message to include in the email body
subject	string	—	Custom email subject (defaults to auto-generated)
task_id	string	—	Optional specific task ID to highlight
to_email	string	yes	Recipient email address
to_name	string	—	Recipient display name

No output schema declared.

No examples provided.

tascan_update_event ~116

Update an event / task list (name, description, team_mode, multi_instance, timer_mode). team_mode and multi_instance cannot both be true.

Input Output Examples

Name	Type	Req	Description
description	string	—	New description
list_id	string	yes	Task list (event) ID
multi_instance	boolean	—	Multi-instance — each worker gets isolated copy
name	string	—	New name
team_mode	boolean	—	Team mode — shared completions
timer_mode	string	—	Timer mode (auto or manual)

No output schema declared.

No examples provided.

tascan_update_project ~82

Update a project (name, location, status, dates)

Input Output Examples

Name	Type	Req	Description
end_date	string	—	End date (ISO)
location	string	—	New location
name	string	—	New name
project_id	string	yes	Project ID
start_date	string	—	Start date (ISO)
status	string	—	Status

No output schema declared.

No examples provided.

tascan_update_task ~124

Update a task (title, description, response_type, flags, sort_order)

Input Output Examples

Name	Type	Req	Description
description	string	—	New description
is_safety_checkpoint	boolean	—	Safety-critical flag
requires_photo	boolean	—	Require photo
response_type	string	—	See tascan_add_tasks for guidance. "text" for info collection, "photo" for visual proof, "checkbox" for yes/no only.
sort_order	number	—	Sort position
task_id	string	yes	Task ID
title	string	—	New title

No output schema declared.

No examples provided.

tascan_update_worker ~58

Update a worker profile (name, phone, email)

Input Output Examples

Name	Type	Req	Description
email	string	—	New email
name	string	—	New name
phone	string	—	New phone
worker_id	string	yes	Worker ID

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	67
27 Jul	68
28 Jul	69
29 Jul	69
30 Jul	70
31 Jul	74
1 Aug	75
2 Aug	75
3 Aug	76