TaskTime Pro
NPM · @TASKTIMEPRO/AGENT-BRIDGE · SCANNED SEP 21
First-party local TaskTime Pro tools for tasks, timers, expenses, invoices, reports, and planning.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to tasktimepro/tasktime). View diagnostics → Pass
- Clear OSI-approved license (AGPL-3.0-only).Pass
- Actively maintained (last published 5 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability53
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 7625 tokens (~61/item across 124 items; 124 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 21 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "cascade_delete_client" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 124 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the TaskTime Pro MCP server?
TaskTime Pro runs locally as an npm package, launched with npx -y @tasktimepro/agent-bridge. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @tasktimepro/agent-bridge
claude mcp add pro-tasktime-agent-bridge -- npx -y @tasktimepro/agent-bridge
{
"mcpServers": {
"pro-tasktime-agent-bridge": {
"command": "npx",
"args": [
"-y",
"@tasktimepro/agent-bridge"
]
}
}
} {
"servers": {
"pro-tasktime-agent-bridge": {
"command": "npx",
"args": [
"-y",
"@tasktimepro/agent-bridge"
]
}
}
} codex mcp add pro-tasktime-agent-bridge -- npx -y @tasktimepro/agent-bridge
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pro-tasktime-agent-bridge": {
"type": "local",
"command": [
"npx",
"-y",
"@tasktimepro/agent-bridge"
],
"enabled": true
}
}
} openclaw mcp add pro-tasktime-agent-bridge --command npx --arg -y --arg @tasktimepro/agent-bridge
mcp_servers:
pro-tasktime-agent-bridge:
command: "npx"
args: ["-y", "@tasktimepro/agent-bridge"] {
"McpServers": {
"pro-tasktime-agent-bridge": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@tasktimepro/agent-bridge"
]
}
}
} assistant mcp add pro-tasktime-agent-bridge -t stdio -c npx -a -y @tasktimepro/agent-bridge
{
"mcpServers": {
"pro-tasktime-agent-bridge": {
"command": "npx",
"args": [
"-y",
"@tasktimepro/agent-bridge"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +13
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.80 functional
- 16 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- Package version: 1.1.0 → 1.2.0 functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −2
- Stability: pass → 0.80 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Sept 2026 · Analysed npm/@tasktimepro/agent-bridge@1.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | tasktimepro/tasktime |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/tasktimepro/tasktime/.github/workflows/publish-agent-bridge.yml@refs/heads/main |
| Rekor log index | 2857783654 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:6f93aad9cf9536a5cedf79ad529fceb3f690f4f11c3ef8e25312959893742ce62326d9eea82e02c88048dfcf2fb8ebe52e2b778f6538306d5d6bc0422 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
start_timer ~51
Start a timer for a task. Existing active timers for the same key are not overwritten.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotencyKey | string | – | – |
| note | string | – | – |
| taskId | string | yes | – |
No output schema declared.
No examples provided.
stop_timer ~53
Stop a timer and create one matching time entry with complete-history validation and replay/concurrency recovery.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotencyKey | string | – | – |
| taskId | string | – | – |
| timerKey | string | – | – |
No output schema declared.
No examples provided.
unarchive_business_brand_asset ~36
Restore an archived business logo brand asset without changing invoices or business profile references.
| Name | Type | Req | Description |
|---|---|---|---|
| businessBrandAssetId | string | yes | – |
No output schema declared.
No examples provided.
unarchive_client ~40
Restore an archived client without changing related data. Free includes one active client; trial and Pro include unlimited active clients.
| Name | Type | Req | Description |
|---|---|---|---|
| clientId | string | yes | – |
No output schema declared.
No examples provided.
unarchive_expense_category ~33
Restore an archived expense category without changing related expenses or recurring templates.
| Name | Type | Req | Description |
|---|---|---|---|
| expenseCategoryId | string | yes | – |
No output schema declared.
No examples provided.
unarchive_project ~26
Restore an archived project without changing related data.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | – |
No output schema declared.
No examples provided.
unarchive_task ~36
Restore an archived task using TaskTime Pro unarchive behavior. This is not a destructive recreate.
| Name | Type | Req | Description |
|---|---|---|---|
| taskId | string | yes | – |
No output schema declared.
No examples provided.
update_business_brand_asset ~41
Update a business logo brand asset without deleting invoices or business profile references.
| Name | Type | Req | Description |
|---|---|---|---|
| businessBrandAssetId | string | yes | – |
| updates | object | yes | – |
No output schema declared.
No examples provided.
update_business_info ~39
Update a business profile without deleting invoices, expenses, or brand assets.
| Name | Type | Req | Description |
|---|---|---|---|
| businessInfoId | string | yes | – |
| updates | object | yes | – |
No output schema declared.
No examples provided.
update_client ~42
Update client fields. Editing is always available; changing archived to false applies the active-client policy.
| Name | Type | Req | Description |
|---|---|---|---|
| clientId | string | yes | – |
| updates | object | yes | – |
No output schema declared.
No examples provided.
update_email_template ~33
Update an invoice or quote email template.
| Name | Type | Req | Description |
|---|---|---|---|
| emailTemplateId | string | yes | – |
| updates | object | yes | – |
No output schema declared.
No examples provided.
update_expense_category ~45
Update expense category metadata such as name, group, color, default flag, and archive state.
| Name | Type | Req | Description |
|---|---|---|---|
| expenseCategoryId | string | yes | – |
| updates | object | yes | – |
No output schema declared.
No examples provided.
update_expense_recurrence ~43
Update a recurring expense template for future generated expenses without mutating already-created expenses.
| Name | Type | Req | Description |
|---|---|---|---|
| recurrenceId | string | yes | – |
| updates | object | yes | – |
No output schema declared.
No examples provided.
update_invoice_draft ~82
Edit allowed metadata, line items, totals, and UI composition fields on an existing draft invoice. Set draftNumberMode to automatic or manual; an invoiceNumber edit defaults to manual. This does not mark billing state, update task billing cutoffs, link projects, or advance invoice numbering.
| Name | Type | Req | Description |
|---|---|---|---|
| invoiceId | string | yes | – |
| updates | object | yes | – |
No output schema declared.
No examples provided.
update_invoice_template ~39
Update an invoice template. Sequence changes are allowed but should be deliberate.
| Name | Type | Req | Description |
|---|---|---|---|
| invoiceTemplateId | string | yes | – |
| updates | object | yes | – |
No output schema declared.
No examples provided.
update_payment_method ~39
Update a payment method without deleting invoices or expenses that reference older snapshots.
| Name | Type | Req | Description |
|---|---|---|---|
| paymentMethodId | string | yes | – |
| updates | object | yes | – |
No output schema declared.
No examples provided.
update_planner_attachment ~37
Update planner attachment options such as estimated hours.
| Name | Type | Req | Description |
|---|---|---|---|
| estimatedHours | number|null | – | – |
| plannerAttachmentId | string | yes | – |
No output schema declared.
No examples provided.
update_preferences ~61
Update non-sync user preferences such as currency, theme, date/time format, default view, week start, task visibility, default billable behavior, sorting, weekly goals, and notification time. Sync/backup preferences are intentionally rejected.
| Name | Type | Req | Description |
|---|---|---|---|
| updates | object | yes | – |
No output schema declared.
No examples provided.
update_project ~49
Update non-destructive project fields such as title, rates, client link, color, deadline, budget, and task view preferences.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | – |
| updates | object | yes | – |
No output schema declared.
No examples provided.
update_project_notes ~60
Update project notes with plain text or TipTap JSON using the same persisted notes payload as the UI.
| Name | Type | Req | Description |
|---|---|---|---|
| clear | boolean | – | – |
| content | object|null | – | – |
| plainText | string | – | – |
| projectId | string | yes | – |
No output schema declared.
No examples provided.
update_task ~76
Update a TaskTime Pro task through relationship and task-state invariants. Use complete_task for recurring occurrences. Set updates.recurring.paused to true to pause the schedule or false to resume without catching up; include the recurrence type and schedule. Timer state is unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| taskId | string | yes | – |
| updates | object | yes | – |
No output schema declared.
No examples provided.
update_tax_return_period ~55
Update non-status tax return period metadata such as title, dates, business profile, and notes. Filing/payment status changes use explicit status tools.
| Name | Type | Req | Description |
|---|---|---|---|
| taxReturnPeriodId | string | yes | – |
| updates | object | yes | – |
No output schema declared.
No examples provided.
update_time_entry ~88
Edit an active unbilled time entry after validating source/target task, billing cutoff, and complete-history overlap rules. Historical and billed entries are rejected.
| Name | Type | Req | Description |
|---|---|---|---|
| billingIncrementMinutes | number|null | – | – |
| end | number | – | – |
| entryId | string | yes | – |
| note | string|null | – | – |
| start | number | – | – |
| taskId | string | – | – |
No output schema declared.
No examples provided.
update_timer ~50
Update an active timer note and/or start timestamp.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string|null | – | – |
| startTime | number | – | – |
| taskId | string | – | – |
| timerKey | string | – | – |
No output schema declared.
No examples provided.
What is the TaskTime Pro MCP server?
TaskTime Pro is an MCP server listed in the public MCP registry as pro.tasktime/agent-bridge. First-party local TaskTime Pro tools for tasks, timers, expenses, invoices, reports, and planning. This page covers its npm package (@tasktimepro/agent-bridge).
Is the TaskTime Pro MCP server safe to use?
TaskTime Pro scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the TaskTime Pro MCP server expose?
TaskTime Pro exposes 124 tools: add_manual_time_entry, archive_business_brand_asset, archive_client, archive_expense_category, archive_project, and 119 more. Their descriptions and schemas cost roughly 7,625 tokens of context every time the server is loaded.
Is the TaskTime Pro MCP server still maintained?
TaskTime Pro is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the TaskTime Pro MCP server under?
TaskTime Pro declares the AGPL-3.0-only licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.