LifeScored MCP Server
Provides access to the rulebook, input schema, and methodology for the life scored system, enabling agents to compute scores locally without sending personal data to the server.
Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
royashbrook
Source: Glama
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.
get_rulebookThe 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.
get_input_schemaJust 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.
get_methodologyPlain-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.
how_to_give_feedbackHow to suggest a better weight, a fresh source, or a new rule via GitHub, so improvements from many people aggregate in the open.
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
SvelteKit: ReDoS (O(n^2)) in content negotiation — unauthenticated DoS via the Accept header
SvelteKit: Prototype pollution in file input deletion path in remote-function forms
SvelteKit: Big remote form function payloads can cause Node process to crash
Dependencies
16 dependencies, 1 flagged: @playwright/test
Tool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
4/4 tools missing one or more hints — get_rulebook (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_input_schema (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_methodology (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +1 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
Tool test coverage
3/4 tools referenced in tests (75%)
Write tests that reference each tool by name so every tool has at least one test.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/royashbrook/lifescored)?variant=verified to the badge URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check