io.usefulapi/reclaimai

REMOTE · RECLAIMAI.USEFULAPI.IO · SCANNED AUG 3

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

Available components

70 70 Trust /100

Trust breakdown (6 categories)

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 →

Endpoint Security78

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. 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
The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability77

AI-judged instruction clarity (excellent).Pass
Tool/resource definitions use about 1045 tokens (~69/item across 15 items; 15 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management3

Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities60

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · reclaimai.usefulapi.io

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.toml

[mcp_servers.io-usefulapi-reclaimai]
url = "https://reclaimai.usefulapi.io/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-reclaimai": {
      "type": "remote",
      "url": "https://reclaimai.usefulapi.io/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add io-usefulapi-reclaimai --url https://reclaimai.usefulapi.io/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  io-usefulapi-reclaimai:
    url: "https://reclaimai.usefulapi.io/mcp"

// mcp.json

{
  "mcpServers": {
    "io-usefulapi-reclaimai": {
      "type": "http",
      "url": "https://reclaimai.usefulapi.io/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

3 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
2 Aug 26 +52
- Authorization: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: excellent functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
1 Aug 26 18

First indexed and scored.

Show 1 earlier entry Hide earlier entries

Diagnostics

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 3 Aug 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	1 Aug 2026	30 Oct 2026	ECDSA 256	ECDSA-SHA256	f85935917dfad3e113b07247bfa34b93
SANs: usefulapi.io, reclaimai.usefulapi.io, *.reclaimai.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

DNSSEC insecure

Validation of reclaimai.usefulapi.io. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
io.	present	57355	8	Verified
usefulapi.io.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result	Enforced and verified
Enforced	On tool calls
HTTP status	200

WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://reclaimai.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"

Bearer realm="OAuth", resource_metadata="https://reclaimai.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"

Protected resource metadata

Document	https://reclaimai.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved	Yes
Resource	https://reclaimai.usefulapi.io/mcp
Authorisation server	https://reclaimai.usefulapi.io

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://reclaimai.usefulapi.io/mcp	Verified	200
http (plaintext)	http://reclaimai.usefulapi.io/mcp	Inconclusive	401

MCP tools — 15 exposed · ~1,045 tokens

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.

Tool Tokens

reclaim_add_time Add time to task ~61

Add scheduled time to a task. Reclaim REST: POST /api/planner/add-time/task/{id}.

Input Output Examples

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.

Input Output Examples

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}.

Input Output Examples

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 Output Examples

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}.

Input Output Examples

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}.

Input Output Examples

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.

Input Output Examples

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 Output Examples

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 Output Examples

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}.

Input Output Examples

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}.

Input Output Examples

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}.

Input Output Examples

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}.

Input Output Examples

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}.

Input Output Examples

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}.

Input Output Examples

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

1 Aug 3 Aug