mcp-jp-calendar vs Taskforce

Side by side on the facts. GitHub figures come straight from each repository; ratings come from signed-in reviewers here.

Metricmcp-jp-calendarMCP Server TaskforceMCP Server

Type: mcp-jp-calendarMCP Server; TaskforceMCP Server
Category: mcp-jp-calendarProductivity; TaskforceProductivity
GitHub stars: mcp-jp-calendar0; Taskforce0
Trust scoreⓘAuditability and maintenance signals — not a security audit.: mcp-jp-calendarNot yet assessed; TaskforceNot yet assessed
Community rating: mcp-jp-calendarNo reviews yet; TaskforceNo reviews yet
Last commit: mcp-jp-calendarUnknown; TaskforceUnknown
Licence: mcp-jp-calendarNone declared; TaskforceNone declared
Official: mcp-jp-calendarNo; TaskforceNo
Source: mcp-jp-calendar Repository; Taskforce Repository

Highlighted cells win that row on an objective measure. Rows without a clear winner — category, licence, source — are left unmarked. A higher trust score means better auditability and maintenance, not safer code.