myquant-editorial
https://myquantdoesntspeakenglish.com
Registry code: 292a2b0a31f245f8
Use this server to discover or read the current My Quant briefing. Address stories by their stable source IDs, keep every returned source, release ID, publication state, evidence clock, and limitation attached, and treat every market statement as editorial analysis rather than personalized advice.
- endpoint
- https://myquantdoesntspeakenglish.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is myquant-editorial live?
- Yes — it answered the hub's last check (checked 17m ago). It answered 100% of checks over the last 30 days.
- Is myquant-editorial free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does myquant-editorial have?
- 5 tools: get_story, search_stories, list_capabilities, get_health, latest_stories.
- Is myquant-editorial safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 5 tools
- degraded → live
- unknown → live
- topic
- finance & markets
- used for
- read latest market briefing stories
- search briefing archive
- get a story by id
- takes → gives
- text → text, data
- tools
- 5 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_capabilities reads open 41d ago
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.
{ "type": "object", "additionalProperties": false }arguments 4 linesget_health reads open 41d ago
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.
{ "type": "object", "additionalProperties": false }arguments 4 lineslatest_stories reads open 41d ago
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.
{ "type": "object", "properties": { "limit": { "type": "integer", "default": 10, "maximum": 20, "minimum": 1, "description": "Maximum records to return, newest first; 1–20, default 10. There is no pagination parameter." } }, "additionalProperties": false }arguments 13 linesget_story reads unknown never probed
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.
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "maxLength": 256, "minLength": 1, "description": "Exact 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." } }, "additionalProperties": false }arguments 15 linessearch_stories reads unknown never probed
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.
{ "type": "object", "required": [ "query" ], "properties": { "limit": { "type": "integer", "default": 10, "maximum": 20, "minimum": 1, "description": "Maximum matching records to return, newest first; 1–20, default 10. Does not change which terms must match." }, "query": { "type": "string", "maxLength": 160, "minLength": 1, "description": "Plain 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 bytes after normalization. No quote, Boolean, regex, or semantic-search syntax." } }, "additionalProperties": false }arguments 22 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id292a2b0a31f245f8.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/292a2b0a31f245f8/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/292a2b0a31f245f8?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.