Edge Lab MCP

An MCP server operated by LifeLongEdge that allows AI assistants to query published Edge Lab trading-system research studies as structured data, providing a catalog of studies with slugs, titles, dates, and URLs.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Vendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by LifeLongEdge

MCP endpoint (Streamable HTTP)

https://lifelongedge.com/mcp

Vendor documentation

What its tools do

1 tool, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Not annotated (1)

list_studies

1 of 1 have a description · 0 of 1 declare behavior hints

Checks and signals

Each line is separate evidence, not a trust score.

Passed Endpoint answered the live check · Nov 6, 2026, 2:18 PM UTC
Passed Official MCP Registry namespace is tied to lifelongedge.com · Nov 6, 2026, 1:58 PM UTC
Passed Endpoint is on the registry namespace domain · Nov 6, 2026, 1:58 PM UTC
Availability 1 of 1 checks passed in 30 days

What you can do with it

Query the published Edge Lab catalog of trading research studies
Retrieve structured metadata for specific trading system studies
Access research URLs and publication dates via AI assistants

Source and maintenance

Vendor evidenceRegistry 0.1.0

mcp-registry: com.lifelongedge/edge-lab@0.1.0

Protocol and capabilities

Server: edge-lab 0.1.0
MCP protocol negotiated in check: 2025-06-18
Tools: 1 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Edge Lab study catalog. Call list_studies to retrieve the published research index (slug, title, published date, URL).

Tools

1 advertised

list_studies — List Edge Lab studies

Advertised by the server during the last successful anonymous check.

List every published (public) Edge Lab research study: slug, title, published date, and URL. Returns the authoritative catalog so the answer comes from the real index rather than a guess. Takes no arguments.

list_studies input schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (2 of 2 answered).

2026-11-06: 1 of 1 checks answered
2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 568 ms
95th percentile latency: 568 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 6, 2026, 2:18 PM UTC · probe · passed · 568 ms · metadata changed · 1 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http edge-lab-mcp https://lifelongedge.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add edge-lab-mcp --url https://lifelongedge.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable edge-lab-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "edge-lab-mcp": {
      "url": "https://lifelongedge.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "edge-lab-mcp": {
      "type": "streamableHttp",
      "url": "https://lifelongedge.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start edge-lab-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "edge-lab-mcp": {
      "type": "http",
      "url": "https://lifelongedge.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http edge-lab-mcp https://lifelongedge.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.

Claude Desktop configuration

https://lifelongedge.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "edge-lab-mcp": {
      "serverUrl": "https://lifelongedge.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Edge Lab MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

See all 6,928

Do you run Edge Lab MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing