Skip to content

MCP servers › io.github.Yahhi › aimyear-mcp

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.Yahhi/aimyear-mcp

Accountability partner in your agent: one yearly aim, one main step a day, a timer your agent runs. — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-10-23Topic: productivity-and-docs · AI-classifiedPricing: freemium · AI-classifiedversion 0.4.2TypeScriptstreamable HTTP51 tools

Summary

io.github.Yahhi/aimyear-mcp is a remote MCP server listed in the official MCP registry at version 0.4.2. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 51 tools, 0 resources and 2 prompts.

Record checks

4 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Sign-in
none needed to open a session
Repository
public
Tools
51
Described as changing data
30 of 51 toolsAI-classified
Mainly works on
files and code on the machine it runs onAI-classified
Topic
productivity-and-docsAI-classified
Pricing
freemiumAI-classified
Last tested
2026-10-23

Add to your client

Observed fact

This server accepted a session without any credential and lists 26 tools whose name or declaration suggests they change data (set_goal, set_levers, set_projects, set_milestones, edit_milestone and 21 more). That is our reading of the names; we did not call them. Source: our connection, 2026-10-23.

Worth knowing before you connect it

  • 30 tools are described as changing something (set_goal, record_progress, set_levers, …): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-23
Mode
read-only (no tool calls)
Latest version
0.4.2, published 2026-10-18 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-18 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-23
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.4.2 (published 2026-10-18).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory
51tools
0resources
2prompts

What it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on.

30 of 51 tools are described as changing something (creating, editing, deleting, sending or running).

  • get_goalon 5 other serversreads or searches

    “The one yearly goal: kind (count or done), metric, starting value, current value, target, deadline, progress, levers (hard/comfortable) and other projects.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • check_goal_draft

    “Check a goal that is not saved yet against the rubric (a countable metric with value today and target, or a done-or-not result you can check yes or no; deadline within 12 months; pace per week).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    6 inputs
    • kindstring“count (default): a number from baseline to target, e.g.”
    • titlestring
    • metricstring“the one number and its unit, e.g.”
    • baselinenumber“value today”
    • targetnumber
    • deadlinestring“YYYY-MM-DD in the user's timezone”
  • set_goalon 2 other serverscreates or changes datadescribed as changing data

    “Save the yearly goal, or replace it with the next one.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    8 inputs, 2 required
    • kindstring“count (default): a number from baseline to target, e.g.”
    • titlestringrequired
    • whystring
    • metricstring“required for kind count”
    • baselinenumber“value today; required for kind count”
    • targetnumber“required for kind count”
    • deadlinestringrequired“YYYY-MM-DD in the user's timezone”
    • areastring“default money”
  • record_progresscreates or changes datadescribed as changing data

    “Record the current value of the goal metric ("I now have 4 customers"), or of a countable milestone when milestoneId is given ("I have talked to 7 people").”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    3 inputs, 1 required
    • valuenumberrequired
    • datestring“YYYY-MM-DD in the user's timezone”
    • milestoneIdstring“a countable milestone instead of the goal”
  • set_leverscreates or changes datadescribed as changing data

    “Replace the list of levers: the recurring kinds of goal work.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • leversarrayrequired
  • set_projectson 1 other servercreates or changes datadescribed as changing data

    “Replace the list of other projects (paid work, other products, life routines), so their sessions count as other work or life, not goal work.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • projectsarrayrequired
  • get_pathon 1 other serverreads or searches

    “Milestones with kind, progress (recorded value or steps done), pace (ahead/on_pace/behind) and their steps.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • set_milestonescreates or changes datadescribed as changing data

    “Replace the list of 2–6 ordered milestones under the goal, each countable (metric and target) or measured by its steps, with a due date before the goal deadline.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • milestonesarrayrequired
  • edit_milestonecreates or changes datadescribed as changing data

    “Change one milestone: title, kind (count or steps), metric, target, due date or status.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    7 inputs, 1 required
    • milestoneIdstringrequired
    • titlestring
    • kindstring“count: progress is a recorded value against target ("talk to 20 people"); steps: progress is steps done ("implement the onboarding flow"), no metric needed.”
    • metricstring
    • targetnumber
    • duestring“YYYY-MM-DD in the user's timezone”
    • statusstring
  • add_stepscreates or changes datadescribed as changing data

    “Add concrete steps to a milestone.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    3 inputs, 2 required
    • milestoneIdstringrequired
    • stepsarrayrequired
    • op_idstring“for apps replaying queued requests: an id the app minted before its first attempt and reuses on retries, so the write is applied once and a retry gets the firs…”
  • edit_stepcreates or changes datadescribed as changing data

    “Change one step: title, status (todo/doing/done), order, lever, estimate.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    6 inputs, 1 required
    • stepIdstringrequired
    • titlestring
    • statusstring
    • orderinteger
    • leverIdstring
    • estimateMininteger
  • delete_stepdeletesdescribed as changing data

    “Delete one step from the path.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    1 input, 1 required
    • stepIdstringrequired
