Reclaim.ai MCP by usefulapi
REMOTE · RECLAIMAI.USEFULAPI.IO
Read tasks, habits, events and scheduling links; create and update Reclaim tasks and habits.
Available components
Last scanned (4 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Productivity and Notes
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 → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 2 Nov 26 −62
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “add_a_task_or_change_an_existing_one” functional
- New prompt “add_time_or_log_work_on_a_task_then_complete_or_reopen_it” functional
- New prompt “list_your_tasks_with_due_dates_and_time_needed” functional
- New prompt “look_at_your_calendar_for_a_time_window” functional
- New prompt “review_your_daily_habits” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 0
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 0
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.0 → 1.21.3 functional
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.20.0 → 1.21.0 functional
- Server version: 1.19.0 → 1.20.0 functional
- Server version: 1.17.0 → 1.19.0 functional
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 5 Nov 2026 · Probed https://reclaimai.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of reclaimai.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://reclaimai.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/reclaimai/ |
| http (plaintext) | http://reclaimai.usefulapi.io/mcp | Inconclusive | 302 | http://reclaimai.usefulapi.io/mcp |
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 →
reclaim_add_time Add time to task ~61
Add scheduled time to a task. Reclaim REST: POST /api/planner/add-time/task/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The task id. |
| minutes | integer | yes | Minutes of time to add to the task (→ query param minutes). |
No output schema declared.
No examples provided.
reclaim_create_task Create task ~221
Create a new task. Reclaim schedules it into your calendar automatically. Reclaim REST: POST /api/tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| due | string | – | Due date/time (ISO-8601 Zulu datetime, e.g. 2026-07-20T17:00:00.000Z). |
| eventCategory | string | – | Task category — WORK or PERSONAL (default WORK). |
| maxChunkSize | integer | – | Maximum contiguous block, in 15-minute chunks. |
| minChunkSize | integer | – | Minimum contiguous block, in 15-minute chunks. |
| notes | string | – | Freeform notes / description for the task. |
| priority | string | – | Task priority — P1 (highest) … P4 (lowest). |
| snoozeUntil | string | – | Do not schedule before this time (ISO-8601 Zulu datetime). |
| timeChunksRequired | integer | – | Total scheduled time as a number of 15-minute chunks, e.g. 4 = 1 hour. |
| title | string | yes | The task title. |
No output schema declared.
No examples provided.
reclaim_delete_task Delete task ~38
Permanently delete a task. Reclaim REST: DELETE /api/tasks/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The task id to delete. |
No output schema declared.
No examples provided.
reclaim_get_current_user Get current user ~28
Get the authenticated Reclaim user's profile. Reclaim REST: GET /api/users/me.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
reclaim_get_habit Get habit ~45
Get a single daily habit by id. Reclaim REST: GET /api/assist/habits/daily/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The habit id. |
No output schema declared.
No examples provided.
reclaim_get_task Get task ~37
Get a single task by id. Reclaim REST: GET /api/tasks/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The task id. |
No output schema declared.
No examples provided.
reclaim_list_events List events ~73
List calendar events. Reclaim REST: GET /api/events. Optional start/end window.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | End of the calendar events window (ISO date/datetime string → query param end). |
| start | string | – | Start of the calendar events window (ISO date/datetime string → query param start). |
No output schema declared.
No examples provided.
reclaim_list_habits List habits ~33
List the authenticated user's daily habits. Reclaim REST: GET /api/assist/habits/daily.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
reclaim_list_tasks List tasks ~24
List the authenticated user's tasks. Reclaim REST: GET /api/tasks.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
reclaim_log_work Log work on task ~84
Log completed work time against a task. Reclaim REST: POST /api/planner/log-work/task/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | End time of the logged work (ISO-8601 Zulu datetime → query param end). |
| id | string | yes | The task id. |
| minutes | integer | yes | Minutes of work to log (→ query param minutes). |
No output schema declared.
No examples provided.
reclaim_mark_task_complete Mark task complete ~47
Mark a task as done in the planner. Reclaim REST: POST /api/planner/done/task/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The task id to mark complete. |
No output schema declared.
No examples provided.
reclaim_mark_task_incomplete Mark task incomplete ~52
Reopen a completed task (unarchive) in the planner. Reclaim REST: POST /api/planner/unarchive/task/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The task id to mark incomplete. |
No output schema declared.
No examples provided.
reclaim_start_task Start task ~44
Start time-tracking on a task now. Reclaim REST: POST /api/planner/start/task/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The task id to start. |
No output schema declared.
No examples provided.
reclaim_stop_task Stop task ~44
Stop time-tracking on a task. Reclaim REST: POST /api/planner/stop/task/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The task id to stop. |
No output schema declared.
No examples provided.
reclaim_update_task Update task ~214
Update fields on an existing task. Only provided fields are changed. Reclaim REST: PATCH /api/tasks/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| due | string | – | Due date/time (ISO-8601 Zulu datetime). |
| eventCategory | string | – | Task category — WORK or PERSONAL (default WORK). |
| id | string | yes | The task id to update. |
| maxChunkSize | integer | – | Maximum contiguous block, in 15-minute chunks. |
| minChunkSize | integer | – | Minimum contiguous block, in 15-minute chunks. |
| notes | string | – | Freeform notes / description for the task. |
| priority | string | – | Task priority — P1 (highest) … P4 (lowest). |
| snoozeUntil | string | – | Do not schedule before this time (ISO-8601 Zulu datetime). |
| timeChunksRequired | integer | – | Total scheduled time as a number of 15-minute chunks, e.g. 4 = 1 hour. |
| title | string | – | The task title. |
No output schema declared.
No examples provided.
How do I install the Reclaim.ai MCP by usefulapi server?
Reclaim.ai MCP by usefulapi is a hosted endpoint at https://reclaimai.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · reclaimai.usefulapi.io
claude mcp add --transport http io-usefulapi-reclaimai 'https://reclaimai.usefulapi.io/mcp'
What is the Reclaim.ai MCP by usefulapi server?
Reclaim.ai MCP by usefulapi is listed in the public MCP registry as io.usefulapi/reclaimai. Read tasks, habits, events and scheduling links; create and update Reclaim tasks and habits. This page covers its hosted endpoint (https://reclaimai.usefulapi.io/mcp).
Is the Reclaim.ai MCP by usefulapi server safe to use?
Reclaim.ai MCP by usefulapi scores 18 out of 100 on VerifyMCP. 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 Reclaim.ai MCP by usefulapi server expose?
Reclaim.ai MCP by usefulapi exposes 15 tools: reclaim_get_current_user, reclaim_list_tasks, reclaim_get_task, reclaim_list_habits, reclaim_get_habit, and 10 more. Their descriptions and schemas cost roughly 1,045 tokens of context every time the server is loaded.
Does the Reclaim.ai MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Reclaim.ai MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Reclaim.ai MCP by usefulapi server still maintained?
Reclaim.ai MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.