LOPJLB Research

com.lopjlbPublished by lopjlb.comOfficial publisherv1.5.0Updated Nov 7, 2026

U.S. equity quant research: market regime, signals, scores, screens and CallCards.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote MCP server for U.S. equity quantitative research, giving an assistant market regime, signals, scores, screens and CallCards.

What you can do
  • Retrieve U.S. equity quantitative research outputs such as market regime assessments and signals
  • Look up scores and run screens over U.S. equities
  • Access CallCards, the provider's research summaries
  • No tool list, instructions or README were supplied, so the exact operations and their inputs are not documented here
When to use it
Worth considering when an assistant needs U.S. equity market context, quantitative signals or screening results inside a research or analysis conversation, rather than raw price data.
Requirements
A remote streamable HTTP endpoint at the provider's site; OAuth authentication is required. No packages, environment variables or headers are declared.
Before you install
Access requires OAuth sign-in to the provider's service, so an account and its permissions are involved. Research outputs are third-party analysis, not verified facts, and should not be treated as investment advice. No tool list is published, so what the assistant can read or change is unclear before connecting.

Installation

In SourceWeft

  1. Open LOPJLB Research in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.lopjlb%2Fresearch/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "lopjlb-research": {
      "type": "http",
      "url": "https://www.lopjlb.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.5.0LatestNov 7, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.