Show 39 more tools
  • next_stepson 1 other serverreads or searches

    “Open steps of the current milestone, hard-lever steps first: the candidates for today's main step.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • countinteger
  • get_commitmentson 2 other serversreads or searches

    “Recurring weekly time: commitments (school runs, training, classes), overhead (sleep, meals) and focus windows.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • set_commitmentscreates or changes datadescribed as changing data

    “Replace the list of recurring weekly commitments.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • commitmentsarrayrequired
  • get_capacityon 1 other serverreads or searches

    “Weekly time budget out of 168 hours: overhead, hours committed per area, focus windows, and what is still unaccounted for.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • get_planning_contexton 2 other serversreads or searches

    “Everything needed to plan a day: goal and pace, next_steps, yesterday's summary and undone items, week balance, days since a hard lever.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • datestring“YYYY-MM-DD in the user's timezone”
  • get_planon 26 other serversreads or searches

    “The plan for a day (default today).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • datestring“YYYY-MM-DD in the user's timezone”
  • set_planon 2 other serverscreates or changes datadescribed as changing data

    “Replace the plan for a day.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    2 inputs, 1 required
    • datestring“YYYY-MM-DD in the user's timezone”
    • itemsarrayrequired
  • edit_plan_itemcreates or changes datadescribed as changing data

    “Change one plan item: mark it done or not done, rename it, change its estimate, area or links, or make it the main step.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    12 inputs, 1 required
    • itemIdstringrequired
    • datestring“YYYY-MM-DD in the user's timezone”
    • doneboolean
    • levelstring“routines only; sets done unless done is given”
    • countinteger“units done in this tick, for a routine with perWeek; above 0 ticks it, 0 unticks it”
    • titlestring
    • areastring
    • projectIdstring
    • leverIdstring
    • stepIdstring
    • isMainStepboolean
    • estimateMininteger
  • get_routinesreads or searches

    “Routines: small steps that repeat on fixed weekdays, e.g.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • set_routinescreates or changes datadescribed as changing data

    “Replace the list of routines: small steps that repeat on fixed weekdays.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • routinesarrayrequired
  • delete_plan_itemdeletesdescribed as changing data

    “Remove one item from a day's plan.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    2 inputs, 1 required
    • itemIdstringrequired
    • datestring“YYYY-MM-DD in the user's timezone”
  • set_day_modecreates or changes datadescribed as changing data

    “Tracking for a day: full (everything recorded, the default) or off (timer and reminders only, nothing stored, no plan required).”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • datestring“YYYY-MM-DD in the user's timezone”
    • modestringrequired
  • get_nowon 1 other serverreads or searches

    “What is happening now: running sessions with attention shares, the timer, today's main step, today's minutes, the streak and a one-line nudge.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • start_sessionon 16 other serverscreates or changes datadescribed as changing data

    “Start a session of work and, if none is running, the timer.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    15 inputs, 1 required
    • taskstringrequired“what you are about to do, specific”
    • areastring“default work”
    • projectIdstring
    • leverIdstring
    • stepIdstring“path step id”
    • itemIdstring“plan item id”
    • weightnumber“attention weight vs other sessions at the same time, default 1”
    • exclusiveboolean“true: nothing else was happening then”
    • directionstring“up (default) counts elapsed time and runs until stopped, with a stand-up reminder every workMin; down is a fixed timebox, for a break”
    • minutesinteger“length for a down timer, or the stand-up interval for an up timer”
    • workplacestring
    • overrideboolean“true only after the user confirmed past a stop”
    • op_idstring“for apps replaying queued requests: an id the app minted before its first attempt and reuses on retries, so the write is applied once and a retry gets the firs…”
    • start_atstring“when the work began as ISO 8601 with offset, e.g.”
    • session_idstring“for apps: the session id the app minted itself.”
  • add_noteon 22 other serverscreates or changes datadescribed as changing data

    “Add a one-line note to a running session (this connection's, or session_id).”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    3 inputs, 1 required
    • notestringrequired
    • session_idstring“from get_now; required with op_id”
    • op_idstring“for apps replaying queued requests: an id the app minted before its first attempt and reuses on retries, so the write is applied once and a retry gets the firs…”
  • split_attentioncreates or changes datadescribed as changing data

    “Set attention weights of the running sessions at once, e.g.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • sharesobjectrequired
  • stop_sessionon 3 other serverscreates or changes datadescribed as changing data

    “Stop a running session with a summary and outcome.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    6 inputs, 2 required
    • summarystringrequired
    • outcomestringrequired
    • session_idstring“from get_now; required with op_id or end_at”
    • attention_sharenumber“corrects the share in hindsight”
    • end_atstring“when the work ended as ISO 8601 with offset, e.g.”
    • op_idstring“for apps replaying queued requests: an id the app minted before its first attempt and reuses on retries, so the write is applied once and a retry gets the firs…”
  • stop_timeron 2 other serversdeletesdescribed as changing data

    “Stop the timer ("pause", "stop", "stand up") and every running session with it.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    2 inputs
    • summarystring
    • outcomestring“default partial”
  • add_sessionon 1 other servercreates or changes datadescribed as changing data

    “Add past time that was not timed: minutes (ending now, or at end), or start+end as HH:MM on date.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    13 inputs, 1 required
    • taskstringrequired
    • minutesinteger
    • startstring“HH:MM local time”
    • endstring“HH:MM local time”
    • datestring“YYYY-MM-DD in the user's timezone”
    • areastring“default work”
    • projectIdstring
    • leverIdstring
    • stepIdstring“path step id”
    • itemIdstring“plan item id”
    • weightnumber“attention weight vs other sessions at the same time, default 1”
    • exclusiveboolean“true: nothing else was happening then”
    • op_idstring“for apps replaying queued requests: an id the app minted before its first attempt and reuses on retries, so the write is applied once and a retry gets the firs…”
  • edit_sessionon 2 other serverscreates or changes datadescribed as changing data

    “Fix a session, running or finished: start and end (HH:MM on date; an end before the start means it ran past midnight), task, area, project, lever, step, plan item, summary, outcome, attention share, …”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    15 inputs, 1 required
    • session_idstringrequired
    • datestring“local date of start and end; default the session's own date”
    • startstring“HH:MM local time”
    • endstring“HH:MM local time”
    • taskstring
    • areastring“default work”
    • projectIdstring
    • leverIdstring
    • stepIdstring“path step id”
    • itemIdstring“plan item id”
    • weightnumber“attention weight vs other sessions at the same time, default 1”
    • exclusiveboolean“true: nothing else was happening then”
    • summarystring
    • outcomestring
    • attention_sharenumber“share of the session's wall time that was real attention”
  • delete_sessionon 7 other serversdeletesdescribed as changing data

    “Delete a session, running or finished, so it no longer counts.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    2 inputs
    • session_idstring“required with op_id”
    • op_idstring“for apps replaying queued requests: an id the app minted before its first attempt and reuses on retries, so the write is applied once and a retry gets the firs…”
  • list_sessionson 47 other serversreads or searches

    “Sessions in a date range (default the last 7 days), with ids, optionally filtered by area or project.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs
    • fromstring“YYYY-MM-DD in the user's timezone”
    • tostring“YYYY-MM-DD in the user's timezone”
    • areastring
    • projectIdstring
  • find_gapson 1 other serverreads or searches

    “Untimed stretches of 20+ minutes between the first and last session of a day.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • datestring“YYYY-MM-DD in the user's timezone”
  • summarize_dayreads or searches

    “Full summary of a day: wall and attention minutes per area, classification and lever, sessions, gaps, overlaps, overrides.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • datestring“YYYY-MM-DD in the user's timezone”
  • summarize_weekreads or searches

    “A week, Monday to Sunday (to today for the current week): main-step days, goal share, hard share, area balance, overrides, streak, milestone pace.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • datestring“any day of the week, default today”
  • get_insightson 11 other serversreads or searches

    “Week (the last 7 days) or month (the last 30 days) ending on to (default today): minutes per day on the aim, other work and life; hard vs comfortable share of aim time; an hour × weekday heatmap of a…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • rangestring“default week”
    • tostring“last day, default today”
  • find_leaksreads or searches

    “Where time leaks: comfortable goal work while the main step waited, overrides, unplanned work, gaps, switching, missed main steps, days without a plan.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • fromstring“YYYY-MM-DD in the user's timezone”
    • tostring“YYYY-MM-DD in the user's timezone”
  • get_settingson 9 other serversreads or searches

    “Timezone, where reminders go (desktop or mobile), timer settings, and which networks get progress posts (post_to).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • set_settingscreates or changes datadescribed as changing data

    “Change any of: timezone (IANA name, e.g.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    8 inputs
    • timezonestring
    • workplacestring
    • workMininteger
    • breakMininteger
    • longBreakEveryinteger
    • longBreakMininteger
    • standupboolean
    • post_toarray“which connected networks get the day's progress post (the app sets it); [] for none”
  • add_devicecreates or changes datadescribed as changing data

    “Register a device token so server reminders (stand up, break over) can reach it.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    3 inputs, 2 required
    • tokenstringrequired
    • platformstringrequired
    • labelstring
  • list_deviceson 32 other serversreads or searches

    “Which devices can receive reminders, and when each was last seen.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • delete_deviceon 2 other serversdeletesdescribed as changing data

    “Remove a device so it stops receiving reminders.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    1 input, 1 required
    • tokenstringrequired
  • list_agentson 71 other serversreads or searches

    “Agents connected to this AimYear account (Claude, ChatGPT, Claude Code, the AimYear app…): name, client_id, when it connected and when it was last active.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • delete_agenton 8 other serversdeletesdescribed as changing data

    “Disconnect one agent: its sign-in for this account is deleted and it can no longer read or change anything until it connects again.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    1 input, 1 required
    • client_idstringrequired
  • add_social_accountcreates or changes datadescribed as changing data

    “Connect WIP (wip.co) or Bluesky so AimYear can post the day's progress there when the user says Post (Pro).”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world yes

    4 inputs, 1 required
    • networkstringrequired
    • api_keystring“WIP only”
    • handlestring“Bluesky only, e.g.”
    • app_passwordstring“Bluesky only: xxxx-xxxx-xxxx-xxxx”
  • list_social_accountson 1 other serverreads or searches

    “Connected networks (handle, since when), which of them get progress posts, and whether the user has Pro.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • delete_social_accountdeletesdescribed as changing data

    “Disconnect a network and delete its saved login.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world no

    1 input, 1 required
    • networkstringrequired
  • get_post_draftreads or searches

    “The day's progress post drafted from the record (aim and progress, main step done or not, minutes on the aim and on hard work, routines, comebacks), at most 300 characters, ending with aimyear.com; a…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input
    • datestring“YYYY-MM-DD in the user's timezone”
  • add_poston 1 other serversends messagesdescribed as changing data

    “Post the day's progress, only after the user explicitly said to post.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world yes

    3 inputs
    • datestring“YYYY-MM-DD in the user's timezone”
    • textstring
    • networksarray“default: the networks chosen in settings”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does
100% of 51 tools
Says what it returns
48% of 50 tools
States limits, defaults or errors
4% of 49 tools
Says when to use it
15% of 13 tools
Items covered per tool
1.9 of 4 on average

Counted from the listing

Parameters with a description
52% of 150
Tools with a description
100% of 51
Typical description length
217 characters

The tool set

Counted from the listing

Tools
51
Size of the list
about 11,410 tokens for an agent to load (characters ÷ 4)
Naming
51 of 51 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 51 of 51 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://mcp.aimyear.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "aimyear-mcp": {
      "url": "https://mcp.aimyear.com/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "aimyear-mcp": {
      "type": "http",
      "url": "https://mcp.aimyear.com/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"aimyear-mcp","type":"http","url":"https://mcp.aimyear.com/mcp"}'
Claude Code
claude mcp add --transport http aimyear-mcp https://mcp.aimyear.com/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.aimyear.com/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint mcp.aimyear.com/mcpSession openedmatchesour test · 2026-10-23
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-23
Repository github.com/Yahhi/aimyear-mcpOpens publiclymatchesapi.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.Yahhi
GitHub owner
a personal account (Yahhi)
Repository
github.com/Yahhi/aimyear-mcp
Stars
0
Repository age
31–90 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.Yahhi/aimyear-mcp

Answered from the data above

Is io.github.Yahhi/aimyear-mcp safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. 30 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Is io.github.Yahhi/aimyear-mcp free to use?

Its website (aimyear.com/) describes a freemium pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.

Does io.github.Yahhi/aimyear-mcp need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.github.Yahhi/aimyear-mcp been security tested?

Partly. 5 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

What can io.github.Yahhi/aimyear-mcp do?

It lists 51 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, delete and send messages. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.Yahhi/aimyear-mcp change or delete data?

30 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.Yahhi/aimyear-mcp publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of io.github.Yahhi/aimyear-mcp?

In github.com/Yahhi/aimyear-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

Active servers whose topic is also “productivity-and-docs” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: exercised
  13. Fake assistant turns: exercised
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

5 exercised11 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 5 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 5
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.exercised
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 11
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 2
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,240 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 51 tools, 0 resources, 2 prompts.
  4. 5,233 msFinished: 5 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
AI-classified · 2026-10-23
Pricing modelAI-classified
freemium
read from aimyear.com/ · 2026-10-23

“Connect your agent: free”

Programming language
api.github.com · 2026-10-23
Hosting type
registry · 2026-10-23
MCP capability
prompts, tools
our test · 2026-10-23
Transport
streamable HTTP
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
registry · 2026-10-23
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: a personal account · repository age: 31–90 days · stars: 0–9
api.github.com · 2026-10-23
Maintenance
api.github.com · 2026-10-23
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.Yahhi/aimyear-mcp: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.Yahhi/aimyear-mcp

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.Yahhi/aimyear-mcp)](https://protocolprobe.com/mcp/servers/io.github.Yahhi/aimyear-mcp)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology