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.

Anchored Hope Index™ | Mental Resilience Counseling

REMOTE · ANCHOREDHOPEINDEX.COM · SCANNED SEP 20

A professional resilience and future-orientation assessment for leaders, executives, and high-perfor

0 this week 61 Trust /100
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 Security57
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 220 tokens (~110/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: schema churn in the 16 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Anchored Hope Index™ | Mental Resilience Counseling MCP server?

Anchored Hope Index™ | Mental Resilience Counseling is a hosted endpoint at https://anchoredhopeindex.com/api/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 · anchoredhopeindex.com

# add to Claude Code
claude mcp add --transport http janoliverautomation-stack-anchoredhopeindex-com 'https://anchoredhopeindex.com/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "janoliverautomation-stack-anchoredhopeindex-com": {
      "url": "https://anchoredhopeindex.com/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "janoliverautomation-stack-anchoredhopeindex-com": {
      "type": "http",
      "url": "https://anchoredhopeindex.com/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.janoliverautomation-stack-anchoredhopeindex-com]
url = "https://anchoredhopeindex.com/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "janoliverautomation-stack-anchoredhopeindex-com": {
      "type": "remote",
      "url": "https://anchoredhopeindex.com/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add janoliverautomation-stack-anchoredhopeindex-com --url 'https://anchoredhopeindex.com/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  janoliverautomation-stack-anchoredhopeindex-com:
    url: "https://anchoredhopeindex.com/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "janoliverautomation-stack-anchoredhopeindex-com": {
      "Transport": "http",
      "Url": "https://anchoredhopeindex.com/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add janoliverautomation-stack-anchoredhopeindex-com -t streamable-http -u 'https://anchoredhopeindex.com/api/mcp'
// mcp.json
{
  "mcpServers": {
    "janoliverautomation-stack-anchoredhopeindex-com": {
      "type": "http",
      "url": "https://anchoredhopeindex.com/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 10 Sept 26 −2
    • Stability: 0.17 → fail security
    • A breaking change shipped without a version bump: still 1.0.0 security
    • “run_anchored_hope_index” made “agency” required, so existing callers break functional
    • “run_anchored_hope_index” made “emotionalEndurance” required, so existing callers break functional
    • “run_anchored_hope_index” made “futureDirection” required, so existing callers break functional
    • “run_anchored_hope_index” made “meaning” required, so existing callers break functional
    • “run_anchored_hope_index” made “motivationStability” required, so existing callers break functional
    • “run_anchored_hope_index” made “stressStability” required, so existing callers break functional
    • “run_anchored_hope_index” made “supportConnection” required, so existing callers break functional
  • 8 Sept 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.

  • 6 Sept 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.

  • 5 Sept 26 +5
    • Schema quality: 118 → 220 functional
    • Tool coverage: 0% → 100% functional
    • Stability: unverified → 0.03 functional
    • Tool “run_anchored_hope_index” now declares an output schema functional
    • First check of Tool coverage: 100 functional
    • Schema quality: fair → good functional
    • New tool “get_framework_metadata” functional
    • “run_anchored_hope_index” reworded the description of “agency” cosmetic
    • “run_anchored_hope_index” reworded the description of “emotionalEndurance” cosmetic
    • “run_anchored_hope_index” reworded the description of “futureDirection” cosmetic
    • “run_anchored_hope_index” reworded the description of “meaning” cosmetic
    • “run_anchored_hope_index” reworded the description of “motivationStability” cosmetic
    • “run_anchored_hope_index” reworded the description of “stressStability” cosmetic
    • “run_anchored_hope_index” reworded the description of “supportConnection” cosmetic
    • Tool “run_anchored_hope_index” changed its title: Run Anchored Hope Index™ cosmetic
  • 4 Sept 26 56

    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 20 Sept 2026 · Probed https://anchoredhopeindex.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=anchoredhopeindex.com CN=WE1,O=Google Trust Services,C=US 28 Aug 2026 26 Nov 2026 ECDSA 256 ECDSA-SHA256 4b7b52840f3b46f9133c7661e095a140
SANs: anchoredhopeindex.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of anchoredhopeindex.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
anchoredhopeindex.com. absent 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://anchoredhopeindex.com/api/mcp Verified 200
http (plaintext) http://anchoredhopeindex.com/api/mcp HTTPS enforced 301 https://anchoredhopeindex.com/api/mcp
MCP tools · 2 exposed · ~201 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_framework_metadata ~44

Returns the scoring framework metadata: seven resilience domains, five result bands with score ranges, and the Likert scale definition. No arguments required. Read-only, no PII.

Input schema present but exposes no named parameters.

NameTypeReqDescription
disclaimerstringyes
domainsarrayyes
likertScaleobjectyes
resultBandsarrayyes
toolstringyes

No examples provided.

run_anchored_hope_index ~157

Educational, non-clinical structured reflection on hope and resilience. This tool provides educational information only and is not a clinical assessment or medical advice.

NameTypeReqDescription
agencynumberyesAgency & Pathway Belief (1-5)
emotionalEndurancenumberyesEmotional Endurance (1-5)
futureDirectionnumberyesFuture Orientation (1-5)
meaningnumberyesMeaning & Purpose (1-5)
motivationStabilitynumberyesMotivation Stability (1-5)
stressStabilitynumberyesStress Stability (1=high drift, 5=very stable)
supportConnectionnumberyesSupport & Relational Anchor (1-5)
NameTypeReqDescription
categorystringyes
disclaimerstringyes
domainScoresarrayyes
educationalInterpretationstringyes
nextStepsarrayyes
priorityReflectionAreasarrayyes
resultBandstringyes
resultBandLabelstringyes
safetyobjectyes
scorenumberyes
toolstringyes
totalScorenumberyes

No examples provided.

Common questions

What is the Anchored Hope Index™ | Mental Resilience Counseling MCP server?

Anchored Hope Index™ | Mental Resilience Counseling is an MCP server listed in the public MCP registry as io.github.janoliverautomation-stack/anchoredhopeindex-com. A professional resilience and future-orientation assessment for leaders, executives, and high-perfor. This page covers its hosted endpoint (https://anchoredhopeindex.com/api/mcp).

Is the Anchored Hope Index™ | Mental Resilience Counseling MCP server safe to use?

Anchored Hope Index™ | Mental Resilience Counseling scores 61 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 Anchored Hope Index™ | Mental Resilience Counseling MCP server expose?

Anchored Hope Index™ | Mental Resilience Counseling exposes 2 tools: run_anchored_hope_index, get_framework_metadata. Their descriptions and schemas cost roughly 201 tokens of context every time the server is loaded.

Does the Anchored Hope Index™ | Mental Resilience Counseling MCP server require authentication?

No. We connected to Anchored Hope Index™ | Mental Resilience Counseling without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Anchored Hope Index™ | Mental Resilience Counseling MCP server still maintained?

Anchored Hope Index™ | Mental Resilience Counseling is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.