tascan-mcp 3.15.0 → 3.16.0

package/README.md

@@ -83,7 +83,7 @@ https://app.tascan.io/mcp
 
 Add as a custom connector in Claude (Settings > Connectors). When you first use a tool, you'll be redirected to sign in with your TaScan email and password — just like connecting GitHub or Netlify. OAuth 2.0 with PKCE handles everything automatically.
 
-## Tools (36)
+## Tools (90)
 
 ### Projects
 | Tool | Description | Type |
@@ -158,6 +158,26 @@ Add as a custom connector in Claude (Settings > Connectors). When you first use
 | `tascan_register_agent` | Register a new AI agent with capabilities | Create |
 | `tascan_dispatch_to_agent` | Route a task to a specific AI agent for execution | Create |
 
+### Protocol Layer — Coordination, Receipts, Evidence, Verification, Analytics
+
+This table lists only the 10 tools M1 (2026-09-23) added; the coordination-cycle tools from earlier milestones
+(`tascan_create_cycle`, `tascan_post_message`, `tascan_record_integration`, `tascan_get_build`,
+`tascan_get_build_file`, `tascan_get_cycle_report`, `tascan_project_digest`, `tascan_get_receipt`) are documented
+inline in their tool descriptions (`tascan_list_tools` / your MCP client's tool browser shows all 90).
+
+| Tool | Description | Type |
+|------|-------------|------|
+| `tascan_list_cycles` | List coordination-cycle roots (id, title, status, build_ref, deploy_id), filterable by project/status | Read |
+| `tascan_get_task_trail` | Read a task's trail messages (question/answer/handoff/note), newest last | Read |
+| `tascan_verify_receipt` | Independently verify an Action Receipt JWS against the reference verifier (works for a foreign issuer too) | None |
+| `tascan_get_build_diff` | Store an already-computed diff for one build-bundle file against a base commit | Write + Dispatch |
+| `tascan_dispatcher_action` | Record a chief-of-staff dispatcher action (approve/revise/park/deploy/decision/...) as a receipt | Write + Dispatch |
+| `tascan_post_evidence` | Post one evidence event (actor did action to object at a time) into the evidence ledger | Write |
+| `tascan_evidence_policy` | Read (action=get) or author/pin (action=set) a task's evidence policy | Read/Write |
+| `tascan_request_verification` | Enqueue an autonomous verification job (http_probe or doc_check) for a completion | Write |
+| `tascan_list_verifications` | Read a completion's verification verdicts and job queue | Read |
+| `tascan_org_analytics` | Read org-wide analytics: the org rollup or paginated AI issue-resolution history | Read |
+
 ## Usage Examples
 
 ### Example 1: Set up a construction site inspection

package/index.js

@@ -46,7 +46,7 @@ async function api(method, path, body) {
 api.key = API_KEY;   // raw-fetch tools read the key from here (S99: those functions now require auth)
 
 const server = new Server(
-  { name: 'tascan', version: '3.15.0' },
+  { name: 'tascan', version: '3.16.0' },
   { capabilities: { tools: {} } }
 );
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "tascan-mcp",
-  "version": "3.15.0",
+  "version": "3.16.0",
   "mcpName": "io.github.snowbikemike/tascan-mcp",
   "description": "TaScan MCP Server — Closed-loop autonomous operations protocol. 70 tools for projects, tasks, workers, QR codes, NFC tags, worker marketplace with consented SMS invites, geofenced zones with rules (work site / hazard + AI-verified PPE checkpoints / containment / restricted, breach alerts, zone compliance audit), AI condition assessment, worker passports, verification-gated gig payments, client invoicing from verified work (overtime / day rate / per diem / expenses), shareable report links (completion, client service report, project, evidence pack), signed Action Receipts (Ed25519 JWS), cross-entity search, duplicate-worker detection, worker identity merge, AI issue analysis, and autonomous remediation dispatch. 15 patents filed (470+ claims). Task. Scan. Done.",
   "type": "module",