Framezone
REMOTE · FRAMEZONE.APP
Your life dashboard for AI: tasks, habits, goals, budgets, workouts, nutrition, journal, notes.
Available components
Last scanned (1 hour ago)
Scores higher than 98% of remote servers
Reachable. Last reached 17 Oct 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 Security94
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 7299 tokens (~117/item across 62 items; 62 tools + 0 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 Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 63 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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 60. That category is still filling its 30-day observation window: 16 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.
- 10 Oct 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.
- 9 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 50. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 40. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 1 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.
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 17 Oct 2026 · Probed https://framezone.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=framezone.app | CN=YE2,O=Let's Encrypt,C=US | 20 Sept 2026 | 19 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6dd4f3829227dc0d4347baa7953bf5cef16 |
| SANs: *.framezone.app, framezone.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of framezone.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| framezone.app. | 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 realm="mcp", resource_metadata="https://framezone.app/.well-known/oauth-protected-resource/mcp"
Bearer realm="mcp", resource_metadata="https://framezone.app/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
Protected resource metadata
| Document | https://framezone.app/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://framezone.app/mcp |
| Authorisation server | https://framezone.app/mcp |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://framezone.app/mcp | Verified | 200 | |
| http (plaintext) | http://framezone.app/mcp | HTTPS enforced | 301 | https://framezone.app/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 →
log_workout Log workout ~172
Log a workout session with type, duration, calories, and heart rate.
| Name | Type | Req | Description |
|---|---|---|---|
| active_calories | integer | – | Active calories (Apple Watch) |
| avg_hr | integer | – | Average heart rate |
| calories | integer | – | Total calories burned |
| duration_minutes | integer | – | Duration in minutes |
| ended_at | string | – | Session end (Y-m-d H:i:s) |
| location | string | – | Where the session happened |
| max_hr | integer | – | Max heart rate |
| min_hr | integer | – | Min heart rate |
| notes | string | – | Notes |
| started_at | string | – | Session start (Y-m-d H:i:s) |
| type | string | yes | Workout type |
| workout_date | string | – | Workout date (Y-m-d, defaults to today) |
No output schema declared.
No examples provided.
log_workout_sets Log workout sets ~249
Add exercises and sets to a workout. Accepts gym shorthand ("lateral raise 5kg 4x12", "2min rowing machine") and creates the workout for that date if none exists.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_duplicates | boolean | – | Write blocks that already exist on that date with the same load and set count. Off by default — a repeated call is far more often a re-send than a second round. |
| duration_minutes | integer | – | Session duration in minutes |
| notes | string | – | Notes |
| sets_text | string | yes | One movement per line. Understands "4x12", "40kg", "2dk"/"90sn", "3 set". Example: "lateral raise 5kg 4x12\nincline bench press machine 40kg 4x8" |
| type | string | – | Workout type. Sets go to the session of this type on that date; a new session is created when there is none. |
| workout_date | string | – | Date (Y-m-d, defaults to today) |
| workout_id | integer | – | Add to this session. Needed when the date holds more than one session of the same type. |
No output schema declared.
No examples provided.
search Search ~42
Search the user's Framezone data by keyword: tasks, projects, notes, bookmarks, books and goals.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search query (min 2 characters) |
No output schema declared.
No examples provided.
update_book Update book ~107
Update a book: change status, rating, notes, or update reading progress (current page).
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | New author |
| book_id | integer | yes | Book ID |
| current_page | integer | – | Current page (updates reading progress) |
| notes | string | – | Personal notes |
| rating | integer | – | Rating 1-5 |
| status | string | – | New status |
| tags | array | – | Tags |
| title | string | – | New title |
No output schema declared.
No examples provided.
update_contact Update contact ~181
Update a contact. Use mark_contacted=true to record a check-in with today's date.
| Name | Type | Req | Description |
|---|---|---|---|
| birthday | string | – | Birthday (Y-m-d). Year unknown: use 1604 as the year |
| company | string | – | Company |
| contact_frequency_days | integer | – | Contact reminder interval in days |
| string | – | ||
| first_name | string | – | First name |
| id | integer | yes | Contact ID |
| is_favorite | boolean | – | Favorite status |
| last_name | string | – | Last name (empty string clears it) |
| mark_contacted | boolean | – | Mark as contacted today |
| name | string | – | Full name; split into first and last name at the first space |
| notes | string | – | Notes |
| phone | string | – | Phone |
| relationship | string | – | Type |
No output schema declared.
No examples provided.
update_daily_entry Update daily entry ~133
Update the daily journal: set mood (1-5), energy (1-5), focus text, morning/evening notes.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Date to update (Y-m-d, defaults to today) |
| energy | integer | – | Energy rating 1-5 |
| evening_note | string | – | Evening reflection note |
| focus_completed | boolean | – | Whether the focus was achieved |
| focus_text | string | – | Today's focus/intention text (max 255 characters) |
| mood | integer | – | Mood rating 1-5 |
| morning_note | string | – | Morning journal note |
No output schema declared.
No examples provided.
update_goal Update goal ~219
Update a goal: change status, progress, toggle milestones, or add a progress note.
| Name | Type | Req | Description |
|---|---|---|---|
| current_value | number | – | Current value (for numeric goals, >= 0) |
| description | string | – | New description |
| goal_id | integer | yes | Goal ID |
| note | string | – | Progress update note (saved in goal timeline) |
| priority | integer | – | Priority: 1=high, 2=medium, 3=low |
| start_value | number | – | Value the goal started from; progress is measured from it (use for goals that go down, e.g. 90 -> 80 kg) |
| status | string | – | New status |
| target_date | string | – | New target date (Y-m-d) |
| target_value_num | number | – | Target value (numeric and habit goals) |
| title | string | – | New title |
| toggle_milestone | integer | – | Toggle milestone by index (0-based). Ticking the last open one completes the goal; unticking reopens it. |
No output schema declared.
No examples provided.
update_habit Update habit ~181
Update an existing habit. Only provided fields are changed.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Enable or disable the habit |
| color | string | – | Color as #rrggbb, e.g. #10AC84 |
| habit_id | integer | yes | ID of the habit to update |
| icon | string | – | Lucide icon name (lowercase, dashes), e.g. book-open |
| name | string | – | New habit name |
| target_duration | integer | – | New target duration in minutes (5-480) |
| target_value | integer | – | New target count value |
| time_of_day | string | – | When during the day |
| times_per_week | integer | – | New times per week target (1-7) |
| tracking_type | string | – | New tracking type |
| unit | string | – | New unit label |
No output schema declared.
No examples provided.
update_project Update project ~132
Update a project: change name, tier, status, goal link, or target date.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | – | Color hex |
| description | string | – | New description |
| goal_id | integer | – | Link to goal by ID (0 to unlink) |
| icon | string | – | Lucide icon name |
| name | string | – | New name |
| project_id | integer | yes | Project ID |
| status | string | – | New status |
| target_date | string | – | Target date (Y-m-d) |
| tier | string | – | New tier |
| url | string | – | Project URL |
No output schema declared.
No examples provided.
update_task Update task ~125
Update an existing task. Only provided fields are changed.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | New description |
| due_date | string | – | New due date (Y-m-d) |
| is_top3 | boolean | – | Set Top 3 status |
| priority | integer | – | Priority: 1=high, 2=medium, 3=low |
| project_id | integer | – | Assign to project by ID |
| status | string | – | New status |
| task_id | integer | yes | ID of the task to update |
| title | string | – | New title |
No output schema declared.
No examples provided.
update_wishlist_item Update wishlist item ~204
Update a wishlist item — mark it purchased or cancelled, change priority, price or notes. Purchased and cancelled items drop out of the active list.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category |
| currency | string | – | 3-letter currency code of the prices, e.g. GBP |
| item_id | integer | yes | Wishlist item ID |
| name | string | – | New name |
| notes | string | – | Notes — reasoning, alternatives considered, purchase trigger |
| price_max | number | – | Upper price estimate |
| price_min | number | – | Lower price estimate |
| priority | string | – | high | medium | low | waiting (waiting = wanted but gated on a trigger) |
| purchased_at | string | – | Purchase date (Y-m-d). Defaults to today when status becomes purchased. |
| status | string | – | pending = still wanted · purchased = bought · cancelled = no longer wanted |
| url | string | – | Product URL (http or https) |
No output schema declared.
No examples provided.
weekly_summary Weekly summary ~51
Get a comprehensive weekly review: tasks, habits, mood/energy, portfolio, books, focus time.
| Name | Type | Req | Description |
|---|---|---|---|
| week | string | – | ISO week format like "2026-W13" (defaults to current week) |
No output schema declared.
No examples provided.
How do I install the Framezone MCP server?
Framezone is a hosted endpoint at https://framezone.app/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 · framezone.app
claude mcp add --transport http app-framezone-framezone 'https://framezone.app/mcp'
What is the Framezone MCP server?
Framezone is an MCP server listed in the public MCP registry as app.framezone/framezone. Your life dashboard for AI: tasks, habits, goals, budgets, workouts, nutrition, journal, notes. This page covers its hosted endpoint (https://framezone.app/mcp).
Is the Framezone MCP server safe to use?
Framezone scores 90 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 Framezone MCP server expose?
Framezone exposes 62 tools: list_tasks, create_task, update_task, complete_task, delete_task, and 57 more. Their descriptions and schemas cost roughly 6,269 tokens of context every time the server is loaded.
Does the Framezone MCP server require authentication?
Yes. Framezone 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 Framezone MCP server still maintained?
Framezone is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.