Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

FutureSelf Vision Board Planner

REMOTE · FUTURESELF-AI.COM

Plan a vision board: ideas for a goal, a board plan from your goals, affirmations.

+3 this week 77 Trust /100

Last scanned (18 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Productivity and Notes

Trust breakdown (7 categories)

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 457 tokens (~152/item across 3 items; 3 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 Management30
  • Stability observed for 9 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
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 12 Nov 26 73

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://futureself-ai.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=futureself-ai.com CN=YR1,O=Let's Encrypt,C=US 12 Nov 2026 10 Feb 2027 RSA 2048 SHA256-RSA 54be9a8ba2d5d44808d568799b2823ee802
SANs: futureself-ai.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of futureself-ai.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
futureself-ai.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-eval' 'unsafe-inline' https://*.stripe.com https://js.stripe.com https://*.google.com https://*.googleapis.com https://*.gstatic.com https://*.googletagmanager.com https://connect.facebook.net https://*.clarity.ms https://www.clarity.ms https://*.doubleclick.net https://s.pinimg.com https://ct.pinterest.com https://va.vercel-scripts.com https://api.goaffpro.com; style-src 'self' 'unsafe-inline' https://*.googleapis.com https://fonts.googleapis.com; img-src 'self' blob: data: https:; font-src 'self' data: https://fonts.gstatic.com https://*.gstatic.com https://fonts.googleapis.com; connect-src 'self' blob: data: https: https://*.stripe.com https://*.google-analytics.com https://*.mixpanel.com https://*.clarity.ms https://*.pinterest.com https://ct.pinterest.com; frame-src 'self' https://*.stripe.com https://js.stripe.com https://*.facebook.com https://ct.pinterest.com; worker-src 'self' blob:; object-src 'none'; base-uri 'self'; form-action 'self' https://www.faceb
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), interest-cohort=(), payment=(self)

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://futureself-ai.com/mcp Verified 200
http (plaintext) http://futureself-ai.com/mcp HTTPS enforced 308 https://futureself-ai.com/mcp
MCP tools · 3 exposed · ~410 tokens

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 →

Tool Tokens
get_affirmations ~97

Returns seven affirmations for one life area (wealth, career, health, relationships or identity) in a gentle, bold or spiritual tone, optionally with the person's first name in them. Use when someone asks for affirmations or mantras to repeat or to write on a vision board.

NameTypeReqDescription
areastringyesThe life area
namestring–First name, optional
tonestring–Default gentle

No output schema declared.

No examples provided.

plan_vision_board ~188

Turns a person's goals, or their wheel-of-life ratings (eight areas rated 1 to 10), into a structured vision board plan: three or four sections, each with scenes to picture, affirmations to write under them and a slot for the first step, plus how to keep the board in use. Goals the library does not know are kept in the person's own words. Use when someone wants help planning or laying out a vision board.

NameTypeReqDescription
goalsarray–Goals in the person's words, most important first, e.g. ["run a marathon", "pay off my debt"]
life_ratingsobject–Optional wheel-of-life ratings, 1 to 10. The lowest-rated areas become sections.
namestring–First name to put in the affirmations, optional
tonestring–Tone of the affirmations, default gentle

No output schema declared.

No examples provided.

search_vision_board_goals ~125

Searches the FutureSelf library of 61 vision board goals (careers, health, money, relationships, growth, lifestyle) and returns the closest matches, each with three concrete scenes to picture and a practical tip for building that board. Use when someone asks what to put on a vision board for a goal, a job or a stage of life, e.g. nurses, debt, a marathon or moving abroad.

NameTypeReqDescription
querystringyesThe goal, job or life stage, e.g. "nurse", "pay off debt", "van life"

No output schema declared.

No examples provided.

Install

How do I install the FutureSelf Vision Board Planner MCP server?

FutureSelf Vision Board Planner is a hosted endpoint at https://futureself-ai.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 · futureself-ai.com

# add to Claude Code
claude mcp add --transport http ranqint-futureself 'https://futureself-ai.com/mcp'
Common questions

What is the FutureSelf Vision Board Planner MCP server?

FutureSelf Vision Board Planner is an MCP server listed in the public MCP registry as io.github.Ranqint/futureself. Plan a vision board: ideas for a goal, a board plan from your goals, affirmations. This page covers its hosted endpoint (https://futureself-ai.com/mcp).

Is the FutureSelf Vision Board Planner MCP server safe to use?

FutureSelf Vision Board Planner scores 77 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 FutureSelf Vision Board Planner MCP server expose?

FutureSelf Vision Board Planner exposes 3 tools: search_vision_board_goals, plan_vision_board, get_affirmations. Their descriptions and schemas cost roughly 410 tokens of context every time the server is loaded.

Does the FutureSelf Vision Board Planner MCP server require authentication?

No. We connected to FutureSelf Vision Board Planner without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the FutureSelf Vision Board Planner MCP server still maintained?

FutureSelf Vision Board Planner is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the FutureSelf Vision Board Planner MCP server?

VerifyMCP ran 13 checks on FutureSelf Vision Board Planner, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.