MCP.Market

my quant doesn’t speak english — editorial discovery MCP server

online · 100% uptime
by beepboop2025·io.github.beepboop2025/myquant-editorial·v2.1.1

Read-only discovery and bounded access to a finite market briefing with evidence boundaries.

A91/100grade A
What users say
No reviews yet
Be the first
Safety scan
A91/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed my quant doesn’t speak english — editorial discovery yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

my quant doesn’t speak english — editorial discovery tools (5)

write = sends, deletes, buys or posts
  • get_healthFree

    Check that this endpoint responds with product.health.v1 metadata: product, API/MCP versions, deployed source SHA when available, and checked_at. Use for connection and version diagnosis; it does not fetch the editorial feed or prove source freshness. Public and read-only; no credentials or arguments. Use list_capabilities for supported surfaces and content limits.

  • get_storyFree

    Retrieve one published story using its exact stable ID from latest_stories or search_stories. Returns story, feed receipt, and release identity while retaining canonical sources, evidence clocks, publication state, release IDs, and limitations. Matching is exact and case-sensitive; an unknown ID returns a tool error. Public and read-only; no credentials. The canonical feed is cached for up to 60 seconds; unavailable or invalid feeds return a tool error. Use search_stories first when you only know a title or topic.

  • latest_storiesFree

    Read recent published archive records when you want a chronological overview without a search term. Returns count, stories, the feed receipt, and release identity; each story retains sources, evidence clocks, publication state, release IDs, and limitations. Public and read-only; no credentials. Lists default to 10 records, at most 20, without pagination. The canonical feed is cached for up to 60 seconds; unavailable or invalid feeds return a tool error. Use search_stories for text matching or get_story for an exact returned ID.

  • list_capabilitiesFree

    Discover available product features, API/MCP URLs, versions, content limits, and interpretation boundaries before choosing a content tool. Returns product.capabilities.v1 metadata, without fetching stories or checking upstream freshness. Public and read-only; no credentials or arguments. Use latest_stories for recent records or get_health for endpoint compatibility. The mobile app distribution channel remains separately suspended.

  • search_storiesFree

    Find published archive records by text when you do not know an exact story ID. All space-separated terms must match as case-insensitive substrings across IDs, titles, summaries, tags, products, beats, evidence status, contributions, or source labels/release IDs. Returns newest-first stories, normalized query, count, feed receipt, and release identity, preserving evidence clocks and limitations. No relevance ranking or pagination; zero matches returns an empty list. Public and read-only; no credentials. The feed is cached for up to 60 seconds; invalid queries or unavailable/invalid feeds return a tool error. Use get_story for an exact ID or latest_stories for an unfiltered overview.

Public scan report

scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1465ms20/20
  • Tool poisoning5 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 91/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How my quant doesn’t speak english — editorial discovery compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 85% of 48,255 servers
Tools
5
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
152 ms
faster than 73% of 30,031 servers

What its tools let an agent do: 5 read

Install my quant doesn’t speak english — editorial discovery in Claude Code, Cursor or VS Code

claude mcp add --transport http myquant-editorial https://myquantdoesntspeakenglish.com/mcp
Add to Cursor

What the publisher says

From the my quant doesn’t speak english — editorial discovery repository's README, as published. We do not edit it. Read it on GitHub

my quant doesn’t speak english

The public editorial and advertising front door for the Liquidity Lab family: Seiche, LiquiLens, and LiquiLens—Undertow.

The site consumes each product's structured editorial feed at build time. Its SOURCE_PUBLISHED website mode gives every record the source marks published a MyQuant reading page, while preserving the specialist's canonical URL, exact claim, evidence clocks, fingerprint, and limitation. The mobile app feed is independently SUSPENDED and contains zero stories.

Every specialist page must also pass the analysis-quality gate. It answers what the source says, what changed (or why a comparison is unavailable), why the mechanism matters, what to inspect next, and where the evidence stops. The JSON Feed carries the same change/next-check fields and its PASSED receipt. A build fails instead of publishing thin labels, missing source identity, missing clocks, or known invalid comparison grammar.

data/fleet-registry.json maps the complete registered family at an immutable LiquiLens family.toml revision: seven core repositories, six research modules, and ten adjacent surfaces. Coverage does not imply ingestion. Only LiquiLens, Seiche, and Undertow market-liquidity currently publish compatible direct readings; upstream, research, private, paused, delivery, and separate-domain projects remain visible at /coverage with their exact reason.

The public site has two explicit lanes:

  • Interpreted: plain-English readings of Seiche, LiquiLens, and Undertow work;
  • MyQuant Analysis: independently sourced house reporting on important news.

The Interpreted lane includes reviewed longforms and LiquiLens historical case files. Case files display each lens's HIT, MISS, or VOID separately and state whether the replay was reconstructed later. They are not silently promoted into real-time calls or validated-backtest evidence.

Original house reporting lives in content/ and must declare its sources, contribution, limitations, and publication status.

npm test
MYQUANT_USE_REVIEWED_CACHE=1 npm run build
npm run verify
npm run dev

The build has no runtime dependencies. If a source is temporarily unavailable, it uses the last successful data/cache.json slice for that source and prints the coverage state in the generated page. The LiquiLens desk channel is additionally pinned to liquilens.desk-bit-feed.v1; a missing or changed root schema is treated as an upstream contract failure, so the build keeps the last accepted channel and marks LiquiLens as cached/degraded instead of normalizing an unknown shape.

Public API and MCP

The product exposes read-only discovery without accounts or user state:

bounded latest stories, exact stable-ID retrieval, and evidence-aware search;

  • GET /api/v1/capabilities describes the editorial, feed, and evidence surfaces;
  • GET /api/v1/health returns a non-sensitive compatibility heartbeat;
  • POST /mcp serves five stateless, read-only tools: discovery, health,

public AI/MCP discovery, with the Registry manifest at GET /server.json.

  • GET /openapi.json is the curated REST contract;
  • GET /.well-known/ai-catalog.json and GET /.well-known/mcp.json expose

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

my quant doesn’t speak english — editorial discovery: common questions

Is my quant doesn’t speak english — editorial discovery MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the my quant doesn’t speak english — editorial discovery safety report
How do I install my quant doesn’t speak english — editorial discovery?
It runs remotely at myquantdoesntspeakenglish.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does my quant doesn’t speak english — editorial discovery need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is my quant doesn’t speak english — editorial discovery maintained?
The last commit was 19 days ago (2026-10-16). The latest release is v2.1.1.
Is my quant doesn’t speak english — editorial discovery up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does my quant doesn’t speak english — editorial discovery compare with other MCP servers?
safety score 91/100 (higher than 85% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from beepboop2025 →