Skip to content

Reclaim.ai MCP by usefulapi

io.usefulapi/reclaimaiusefulapi.iostreamable-httpv1.40.4Scanned

Read tasks, habits, events and scheduling links; create and update Reclaim tasks and habits.

15 tools: 9 can delete or cancel things and 6 only read.

Tools: 9 delete, 0 irreversible, 0 write, 6 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

9 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Reclaim.ai MCP by usefulapi can do

The Reclaim.ai MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 15 tools. It can delete or cancel things (9 tools: reclaim_create_task, reclaim_update_task, reclaim_mark_task_complete, reclaim_mark_task_incomplete and 5 more). 6 tools only read.

1 tool reads private data (reclaim_list_events).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Last scanned Oct 25, 2026, version 1.40.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

15 tools

Deletes or cancels 9Claude Code: deny
  • reclaim_add_timeAdd scheduled time to a task.No findings

    Why it is in this group

    • The name "reclaim_add_time" says "add": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Add scheduled time to a task. Reclaim REST: POST /api/planner/add-time/task/{id}.

    Annotations the server declares

    • title: Add time to task
    • destructiveHint: true
  • reclaim_create_taskCreate a new task.No findings

    Why it is in this group

    • The name "reclaim_create_task" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Create a new task. Reclaim schedules it into your calendar automatically. Reclaim REST: POST /api/tasks.

    Annotations the server declares

    • title: Create task
    • destructiveHint: true
  • reclaim_delete_taskPermanently delete a task.No findings

    Why it is in this group

    • The name "reclaim_delete_task" says "delete": a word for removing or ending something.
    • The description says "Permanently delete".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Permanently delete a task. Reclaim REST: DELETE /api/tasks/{id}.

    Annotations the server declares

    • title: Delete task
    • destructiveHint: true
  • reclaim_log_workLog completed work time against a task.1 finding

    Why it is in this group

    • The name "reclaim_log_work" says "log": a word for reading.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Warn

      The server marks "reclaim_log_work" destructive (destructiveHint: true), and its name says "log", a word for reading.

      Matched text

      annotations: {"destructiveHint":true}; The name "reclaim_log_work" says "log": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Log completed work time against a task. Reclaim REST: POST /api/planner/log-work/task/{id}.

    Annotations the server declares

    • title: Log work on task
    • destructiveHint: true
  • reclaim_mark_task_completeMark a task as done in the planner.No findings

    Why it is in this group

    • The name "reclaim_mark_task_complete" says "mark": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Mark a task as done in the planner. Reclaim REST: POST /api/planner/done/task/{id}.

    Annotations the server declares

    • title: Mark task complete
    • destructiveHint: true
  • reclaim_mark_task_incompleteReopen a completed task (unarchive) in the planner.No findings

    Why it is in this group

    • The name "reclaim_mark_task_incomplete" says "mark": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Reopen a completed task (unarchive) in the planner. Reclaim REST: POST /api/planner/unarchive/task/{id}.

    Annotations the server declares

    • title: Mark task incomplete
    • destructiveHint: true
  • reclaim_start_taskStart time-tracking on a task now.No findings

    Why it is in this group

    • The name "reclaim_start_task" says "start": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Start time-tracking on a task now. Reclaim REST: POST /api/planner/start/task/{id}.

    Annotations the server declares

    • title: Start task
    • destructiveHint: true
  • reclaim_stop_taskStop time-tracking on a task.No findings

    Why it is in this group

    • The name "reclaim_stop_task" says "stop": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Stop time-tracking on a task. Reclaim REST: POST /api/planner/stop/task/{id}.

    Annotations the server declares

    • title: Stop task
    • destructiveHint: true
  • reclaim_update_taskUpdate fields on an existing task.No findings

    Why it is in this group

    • The name "reclaim_update_task" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Update fields on an existing task. Only provided fields are changed. Reclaim REST: PATCH /api/tasks/{id}.

    Annotations the server declares

    • title: Update task
    • destructiveHint: true
