Home / MCP registry index / io.github.Yahhi/aimyear-mcp
AimYear
io.github.Yahhi/aimyear-mcp in the official MCP registry.
Endpoint https://mcp.aimyear.com/mcp. Source: github.com/Yahhi/aimyear-mcp.
The registry describes it as: Accountability partner in your agent: one yearly aim, one main step a day, a timer your agent runs.
We read its 43 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
get_goal check_goal_draft set_goal record_progress set_levers set_projects get_path set_milestones edit_milestone add_steps edit_step delete_step next_steps get_commitments set_commitments get_capacity get_planning_context get_plan set_plan edit_plan_item get_routines set_routines delete_plan_item set_day_mode get_now start_session add_note split_attention stop_session stop_timer add_session edit_session delete_session list_sessions find_gaps summarize_day summarize_week find_leaks get_settings set_settings add_device list_devices delete_device
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-yahhi-aimyear-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.