scoreguide
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
scoreguide
Documentation for a life-score system, read where you work. scoreguide is a local forwarding client for the hosted LifeScored MCP service: it answers tools/list on your own machine from the captured tool definitions and forwards every read to LifeScored, returning the answers exactly as the service sends them back.
The surface is entirely read-only and takes no personal data. You can pull the complete rulebook with its exact math, fetch just the list of questions the system asks, read a plain-English account of how scoring works and what it deliberately leaves out, and learn how to propose an improvement. Scoring itself, when it happens, is computed on the caller's own side — nothing about any person is sent back through these tools.
The tools
get_rulebook— The complete rulebook and exact math: every rule with its weight, bounds, evidence, source and formula, plus the input schema and the engine constants. Takes no arguments.get_input_schema— Just the fields to collect from a user, with types, ranges or allowed values, defaults, and plain-language help. Missing fields fall back to their default. Takes no arguments.get_methodology— How scoring works in plain English, the two governing principles, what is deliberately left out, and the privacy stance — the read to reach for when someone asks whether the system is fair. Takes no arguments.how_to_give_feedback— How to suggest a better weight, a fresh source, or a new rule via GitHub, so improvements from many people aggregate in the open. Takes no arguments.
Related MCP server: OWASP Pentest Guide Knowledge Base
Install and run
As an MCP server via npm:
npx -y @reneturcios/scoreguide mcpMCP client configuration:
{
"mcpServers": {
"scoreguide": {
"command": "npx",
"args": ["-y", "@reneturcios/scoreguide", "mcp"]
}
}
}As a container:
docker run -i ghcr.io/cloudcorprecords/scoreguide
docker run --rm ghcr.io/cloudcorprecords/scoreguide get_rulebook '{}'CLI
One binary serves both the command line and the MCP server. Each tool is a subcommand taking a single JSON string with that tool's arguments:
scoreguide get_rulebook '{}'
scoreguide get_input_schema '{}'
scoreguide get_methodology '{}'
scoreguide how_to_give_feedback '{}'
scoreguide --versionExit codes: 0 when the forwarded call succeeds, 1 when the upstream result is an error, and 2 for usage problems such as an unknown subcommand or a malformed JSON argument.
Configuration
LIFESCORED_MCP_URL— Overrides the upstream endpoint. The default is the pinned hosted endpoint,https://lifescored.com/mcp. (The override variable is a reconstruction added by this rebuild.)
The LifeScored registry record declares no headers on its remote, so scoreguide sends no authentication header of any kind — reads are keyless.
Upstream failures — a JSON-RPC error from the service, a non-2xx response, an unreadable body, or a request that fails outright — are reported to the caller as an error result whose text starts with scoreguide error:.
How forwarding works
The first forwarded call opens a session: an initialize request (protocol version 2025-03-26), followed by a notifications/initialized notification, then the tools/call itself. If the service answers the initialize request with an Mcp-Session-Id header, that value is carried on every later request, and the open session is reused for the rest of the process. Replies are accepted either as plain JSON or as server-sent events. Successful results pass through verbatim, including any isError flag and any extra fields the service includes.
Development
npm install
npm run build # tsc -> dist/ (dist/cli.js is the bin)
npm test # tsx --test test/*.test.ts — stubbed upstream, no network
npm run dev # run the CLI from sourceThe test suite checks the served tool list against the captured surface, exercises the session handshake and its reuse, asserts that no Authorization header is sent under any environment, and verifies that arguments go upstream untouched and results come back untouched.
License
MIT — see LICENSE. Copyright (c) 2026 Rene Turcios.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Read-only MCP server for The Quiet Protocol's engines, benchmarks, proof, and business data.
Read-only MCP server that answers questions about turva.dev from its published data. Five tools return JSON: the service catalog with prices, contact and operator details, engagement principles and dated agent-readiness and security evidence with verification links. Connect over Streamable HTTP. You need no API key. The server does not scan other websites or run audits.
Public, read-only MCP server for FarmNeural company facts, packages, and capabilities.
Read-only MCP for AI usage profiles, leaderboards, stats, and docs; no writes or private data.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceRead-only MCP server that answers questions about turva.dev from its published data. Five tools return JSON: the service catalog with prices, contact and operator details, engagement principles and dated agent-readiness and security evidence with verification links. Connect over Streamable HTTP. You need no API key. The server does not scan other websites or run audits.MIT
- AlicenseAqualityDmaintenanceRead-only MCP server for precise lookup, search, and versioned retrieval of OWASP testing guides (WSTG, MASTG, ISTG, AITG) with full provenance on every result.11Apache 2.0
- AlicenseAqualityBmaintenanceA read-only MCP server so AI agents can query the corpus or the live site.1234 PyPI18MIT
- AlicenseAqualityAmaintenanceRead-only MCP server for discovering and validating Architecture Decision Records, inspecting architecture impact, and reviewing architectural drift evidence.714MIT