Only reads 6Show 6 read-only tools
  • reclaim_get_current_userGet the authenticated Reclaim user's profile.No findings

    Why it is in this group

    • The name "reclaim_get_current_user" says "get": a word for reading.
    Description, as the server wrote it
    Get the authenticated Reclaim user's profile. Reclaim REST: GET /api/users/me.

    Annotations the server declares

    • title: Get current user
    • readOnlyHint: true
  • reclaim_get_habitGet a single daily habit by id.No findings

    Why it is in this group

    • The name "reclaim_get_habit" says "get": a word for reading.
    Description, as the server wrote it
    Get a single daily habit by id. Reclaim REST: GET /api/assist/habits/daily/{id}.

    Annotations the server declares

    • title: Get habit
    • readOnlyHint: true
  • reclaim_get_taskGet a single task by id.No findings

    Why it is in this group

    • The name "reclaim_get_task" says "get": a word for reading.
    Description, as the server wrote it
    Get a single task by id. Reclaim REST: GET /api/tasks/{id}.

    Annotations the server declares

    • title: Get task
    • readOnlyHint: true
  • reclaim_list_eventsList calendar events.Reads private dataNo findings

    Why it is in this group

    • The name "reclaim_list_events" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "calendar": it reads calendars.
    Description, as the server wrote it
    List calendar events. Reclaim REST: GET /api/events. Optional start/end window.

    Annotations the server declares

    • title: List events
    • readOnlyHint: true
  • reclaim_list_habitsList the authenticated user's daily habits.No findings

    Why it is in this group

    • The name "reclaim_list_habits" says "list": a word for reading.
    Description, as the server wrote it
    List the authenticated user's daily habits. Reclaim REST: GET /api/assist/habits/daily.

    Annotations the server declares

    • title: List habits
    • readOnlyHint: true
  • reclaim_list_tasksList the authenticated user's tasks.No findings

    Why it is in this group

    • The name "reclaim_list_tasks" says "list": a word for reading.
    Description, as the server wrote it
    List the authenticated user's tasks. Reclaim REST: GET /api/tasks.

    Annotations the server declares

    • title: List tasks
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 9 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://reclaimai.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://reclaimai.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "reclaim_log_work" destructive (destructiveHint: true), and its name says "log", a word for reading.

    Matched text

    annotations: {"destructiveHint":true}; The name "reclaim_log_work" says "log": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 9 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://reclaimai.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://reclaimai.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.40.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http reclaimai https://reclaimai.usefulapi.io/mcp
claude mcp add --transport http reclaimai https://reclaimai.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__reclaimai__reclaim_get_current_user",
      "mcp__reclaimai__reclaim_list_tasks",
      "mcp__reclaimai__reclaim_get_task",
      "mcp__reclaimai__reclaim_list_habits",
      "mcp__reclaimai__reclaim_get_habit",
      "mcp__reclaimai__reclaim_list_events"
    ],
    "ask": [],
    "deny": [
      "mcp__reclaimai__reclaim_create_task",
      "mcp__reclaimai__reclaim_update_task",
      "mcp__reclaimai__reclaim_mark_task_complete",
      "mcp__reclaimai__reclaim_mark_task_incomplete",
      "mcp__reclaimai__reclaim_start_task",
      "mcp__reclaimai__reclaim_stop_task",
      "mcp__reclaimai__reclaim_add_time",
      "mcp__reclaimai__reclaim_log_work",
      "mcp__reclaimai__reclaim_delete_task"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as reclaimai. Review it before you use it.

Capability tags behind 1 rule
  • mcp__reclaimai__reclaim_list_events private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/reclaimai/verify?hash=ad4c0fd096353fcb8d135b275d8ea1a796b8266a34bf74423d6c25919fd62b7c" | jq -e '.changed == false'

Pinned hash ad4c0fd09635, from Oct 25, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/reclaimai/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/reclaimai
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/reclaimai.svg)](https://radar.anlyon.com/servers/io.usefulapi/reclaimai)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:19 UTC.

Reclaim.ai MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Reclaim.ai MCP by usefulapi safe?

No scan can promise that. What its definitions show: 15 tools, 9 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Reclaim.ai MCP by usefulapi delete data?

Yes. 9 tools can delete, cancel or revoke something: reclaim_create_task, reclaim_update_task, reclaim_mark_task_complete, reclaim_mark_task_incomplete, reclaim_start_task, reclaim_stop_task and 3 more.

Can the Reclaim.ai MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Reclaim.ai MCP by usefulapi have?

15 tools: 9 destructive, 6 read. reclaim_create_task, reclaim_update_task, reclaim_mark_task_complete, reclaim_mark_task_incomplete, reclaim_start_task, reclaim_stop_task, reclaim_add_time, reclaim_log_work and 7 more.

Does the Reclaim.ai MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Reclaim.ai MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Reclaim.ai MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.