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.

life. scored.

REMOTE · LIFESCORED.COM · SCANNED SEP 21

Rebuilds the scores real systems run on you — credit, actuarial, lending — in the open, cited.

Available components

0 this week 84 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 Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability86
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 295 tokens (~59/item across 5 items; 4 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
Install

How do I install the life. scored. MCP server?

life. scored. is a hosted endpoint at https://lifescored.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 · lifescored.com

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

  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 +1
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

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

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=lifescored.com CN=WE1,O=Google Trust Services,C=US 11 Aug 2026 9 Nov 2026 ECDSA 256 ECDSA-SHA256 898cdca53752f3421340443a833de4ae
SANs: lifescored.com, *.lifescored.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 secure

Validation of lifescored.com. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
lifescored.com. present 2371 13 Verified
lifescored.com. Verified address RRset verified with the apex keys
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=15552000; includeSubDomains
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://lifescored.com/mcp Verified 200
http (plaintext) http://lifescored.com/mcp HTTPS enforced 301 https://lifescored.com/mcp
MCP tools · 4 exposed · ~207 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_input_schema ~51

Just the fields to collect from the user, with types, ranges/allowed values, defaults, and plain-language help. Ask only for what you do not already know; missing fields fall back to their default.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_methodology ~53

Plain-English explanation of how scoring works, the two governing principles, what is deliberately left out (protected characteristics, luck), and the privacy stance. Use to answer "how does this work / is this fair" questions.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_rulebook ~63

The complete life-score rulebook and exact math: every rule (weight, bounds, evidence, source, formula), the input schema (what to ask the user), and the engine constants. Use this to compute a score on your OWN side — nothing is sent back.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

how_to_give_feedback ~40

How to suggest a better weight, a fresh source, or a new rule via GitHub, so improvements from many people aggregate in the open.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the life. scored. MCP server?

life. scored. is an MCP server listed in the public MCP registry as com.lifescored/mcp. Rebuilds the scores real systems run on you, credit, actuarial, lending, in the open, cited. This page covers its hosted endpoint (https://lifescored.com/mcp).

Is the life. scored. MCP server safe to use?

life. scored. scores 84 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 life. scored. MCP server expose?

life. scored. exposes 4 tools: get_rulebook, get_input_schema, get_methodology, how_to_give_feedback. Their descriptions and schemas cost roughly 207 tokens of context every time the server is loaded.

Does the life. scored. MCP server require authentication?

No. We connected to life. scored. without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the life. scored. MCP server still maintained?

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