
edgestudy
io.github.CloudCorpRecords/edgestudy
List the published Edge Lab trading-system research studies: slug, title, date and URL.
Documentation
edgestudy
Ask what Edge Lab has actually published, and get the real index back instead of a guess. edgestudy is a local forwarding client for the hosted Edge Lab MCP service: it answers tools/list on your own machine from the captured tool definition and forwards the catalogue request to Edge Lab, returning the answer exactly as the service sends it.
The surface is a single read-only listing. It covers published research metadata only — the slug, title, published date and URL of each study in the Edge Lab catalogue. There is no trading tool here, no order placement, no account access and nothing to buy: the package is a pipe to a public index, not a copy of it, and nothing is cached or stored locally.
The tool
list_studies— Every published Edge Lab research study: slug, title, published date, and URL, taken from the authoritative catalogue. Takes no arguments.
Install and run
As an MCP server via npm:
npx -y @reneturcios/edgestudy mcp
MCP client configuration:
{
"mcpServers": {
"edgestudy": {
"command": "npx",
"args": ["-y", "@reneturcios/edgestudy", "mcp"]
}
}
}
As a container:
docker run -i ghcr.io/cloudcorprecords/edgestudy
docker run --rm ghcr.io/cloudcorprecords/edgestudy list_studies '{}'
CLI
One binary serves both the command line and the MCP server. The tool is a subcommand taking a single JSON string with that tool's arguments:
edgestudy list_studies '{}'
edgestudy --version
Exit 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
LIFELONGEDGE_MCP_URL— Overrides the upstream endpoint. The default is the pinned hosted endpoint,https://lifelongedge.com/mcp. (The override variable is a reconstruction added by this rebuild.)
The Edge Lab registry record declares no headers on its remote, so edgestudy sends no authentication header of any kind — the catalogue read is 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 edgestudy 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 source
The 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.
@reneturcios/edgestudynpm install @reneturcios/edgestudyghcr.io/cloudcorprecords/edgestudy:0.1.0docker pull ghcr.io/cloudcorprecords/edgestudy:0.1.0:undefinedRelated Servers
io.github.CloudCorpRecords/abandoncheck
Judge whether a dependency is maintained, from factual signals: releases, commits, archival.
io.github.CloudCorpRecords/actionbridge
Zapier exposed actions as MCP tools via a generic action runner.
io.github.CloudCorpRecords/actionpin
GitHub Actions supply-chain hardener: audit workflows for unpinned actions and build a SHA pin plan.