Skip to content

Intentions MCP Server

io.github.intentions-me/intentions-mcpintentions-mestreamable-httpv0.1.2Scanned

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

7 tools: 6 change things and 1 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

6 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Intentions MCP Server can do

The Intentions MCP Server is published by the GitHub account intentions-me. It has 7 tools. It can create or change data (6 tools: intentions_ask_day, intentions_ask_hour, intentions_ask_year, intentions_ask_month and 2 more), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

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

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 19, 2026, version 0.1.2.

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.

7 tools

Changes things 6Claude Code: ask
  • intentions_ask_dayCall when the user asks about timing a decision for a specific date, or wants to pick the best day from a multi-day window.1 finding

    Why it is in this group

    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "intentions_ask_day" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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. On the free tier a range must sit inside the past week and the week ahead; single and compared dates are free anywhere in the window. 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`.

    Annotations the server declares

    • title: Best day to act
    • readOnlyHint: true
    • openWorldHint: false
  • intentions_ask_hourCall 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", "几点去…1 finding

    Why it is in this group

    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "intentions_ask_hour" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Best hour to act
    • readOnlyHint: true
    • openWorldHint: false
  • intentions_ask_monthCall 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", "下个月适合吗").1 finding

    Why it is in this group

    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "intentions_ask_month" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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). Single and compared months are free; scanning a range is free inside last year and this year, and Pro further out. 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`.

    Annotations the server declares

    • title: Best month to act
    • readOnlyHint: true
    • openWorldHint: false
  • intentions_ask_yearCall when the user asks about a full calendar year as a whole ("how is 2026", "今年怎么样", "what's next year like overall").1 finding

    Why it is in this group

    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "intentions_ask_year" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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-3 to currentYear+3 only.

    Annotations the server declares

    • title: Year outlook
    • readOnlyHint: true
    • openWorldHint: false
  • intentions_energy_chartCall when the user wants a visual overview rather than a narrative answer ("show me this week", "chart for today", "next 12 months", "看一下图").1 finding

    Why it is in this group

    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "intentions_energy_chart" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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 Pro: on the free tier it returns a `subscription_required` error whose payload suggests alternatives. `weekly` is free for the past week and the week ahead (omit `date` for this week), and `yearly` for the months of last year and this year (omit `date` for this year); further out both are Pro too.

    Annotations the server declares

    • title: Energy chart
    • readOnlyHint: true
    • openWorldHint: false
  • intentions_set_birth_infoCall once to register the user's birth date/time/gender.No findings

    Why it is in this group

    • The name "intentions_set_birth_info" says "set": a word for a change.
    Description, as the server wrote it
    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. Changes to the date, gender or a known hour (including setting a known hour back to null) are limited to 3 per calendar month (UTC); filling in a previously-null hour, or the minute, is always free. `intentions_get_profile` returns how many are left. Always pass `birthPlace` (the city of birth, e.g. "Portland, Maine") when the user gives it: readings then use the real moment of birth there, daylight saving included. Omit it only to keep the stored one; changing it is free. If the call fails with birth_time_needs_confirming, the clocks changed over that time at the birthplace: ask the user which it was and call again with birthTimeFold (0 = the earlier, 1 = the later). Returns the element profile.

    Annotations the server declares

    • title: Set birth profile
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • intentions_get_profileFetch the user's currently stored birth info.No findings

    Why it is in this group

    • The name "intentions_get_profile" says "get": a word for reading.
    Description, as the server wrote it
    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, profileChanges: { remaining, resetsAt } | null, birthPlace: string | null, next? } where `next`, when present, says what to ask the user (e.g. their city of birth). Any unknown birth field (e.g. unknown hour) is returned as `null`. `profileChanges` is how many changes to the date, gender or a known hour are left this calendar month (UTC) and the ISO instant they come back; if `remaining` is 0, tell the user before attempting such a change. No quota cost.

    Annotations the server declares

    • title: Get birth profile
    • readOnlyHint: true
    • openWorldHint: false

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 private-data or untrusted-input or outbound.

Reads private data0
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.

Tools listed without sign-in

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

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-06-18
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
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.intentions.me/mcp: tools/list returned 7 tools to an anonymous client, including intentions_ask_day (write), intentions_ask_hour (write), intentions_ask_year (write), intentions_ask_month (write), intentions_energy_chart (write) and 1 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

5 warn
  • The server marks "intentions_ask_day" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.

    What this check looks for
  • The server marks "intentions_ask_hour" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.

    What this check looks for
  • The server marks "intentions_ask_year" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.

    What this check looks for
  • The server marks "intentions_ask_month" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.

    What this check looks for
  • The server marks "intentions_energy_chart" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.

    What this check looks for

History

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

  1. Tools2 changed.~2 changedView diff

Install

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

claude mcp add --transport http intentions https://mcp.intentions.me/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http intentions https://mcp.intentions.me/mcp --header 'Authorization: <your-authorization>'

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__intentions__intentions_get_profile"
    ],
    "ask": [
      "mcp__intentions__intentions_ask_day",
      "mcp__intentions__intentions_ask_hour",
      "mcp__intentions__intentions_ask_year",
      "mcp__intentions__intentions_ask_month",
      "mcp__intentions__intentions_energy_chart",
      "mcp__intentions__intentions_set_birth_info"
    ],
    "deny": []
  }
}

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 intentions. Review it before you use it.

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.github.intentions-me/intentions-mcp/verify?hash=7892f0508350adc88afc92d3cfa90c0b570a900089946b60d5d6256710711997" | jq -e '.changed == false'

Pinned hash 7892f0508350, from Nov 19, 2026, 21:18 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.intentions-me/intentions-mcp/changes.xml

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

Badge

Anlyon Radar badge for io.github.intentions-me/intentions-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.intentions-me/intentions-mcp.svg)](https://radar.anlyon.com/servers/io.github.intentions-me/intentions-mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:36 UTC.

Intentions MCP Server: questions and answers

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

Is the Intentions MCP Server safe?

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

Can the Intentions MCP Server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Intentions MCP Server 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 Intentions MCP Server have?

7 tools: 6 write, 1 read. intentions_ask_day, intentions_ask_hour, intentions_ask_year, intentions_ask_month, intentions_energy_chart, intentions_set_birth_info and intentions_get_profile.

Does the Intentions MCP Server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Intentions MCP Server send data to outside services?

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

Has the Intentions MCP Server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 5, 2026. Every change is on this page and in its Atom feed.