my quant — finite market briefing

io.github.beepboop2025Published by GitHub account beepboop2025v2.0.0Updated Oct 24, 2026

Read-only discovery for a finite, offline-capable market briefing with explicit evidence boundaries.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Provides read-only discovery of a finite, offline-capable market briefing with explicit evidence boundaries.

What you can do
The server offers read-only discovery for a market briefing. According to the description, the briefing is finite and offline-capable, and it states explicit evidence boundaries. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Worth considering when an assistant needs read-only access to a bounded market briefing and the limits of that evidence are acceptable. It is not intended for trading, order placement, or other write actions, since the description covers discovery only. Because no tools are listed, confirm the available operations before depending on it.
Requirements
A remote streamable HTTP endpoint at No packages, environment variables, headers, or authentication are declared, so it appears to need only network access to that endpoint.
Before you install
The description states the briefing is finite and has explicit evidence boundaries, so coverage may be limited and should not be treated as complete or current market information. No credentials, payments, wallets, or write actions are declared, but the manifest lists no tools, so verify what the server actually exposes before relying on it.

Installation

In SourceWeft

  1. Open my quant — finite market briefing in the dashboard and add it to a workspace.
  2. 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/io.github.beepboop2025%2Fmyquant-app/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.

{
  "mcpServers": {
    "my-quant-finite-market-briefing": {
      "type": "http",
      "url": "https://myquant-app.vercel.app/mcp"
    }
  }
}

README

This repository has no README.

Tools

2

list_capabilities

Discover the My Quant app

List the current briefing, feed validation, offline reading, topic controls, API, MCP, and product boundaries.

Takes no parameters.

get_health

Check the My Quant app public surfaces

Return a non-sensitive API and MCP compatibility heartbeat without reading or changing on-device state.

Takes no parameters.

Version history

1
  1. v2.0.0LatestSep 16, 2026

Score

75% 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 listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.