Should my agent depend on the MCP server io.github.snowbikemike/tascan-mcp?

Verdict: allow — stale-mid-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

TaScan

io.github.snowbikemike/tascan-mcp

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

— the operator's own registry description reported

Publisher io.github.snowbikemike · first seen 2026-08-12 · endpoint https://tascan-live-event.netlify.app/mcp

allow

verdict

stale-mid-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — stale-mid-solo — safe to depend on

Cluster stale-mid-solo · distinctiveness 0.215 (typical). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency223 ms

vs populationtypical

protocolbehind

authopen

Use — can it use it?

tools32

vs populationmid

capabilities1

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_29392044e35136ed2255d171 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

tascan_add_tasks tascan_analyze_issue tascan_apply_template tascan_auto_resolve tascan_complete_task tascan_create_event tascan_create_project tascan_create_worker tascan_delete_event tascan_delete_project tascan_delete_task tascan_dispatch_instruction tascan_dispatch_to_agent tascan_generate_qr tascan_get_event tascan_get_project tascan_get_report tascan_get_task tascan_list_agents tascan_list_events tascan_list_issues tascan_list_projects tascan_list_tasks tascan_list_templates tascan_list_workers tascan_recommend_fix tascan_register_agent tascan_send_task_email tascan_update_event tascan_update_project tascan_update_task tascan_update_worker

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	32/32	✓
has a description	32/32	✓
description is substantive	30/32	30/32
parameters are typed	32/32	✓
parameters are described	32/32	✓

32 of 32 tools graded · 32 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-03-26

protocol version

—

session model

1.3.0

server version tascan

Capabilities: tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T20:00:13Z	ok_tools	200	223	2025-03-26
2026-08-12T05:35:25Z	ok_tools	200	397	2025-03-26

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.snowbikemike/tascan-mcp.svg)](https://robinsaige.com/s/io.github.snowbikemike/tascan-mcp)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview