Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

my quant doesn’t speak english — editorial discovery

REMOTE · MYQUANTDOESNTSPEAKENGLISH.COM · SCANNED SEP 20

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

+3 this week 87 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 763 tokens (~152/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (60% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the my quant doesn’t speak english — editorial discovery MCP server?

my quant doesn’t speak english — editorial discovery is a hosted endpoint at https://myquantdoesntspeakenglish.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · myquantdoesntspeakenglish.com

# add to Claude Code
claude mcp add --transport http beepboop2025-myquant-editorial 'https://myquantdoesntspeakenglish.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "beepboop2025-myquant-editorial": {
      "url": "https://myquantdoesntspeakenglish.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "beepboop2025-myquant-editorial": {
      "type": "http",
      "url": "https://myquantdoesntspeakenglish.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.beepboop2025-myquant-editorial]
url = "https://myquantdoesntspeakenglish.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "beepboop2025-myquant-editorial": {
      "type": "remote",
      "url": "https://myquantdoesntspeakenglish.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add beepboop2025-myquant-editorial --url 'https://myquantdoesntspeakenglish.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  beepboop2025-myquant-editorial:
    url: "https://myquantdoesntspeakenglish.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "beepboop2025-myquant-editorial": {
      "Transport": "http",
      "Url": "https://myquantdoesntspeakenglish.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add beepboop2025-myquant-editorial -t streamable-http -u 'https://myquantdoesntspeakenglish.com/mcp'
// mcp.json
{
  "mcpServers": {
    "beepboop2025-myquant-editorial": {
      "type": "http",
      "url": "https://myquantdoesntspeakenglish.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Sept 26 +3
    • Tool “get_health” rewrote its description, which is the text the model reads security
    • Tool “get_story” rewrote its description, which is the text the model reads security
    • Tool “latest_stories” rewrote its description, which is the text the model reads security
    • Tool “list_capabilities” rewrote its description, which is the text the model reads security
    • Tool “search_stories” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail functional
    • Tool coverage: 0% → 100% functional
    • Schema quality: good → excellent functional
    • Server version: 2.1.0 → 2.1.1 functional
    • “get_story” reworded the description of “id” cosmetic
    • “latest_stories” reworded the description of “limit” cosmetic
    • “search_stories” reworded the description of “limit” cosmetic
    • “search_stories” reworded the description of “query” cosmetic
  • 5 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://myquantdoesntspeakenglish.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=myquantdoesntspeakenglish.com CN=YR1,O=Let's Encrypt,C=US 12 Aug 2026 10 Nov 2026 RSA 2048 SHA256-RSA 571353c286d940cabec25fdb278b6ae194d
SANs: myquantdoesntspeakenglish.com, www.myquantdoesntspeakenglish.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of myquantdoesntspeakenglish.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
myquantdoesntspeakenglish.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self'; font-src 'self'; img-src 'self' data:; connect-src 'none'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy camera=(), microphone=(), geolocation=(), payment=(), usb=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://myquantdoesntspeakenglish.com/mcp Verified 200
http (plaintext) http://myquantdoesntspeakenglish.com/mcp HTTPS enforced 308 https://myquantdoesntspeakenglish.com/mcp
MCP tools · 5 exposed · ~708 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_health ~77

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_story ~153

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.

NameTypeReqDescription
idstringyesExact stable story id copied from a list/search result, including its prefix; not a title or URL. Case-sensitive, nonblank, without surrounding whitespace, at most 256 characters.
NameTypeReqDescription
feedobjectyes
releaseobjectyes
schemayes
storyobjectyes

No examples provided.

latest_stories ~144

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.

NameTypeReqDescription
limitintegerMaximum records to return, newest first; 1–20, default 10. There is no pagination parameter.
NameTypeReqDescription
countintegeryesNumber of records returned, not the total number of matches.
feedobjectyesCanonical feed URL, content hash, item count, publication authority, and retrieval timestamp.
releaseobjectyesMCP version and deployed source SHA, when available.
schemayes
storiesarrayyesNewest-first published records retaining stable IDs, source links, evidence clocks, publication state, release IDs, and limitations.

No examples provided.

list_capabilities ~82

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_stories ~252

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.

NameTypeReqDescription
limitintegerMaximum matching records to return, newest first; 1–20, default 10. Does not change which terms must match.
querystringyesPlain text, for example "dollar funding" or a source release ID. Unicode NFKC-normalized, trimmed, and whitespace-collapsed; every term must match. At most 12 terms, 160 characters, and 512 UTF-8 byt…
NameTypeReqDescription
countintegeryesNumber of records returned, not the total number of matches.
feedobjectyesCanonical feed URL, content hash, item count, publication authority, and retrieval timestamp.
querystringyesThe Unicode-normalized query with leading/trailing whitespace removed and internal whitespace collapsed.
releaseobjectyesMCP version and deployed source SHA, when available.
schemayes
storiesarrayyesNewest-first published records retaining stable IDs, source links, evidence clocks, publication state, release IDs, and limitations.

No examples provided.

Common questions

What is the my quant doesn’t speak english — editorial discovery MCP server?

my quant doesn’t speak english — editorial discovery is an MCP server listed in the public MCP registry as io.github.beepboop2025/myquant-editorial. Read-only discovery and bounded access to a finite market briefing with evidence boundaries. This page covers its hosted endpoint (https://myquantdoesntspeakenglish.com/mcp).

Is the my quant doesn’t speak english — editorial discovery MCP server safe to use?

my quant doesn’t speak english — editorial discovery scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the my quant doesn’t speak english — editorial discovery MCP server expose?

my quant doesn’t speak english — editorial discovery exposes 5 tools: list_capabilities, get_health, latest_stories, get_story, search_stories. Their descriptions and schemas cost roughly 708 tokens of context every time the server is loaded.

Does the my quant doesn’t speak english — editorial discovery MCP server require authentication?

No. We connected to my quant doesn’t speak english — editorial discovery without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the my quant doesn’t speak english — editorial discovery MCP server still maintained?

my quant doesn’t speak english — editorial discovery is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.