Koskamo

my quant MCP

A finite market briefing MCP server that provides up to five stories translated into plain English with sources and evidence boundaries. It offers read-only discovery for editorial analysis, with reader settings and caches remaining on-device.

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.

my quant MCP logo, by my quantCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-07Published by my quant
MCP endpoint (Streamable HTTP)
https://myquant-app.vercel.app/mcp
Vendor documentation

What its tools do

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

2 of 2 have a description · 2 of 2 declare behavior hints

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Retrieve finite market briefings
  • Access sourced editorial analysis
  • Discover stories with evidence boundaries

Source and maintenance

Community listingRegistry 2.0.0
Maintenance checked

Protocol and capabilities

Server
myquant-app 2.0.0
MCP protocol negotiated in check
2025-11-25
Tools
2 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.

Use this server to discover the My Quant app and its public feed contract. Do not infer access to on-device saved stories, topic settings, or caches; those remain local to the reader.

Tools

2 advertised

list_capabilities — Discover the My Quant app
Advertised by the server during the last successful anonymous check.
Advertised read-only

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

list_capabilities input schema
{
  "type": "object",
  "additionalProperties": false
}
list_capabilities annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
get_health — Check the My Quant app public surfaces
Advertised by the server during the last successful anonymous check.
Advertised read-only

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

get_health input schema
{
  "type": "object",
  "additionalProperties": false
}
get_health annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

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
469 ms
95th percentile latency
469 ms

Maintenance history

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

  • · probe · passed · 469 ms · metadata changed · 2 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 my-quant-mcp https://myquant-app.vercel.app/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 my-quant-mcp --url https://myquant-app.vercel.app/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable my-quant-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "my-quant-mcp": {
      "url": "https://myquant-app.vercel.app/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "my-quant-mcp": {
      "type": "streamableHttp",
      "url": "https://myquant-app.vercel.app/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start my-quant-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "my-quant-mcp": {
      "type": "http",
      "url": "https://myquant-app.vercel.app/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 my-quant-mcp https://myquant-app.vercel.app/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://myquant-app.vercel.app/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": {
    "my-quant-mcp": {
      "serverUrl": "https://myquant-app.vercel.app/mcp"
    }
  }
}

Let your agent find its tools

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