AimYear
REMOTE · MCP.AIMYEAR.COM
Accountability partner in your agent: one yearly aim, one main step a day, a timer your agent runs.
Available components
Last scanned (10 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Productivity and Notes
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 → Why this is hard to score →
Endpoint Security89
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 5970 tokens (~112/item across 53 items; 52 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 52% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 54 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 0
- Server version: 0.11.1 → 0.11.2 functional
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- New tool “set_tracks”, which the server declares destructive security
- Tool “edit_milestone” rewrote its description, which is the text the model reads security
- Tool “get_path” rewrote its description, which is the text the model reads security
- Tool “next_steps” rewrote its description, which is the text the model reads security
- Tool “set_milestones” rewrote its description, which is the text the model reads security
- The server now declares the “resources” capability functional
- New prompt “aim” functional
- New resource “aim-skill” functional
- Server version: 0.9.0 → 0.11.1 functional
- “edit_milestone” added an optional parameter “trackId” cosmetic
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- New tool “delete_agent”, which the server declares destructive security
- New tool “delete_social_account”, which the server declares destructive security
- Tool “get_settings” rewrote its description, which is the text the model reads security
- Tool “set_settings” rewrote its description, which is the text the model reads security
- Schema quality: 4795 → 5633 ▼ functional
- Server version: 0.7.0 → 0.9.0 functional
- New tool “add_post” functional
- New tool “add_social_account” functional
- New tool “get_insights” functional
- New tool “get_post_draft” functional
- New tool “list_agents” functional
- New tool “list_social_accounts” functional
- “set_settings” added an optional parameter “post_to” cosmetic
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 5 Nov 2026 · Probed https://mcp.aimyear.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.aimyear.com | CN=WR3,O=Google Trust Services,C=US | 12 Oct 2026 | 10 Jan 2027 | RSA 2048 | SHA256-RSA | 506b140da0ddb53c0a0c70317f0e9b20 |
| SANs: mcp.aimyear.com | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.aimyear.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| aimyear.com. | 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 resource_metadata="https://mcp.aimyear.com/.well-known/oauth-protected-resource/mcp"
Bearer resource_metadata="https://mcp.aimyear.com/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://mcp.aimyear.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.aimyear.com/mcp |
| Authorisation server | https://mcp.aimyear.com/ |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.aimyear.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.aimyear.com/mcp | HTTPS enforced | 302 | https://mcp.aimyear.com/mcp |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
summarize_day Summarize day ~47
Full summary of a day: wall and attention minutes per area, classification and lever, sessions, gaps, overlaps, overrides.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | YYYY-MM-DD in the user's timezone |
No output schema declared.
No examples provided.
summarize_week Summarize week ~57
A week, Monday to Sunday (to today for the current week): main-step days, goal share, hard share, area balance, overrides, streak, milestone pace.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | any day of the week, default today |
No output schema declared.
No examples provided.
How do I install the AimYear MCP server?
AimYear is a hosted endpoint at https://mcp.aimyear.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.aimyear.com
claude mcp add --transport http yahhi-aimyear-mcp 'https://mcp.aimyear.com/mcp'
What is the AimYear MCP server?
AimYear is an MCP server listed in the public MCP registry as io.github.Yahhi/aimyear-mcp. Accountability partner in your agent: one yearly aim, one main step a day, a timer your agent runs. This page covers its hosted endpoint (https://mcp.aimyear.com/mcp).
Is the AimYear MCP server safe to use?
AimYear scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AimYear MCP server expose?
AimYear exposes 52 tools: get_goal, check_goal_draft, set_goal, record_progress, set_levers, and 47 more. Their descriptions and schemas cost roughly 5,411 tokens of context every time the server is loaded.
Does the AimYear MCP server require authentication?
Yes. AimYear asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the AimYear MCP server still maintained?
AimYear is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.