# Intentions MCP Server (remote · mcp.intentions.me)

Personalized timing intelligence for AI agents — ask 'should I do X on this date?'

- Trust score: 55/100 (low)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- remote · `mcp.intentions.me`: 55/100 (this document), [markdown](https://verifymcp.io/servers/intentions-me-intentions-mcp/mcp.md), [page](https://verifymcp.io/servers/intentions-me-intentions-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.intentions.me/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-04.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 14/100
  - AI-judged instruction clarity (poor).
  - Context-footprint check failed: tool/resource definitions use about 4578 tokens (~654/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http intentions-me-intentions-mcp https://mcp.intentions.me/mcp
```

### Codex

```toml
[mcp_servers.intentions-me-intentions-mcp]
url = "https://mcp.intentions.me/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "intentions-me-intentions-mcp": {
      "type": "remote",
      "url": "https://mcp.intentions.me/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add intentions-me-intentions-mcp --url https://mcp.intentions.me/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  intentions-me-intentions-mcp:
    url: "https://mcp.intentions.me/mcp"
```

### Other

```json
{
  "mcpServers": {
    "intentions-me-intentions-mcp": {
      "type": "http",
      "url": "https://mcp.intentions.me/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 55, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 54, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 53, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 50, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 50, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 49, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 48, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 48)

First indexed and scored.

## MCP tools (7)

### `intentions_ask_day` (~314 tokens)

Call when the user asks about timing a decision for a specific date, or wants to pick the best day from a multi-day window. Covers trip dates, launch days, interview/meeting days, publish/send dates, travel, negotiation windows, relationship moments — any "when to X" question where the answer is a date ("should I X on April 23", "best day this month to Y", "下周四怎么样"). Modes: single date, compare up to 5 dates, or scan a range up to 31 days. Returns score (0-100), verdict, per-layer year/month/day breakdown (alerts + dimension signals), element breakdown, adverse alerts. For multi-month windows use `intentions_ask_month`; for hour precision use `intentions_ask_hour`.

Input parameters:

- `birthInfo` (object): Optional override. If provided, all 6 fields required: { year, month, day, hour, minute, gender } — use null for unknown hour/minute/gender. Omit entirely to use the stored profile.
- `category` (string): Decision domain — tunes the analysis weighting. Default: general.
- `compareDates` (array): Up to 4 additional YYYY-MM-DD dates to compare against targetDate
- `dateRange` (object): Find best dates in range. Max 31 days — use ask_month for longer windows.
- `question` (string, required): The decision or action being considered
- `targetDate` (string): YYYY-MM-DD. Default: today

### `intentions_ask_hour` (~506 tokens)

Call when the user asks about timing within a specific day — best hour to act, morning vs afternoon, when during the day ("best time today to X", "morning or afternoon for Y", "几点去见面好"). Use for interview slots, meeting times, send/publish times, departure times, workout windows. Pro subscription required; on the free tier this returns a `subscription_required` error whose payload suggests `intentions_ask_day` for day-level analysis or `intentions_energy_chart` with period `weekly` / `yearly` for a visual overview (the caller LLM decides whether to retry). Modes: single (date+hour), compare up to 5 hour-pairs, or scan all 12 two-hour blocks of one day. Accepts any clock hour 0..23; internally mapped to the containing 2-hour block midpoint (0/2/4/…/22). 23:00–23:59 automatically rolls the effective day forward by one. Every output entry includes a `window { start, end }` local wall-clock span (`YYYY-MM-DDTHH:MM`, no timezone offset — interpret in the same frame as the input hour). Always cite this when presenting the time. Returns score, verdict, adverse alerts.

Input parameters:

- `bestInDay` (object): Find best hours within a single day. Each entry carries an explicit `window` span.
- `birthInfo` (object): Optional override. If provided, all 6 fields required: { year, month, day, hour, minute, gender } — use null for unknown hour/minute/gender. Omit entirely to use the stored profile.
- `category` (string): Decision domain — tunes the analysis weighting. Default: general.
- `compareHours` (array): Up to 4 additional (date, clock-hour 0..23) pairs to compare against targetDate+targetHour. Pairs that resolve to the same 2-hour block (e.g. hours 7 and 8 on the same date) are deduplicated — submit…
- `question` (string, required): The decision or action being considered
- `targetDate` (string): YYYY-MM-DD. Default: today (single mode only)
- `targetHour` (integer): Clock hour 0..23. Auto-rounded to the containing 2-hour block. 23:XX rolls the effective day forward by one.

### `intentions_ask_year` (~199 tokens)

Call when the user asks about a full calendar year as a whole ("how is 2026", "今年怎么样", "what's next year like overall"). Returns year-level score, verdict, adverse alerts, and element dimensions. For month precision use `intentions_ask_month`; for day use `intentions_ask_day`. Window: currentYear-1 to currentYear+1 only.

Input parameters:

- `birthInfo` (object): Optional override. If provided, all 6 fields required: { year, month, day, hour, minute, gender } — use null for unknown hour/minute/gender. Omit entirely to use the stored profile.
- `category` (string): Decision domain — tunes the analysis weighting. Default: general.
- `question` (string, required): The decision or action being considered
- `targetYear` (integer): YYYY. Default: current year. Allowed: currentYear-1 .. currentYear+1.

### `intentions_ask_month` (~280 tokens)

Call when the user asks at month granularity or wants the best month from a multi-month window ("how is next month", "best month in 2026 to X", "下个月适合吗"). Use for trip-month selection, launch months, content-calendar planning, quarterly/annual decisions. Modes: single month, compare up to 5 months, or scan up to 12 months (returns top 5). Returns month score, element breakdown, adverse alerts. For day precision near the 4th–6th of a month use `intentions_ask_day`; for hour precision use `intentions_ask_hour`.

Input parameters:

- `birthInfo` (object): Optional override. If provided, all 6 fields required: { year, month, day, hour, minute, gender } — use null for unknown hour/minute/gender. Omit entirely to use the stored profile.
- `category` (string): Decision domain — tunes the analysis weighting. Default: general.
- `compareMonths` (array): Up to 4 additional YYYY-MM months to compare against targetMonth
- `monthRange` (object): Find best months in range. Max 12 months. Inclusive on both ends.
- `question` (string, required): The decision or action being considered
- `targetMonth` (string): YYYY-MM. Default: current month

### `intentions_energy_chart` (~271 tokens)

Call when the user wants a visual overview rather than a narrative answer ("show me this week", "chart for today", "next 12 months", "看一下图"). Returns an ASCII chart: `hourly` = 12 two-hour blocks of one day, `weekly` = 7 days, `yearly` = 12 months. The `hourly` mode emits the same hour-resolution scores as `intentions_ask_hour` and is gated behind the Pro subscription on the same terms — on the free tier it returns a `subscription_required` error whose payload suggests `weekly` / `yearly` chart modes or `intentions_ask_day` as alternatives. `weekly` and `yearly` are always free.

Input parameters:

- `birthInfo` (object): Optional override. If provided, all 6 fields required: { year, month, day, hour, minute, gender } — use null for unknown hour/minute/gender. Omit to use the stored profile.
- `date` (string): YYYY-MM-DD. Default: today
- `period` (string, required): Which chart to render: `hourly` = 12 two-hour blocks of one day (Pro-gated), `weekly` = 7 days, `yearly` = 12 months.

### `intentions_set_birth_info` (~242 tokens)

Call once to register the user's birth date/time/gender. Each call is a complete replacement — all 6 fields must be supplied. For fields the user does not know or prefers not to share, pass `null` explicitly (e.g. `hour: null` for unknown birth time, `gender: null` for unspecified). To update just one field, first call `intentions_get_profile` to fetch the current values, merge the user's new input, then call this tool with the full merged payload. Identity-changing edits (year/month/day/hour/gender) are limited to 3 per calendar month; adding precision (e.g. filling in a previously-null hour) is always free. Returns the element profile.

Input parameters:

- `day` (integer, required): Birth day of month, 1–31.
- `gender` (string|null, required): null if unspecified
- `hour` (integer|null, required): null if unknown
- `minute` (integer|null, required): null if unknown; requires hour to also be non-null
- `month` (integer, required): Birth month, 1–12.
- `year` (integer, required): Birth year, 1920–2030.

### `intentions_get_profile` (~87 tokens)

Fetch the user's currently stored birth info. Use this before `intentions_set_birth_info` when updating an existing profile so you can send back a complete merged payload. Returns { hasProfile, birthInfo: { year, month, day, hour, minute, gender } | null } where any unknown field (e.g. unknown hour) is returned as `null`. No quota cost.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/intentions-me-intentions-mcp/mcp#diagnostics

## Score history

- 2026-08-04: 55
- 2026-08-03: 55
- 2026-08-02: 54
- 2026-08-01: 54
- 2026-07-31: 53
- 2026-07-30: 50
- 2026-07-29: 50
- 2026-07-28: 49
- 2026-07-27: 48
- 2026-07-26: 48

## Links

- Remote endpoint: https://mcp.intentions.me/mcp
- Authorisation metadata: https://mcp.intentions.me/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/intentions-me/intentions-mcp
- Website: https://www.intentions.me/
- Changelog RSS feed: https://verifymcp.io/servers/intentions-me-intentions-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/intentions-me-intentions-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/intentions-me-intentions-mcp/mcp