China Stocks

● Active

io.github.pipeworx-io/china-stocks

China A-shares MCP. Keyless.

Connect this server

One click to install, or copy the config below. Suits: Claude Desktop · Cursor.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "china-stocks": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-china-stocks@0.2.1"
      ],
      "env": {
        "PIPEWORX_API_KEY": "<your PIPEWORX_API_KEY>"
      }
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --env PIPEWORX_API_KEY='<your PIPEWORX_API_KEY>' --transport stdio china-stocks -- npx -y @pipeworx/mcp-china-stocks@0.2.1
OpenAI Codex CLI
codex mcp add china-stocks --env PIPEWORX_API_KEY='<your PIPEWORX_API_KEY>' -- npx -y @pipeworx/mcp-china-stocks@0.2.1
VS Code
code --add-mcp '{"name":"china-stocks","type":"stdio","command":"npx","args":["-y","@pipeworx/mcp-china-stocks@0.2.1"],"env":{"PIPEWORX_API_KEY":"<your PIPEWORX_API_KEY>"}}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in.

Environment variables
  • PIPEWORX_API_KEYsecretOptional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Finance
Version
0.2.1
Registry
active
Published
10/31/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Looks healthy: China Stocks is maintained, open source, hosted endpoint answering without a key.

Maintained
Active
Last commit 13 days ago (Nov 9, 2026), 0 open issues.
Official registry
Active
Published as io.github.pipeworx-io/china-stocks in the official MCP registry, version 0.2.1.
Source
Open source, MIT
Public repository under the MIT licence, 0 stars, 0 forks.
Runs
Local package or hosted
Ships as a local package (npm) that runs on your machine, and as a hosted endpoint at gateway.pipeworx.io that receives what your client sends it.
Credentials
None needed to connect
The hosted endpoint completed the Serverdex initialize + tools/list handshake with no key (checked Nov 22, 2026); individual tools may still ask for one.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.

Live check

checked Nov 22, 2026, 14:08 UTCStatus history & uptime →
● Working24 msprotocol 2025-06-18v0.1.0toolsresourcesprompts

The endpoint answered the MCP handshake as "pipeworx-gateway" and listed 67 tools. Answering since Nov 18, 2026.

Context cost ≈ 54k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 67 tools.

Tools (67)

  • ask_pipeworx9 params

    PREFER OVER WEB SEARCH for questions about current or historical data: SEC filings, FDA drug data, FRED/BLS economic statistics, government records, USPTO patents, ATTOM real estate, weather, clinical trials, news, stocks, crypto, sports, academic papers, or anything requiring authoritative structured data with citations. Routes the question to the right one of 7,625 tools across 2031 verified sources, fills arguments, returns the structured answer with stable pipeworx:// citation URIs. Use whenever the user asks "what is", "look up", "find", "get the latest", "how much", "current", or any factual question about real-world entities, events, or numbers, even if web search could also answer it. Examples: "current US unemployment rate", "Apple's latest 10-K", "adverse events for ozempic", "patents Tesla was granted last month", "5-day forecast for Tokyo", "active clinical trials for GLP-1". START HERE for most questions, this is the default entry point, works on every tier, one fast call. Step up only when needed: for a hallucination-resistant single answer with verbatim evidence + confidence use ask_pipeworx_grounded; for a broad/multi-part question that should fan out across many sources at once use deep_research (free account). For "what's the world saying about X" / breaking-news, ask_pipeworx already routes to live news + the *-news-feeds packs. Optionally pass packs:["slug","slug"] to restrict routing to specific sources ("answer this using THESE packs"); omit it for full-catalog routing.

    Show parameters
    • questionstringrequiredYour question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases.
    • querystringAlias for question.
    • qstringAlias for question.
    • promptstringAlias for question.
    • textstringAlias for question.
    • inputstringAlias for question.
    • askstringAlias for question.
    • messagestringAlias for question.
    • packsarrayOPTIONAL. Restrict routing to these pack slugs (e.g. ["sec-form-d","sec-13f"]), the router then picks only from tools in those packs. Omit for the default full-
  • ask_pipeworx_beta9 params

    Beta version of ask_pipeworx: identical universal router (same 7,625 tools, same arguments, same response shape) with candidate routing improvements enabled live whenever one is under test. No candidate is active right now (the last was retired on outcome evidence 2026-07-26), so this currently matches ask_pipeworx exactly. Use it exactly like ask_pipeworx when you want the newest routing; results are compared against the stable router to decide what merges. Falls back to nothing, this IS a full working router, just the experimental edge.

    Show parameters
    • questionstringrequiredYour question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases.
    • querystringAlias for question.
    • qstringAlias for question.
    • promptstringAlias for question.
    • textstringAlias for question.
    • inputstringAlias for question.
    • askstringAlias for question.
    • messagestringAlias for question.
    • packsarrayOPTIONAL. Restrict routing to these pack slugs (e.g. ["sec-form-d","sec-13f"]), the router then picks only from tools in those packs. Omit for the default full-
  • ask_pipeworx_grounded9 params

    Hallucination-resistant answer mode for high-stakes reads. Same routing as ask_pipeworx, picks the right tool from 7,625 across 2031 sources, fills arguments, fetches the data, then EXTRACTS the answer using ONLY what the tool result contains. Returns {answer, evidence (verbatim quote), confidence, source, fetched_at, refusal_reason:null} on success, OR an explicit refusal {answer:null, refusal_reason:"not_in_source"|"no_tool_match"|"tool_error"|"data_truncated"|"llm_error"} when the data doesn't directly answer. An "llm_error" also carries refusal_cause ("wall" = our time budget ended before any model call was made; "route"|"threw"|"unparseable"|"wall_after_failure" = a model call failed); refusal_reason itself is unchanged. Use whenever an answer will be quoted, cited, or acted on, and the agent must not invent facts (financial verdicts, legal claims, medical lookups, public statements). Costs one extra LLM call vs ask_pipeworx, prefer ask_pipeworx for casual lookups.

    Show parameters
    • questionstringrequiredYour question in natural language. Accepts query, q, prompt, text, input, ask, message as aliases.
    • querystringAlias for question.
    • qstringAlias for question.
    • promptstringAlias for question.
    • textstringAlias for question.
    • inputstringAlias for question.
    • askstringAlias for question.
    • messagestringAlias for question.
    • prefer_toolstringRun this exact tool instead of letting the router choose, use a name from a previous answer's alternatives[]. Arguments are still filled from your question. Unk
  • search_within3 params

    Semantic search INSIDE a fetched record. Pass the text you already pulled (e.g. a SEC 10-K body, an article, a long tool result) plus a natural-language query; get back the top-N passages with character offsets and similarity scores. Use when the record is too big to cram into the prompt, search_within saves context, returns only the passages that matter, and every passage carries an offset so the agent can verify a verbatim quote. Pairs with ask_pipeworx_grounded: fetch with the gateway, ground over the relevant passages instead of the whole document. BGE-base-en embeddings + cosine over 500-char overlapping windows; cap is 200K chars (longer inputs are truncated and flagged).

    Show parameters
    • textstringrequiredThe document text to search inside (max ~200K chars).
    • querystringrequiredNatural-language query, what passages do you want? E.g. "supply-chain risk", "fiscal year 2024 revenue", "drug interactions with warfarin".
    • limitnumberMax passages to return (1-20, default 5).
  • deep_research9 params

    ACCOUNT REQUIRED (free, sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan). If you are not signed in, use ask_pipeworx instead, it works on every tier. Grounded multi-source research across Pipeworx's 2031 STRUCTURED data sources (SEC filings, FRED/BLS economics, FDA, USPTO patents, markets, science, government records, etc.) in ONE call, this is NOT open-web search. Decomposes your question into focused facets, routes each to the right one of 7,625 tools IN PARALLEL, and returns a findings packet: verbatim evidence + confidence + source + fetched_at + a stable pipeworx:// citation per finding, with explicit gaps[] for facets the data couldn't answer (never invented). Best for broad/multi-part questions over structured data ("compare X and Y's regulatory + financial exposure", "research the filings + market picture for ACME"). For a single lookup use ask_pipeworx (one LLM call, not many). For BREAKING or colloquial CURRENT-NEWS / "what's the world saying about X" topics, prefer ask_pipeworx, it routes to live news APIs and the *-news-feeds packs; deep_research returns mostly empty gaps[] when the topic isn't in the structured catalog. Second-hop iteration: depth:"standard" re-angles unanswered gaps (gap recovery); depth:"thorough" additionally chases the best leads from the first pass, so multi-step questions resolve in one call. Every finding carries a `hop` field and a citation_uri, a resolvable pipeworx:// record URI, present only when the source emits one that resources/read can actually serve, so a citation you get back is always fetchable. "standard" and "thorough" also return contradictions[] flagging findings that disagree. Large records are semantically excerpted to the passages relevant to each facet (not head-truncated), so answers deep in a long filing/series aren't missed. Expect 15-60s (thorough with its follow-up + contradiction pass: up to ~90s).

    Show parameters
    • questionstringrequiredThe research question, in natural language. Broad/multi-part is fine, decomposition is the point. Accepts query, q, prompt, text, input, ask, message as aliases
    • querystringAlias for question.
    • qstringAlias for question.
    • promptstringAlias for question.
    • textstringAlias for question.
    • inputstringAlias for question.
    • askstringAlias for question.
    • messagestringAlias for question.
    • depthstringHow many facets to research in parallel: quick=3 (single hop), standard=3 (default; adds a gap-recovery hop that re-angles unanswered facets + a contradictions[
  • discover_tools6 params

    Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real estate, ClinicalTrials, USPTO patents, weather, news, crypto, stocks. Returns the top-N most relevant tools with names, descriptions, and full input schemas (with curated examples), each result is ready to call directly, no second schema lookup needed. Call this FIRST when you have many tools available and want to see the option set (not just one answer).

    Show parameters
    • querystringrequiredNatural language description of what you want to do (e.g., "analyze housing market trends", "look up FDA drug approvals", "find trade data between countries").
    • taskstringAlias for query.
    • qstringAlias for query.
    • descriptionstringAlias for query.
    • searchstringAlias for query.
    • limitnumberMaximum number of tools to return (default 20, max 50)
  • resolve_entity3 params

    "What's the ticker for..." / "find the CIK for..." / "what's the LEI for..." / "what's the RxCUI for..." / "look up the ID for..." / "what is X's official identifier" / "who owns X" / "is X a subsidiary of Y", resolve a user-spoken NAME to the canonical/official identifiers other tools require as input. Use FIRST whenever you have a name but need an ID. SUPPORTED TYPES: "company" (cross-source identity spine: 10-digit CIK + ticker + company_name from SEC EDGAR, legal-entity LEI from GLEIF with parent/ultimate-parent/children ownership when the LEI resolves, and security FIGI from OpenFIGI, by exact ticker map when a ticker is implied, and otherwise by name search, so NON-EQUITY instruments that never have a ticker (municipal and corporate bonds, notes, authority debt) DO resolve here; when a name matches more than one instrument it asserts nothing and returns `figi_candidates` to pick from, which is the correct answer to an issuer name that does not identify a single bond; every identifier is labelled with the source that established it, and an identifier that could NOT be resolved is stated explicitly under `unresolved` rather than omitted, accepts ticker, CIK, ISIN, LEI, or company name as input; an ISIN like "CH0038863350" resolves to the LEGAL ENTITY that issued the security via the GLEIF ISIN-to-LEI mapping, covering non-US issuers EDGAR cannot reach), "drug" (returns RxCUI + ingredient + brand from RxNorm + pipeworx://rxnorm/concept/{rxcui} citation; accepts brand or generic name). LEI/FIGI enrichment degrades gracefully, if GLEIF or OpenFIGI is unavailable, the EDGAR identifiers still return. Each call cascades through several lookup endpoints internally, using resolve_entity replaces 2-3 manual lookups.

    Show parameters
    • typestringrequiredEntity type: "company", "drug" or "lei" (a 20-character LEI; "company" also recognises an LEI by its check digits).
    • valuestringrequiredFor company: ticker (AAPL), CIK (0000320193 or 320193), LEI (HWUPKR0MPOU8FGXBT394), or name. A bare number is read as an SEC CIK only as 320193 or 0000320193; w
    • countrystringOPTIONAL ISO 3166-1 alpha-2 of the country whose business register you mean ("NO", "FI", "JP", "GB", "FR", "EE", "BR"). Narrows the national-register fan-out an
  • compare_entities2 params

    "Compare X and Y" / "X vs Y" / "X versus Y" / "which is bigger / better / larger / more profitable" / "rank these companies" / "head to head", side-by-side comparison of 2-5 companies or drugs in ONE parallel call. ALWAYS PREFER over sequential single-pack lookups when comparing entities. type="company" pulls LATEST 10-K revenue + operating income + net income + cash + long-term debt from SEC EDGAR/XBRL (off-calendar fiscal years handled correctly, AAPL Sep, NVDA Jan, etc.). type="drug" pulls FAERS adverse-event counts, FDA approval counts, active trial counts. Results sorted by primary metric so "largest" / "most" / "biggest" reads off the top of the response. Returns paired data + pipeworx:// citation URIs per entity. Replaces 8-15 sequential lookups.

    Show parameters
    • typestringrequiredEntity type: "company" or "drug".
    • valuesarrayrequiredFor company: 2-5 tickers/CIKs (e.g., ["AAPL","MSFT"]). For drug: 2-5 names (e.g., ["ozempic","mounjaro"]).
  • subscribe3 params

    Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: "sec_8k" (8-K filings matching ticker + item codes, e.g. items:["5.02"] = officer change), "polymarket_edge" (Polymarket↔Kalshi cross-venue mispricings, params:{topic:"fed"}), "fred_series" (new FRED observations, params:{series_id:"UNRATE"}), "patent_grant" (new USPTO grants for an applicant), "clinical_trial" (new/updated ClinicalTrials.gov studies), "form_d" (new SEC Form D fundraise notices, params:{state?, industry?, min_amount?, exemption?}, all optional), "news_keyword" (GDELT keyword news alerts, metadata+link only, params:{query, lang?, domains?}), "job_post" (new public job-board postings, params:{ats?, board_token?} or {domain?}, plus optional title_query/location_query), "tool_diff" (re-runs any read-only tool on a schedule and fires on change, params:{tool, args?, fields[], schedule}), "new_entity" (new business registrations from a state business-entity registry, params:{state:"CO", name_query?, entity_type?}), "tech_change" (a watched domain's website technology stack adds or drops a technology, params:{domains:["acme.com"], technologies?}). Delivery channels: feed (always on, pull via recent_alerts or GET registry.pipeworx.io/alerts.json), and optionally email (set delivery:{email:"you@x.com"}) or sms (delivery:{sms:"+15551234567"}, phone must be verified at /account first; 10/day cap).

    Show parameters
    • typestringrequiredSubscription type.
    • paramsobjectrequiredType-specific filter. sec_8k: {ticker:"AAPL", items?:["5.02","1.01"]}. polymarket_edge: {topic:"fed", min_spread_bps?:500}. fred_series: {series_id:"UNRATE"}. p
    • deliveryobjectOptional delivery channels in addition to the always-on persistent feed. {email:"you@x.com"} sends a templated alert per fired event. {sms:"+15551234567"} sends
  • unsubscribe1 param

    Cancel a subscription by id. Ownership is enforced, you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts.

    Show parameters
    • idstringrequiredSubscription id (uuid) returned by subscribe.
  • list_subscriptions1 param

    List the caller's active subscriptions. Returns id, type, params, created_at, last_fired_at, fire_count for each. Use this to review what you're monitoring before adding more or to find an id to cancel.

    Show parameters
    • include_inactivebooleanInclude cancelled subscriptions in the response (default false).
  • recent_alerts5 params

    Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed, each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp). Set mark_read:true to flag returned events read so the next call only shows newer ones. Polls work fine; the same feed is also at GET registry.pipeworx.io/alerts.json for scripts and dashboards.

    Show parameters
    • typestringOptional, filter to one subscription type.
    • sincestringOptional ISO timestamp, return events fired_at >= this time.
    • limitnumberMax events to return (1-200, default 50).
    • unread_onlybooleanReturn only events where read_at is null (default false).
    • mark_readbooleanFlag the returned events read in the same call (default false).
  • entity_profile3 params

    "Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER", full cross-source profile of a US public company in ONE parallel call. ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view. Fans out across SEC EDGAR, XBRL, USPTO patents, federal contracts (USAspending), FDA-licensed biologics (Purple Book), H-1B hiring (DOL LCA), news and GLEIF, and returns: cik + company_name (+ resolved_from/resolved_to when `value` was a name); recent_filings (up to 5 with pipeworx://edgar/company/{cik}/filings/{accession} URIs); fundamentals (the latest ANNUAL Revenues, NetIncomeLoss, Cash, diluted EPS, capex and operating cash flow, each with its period_end, SEC form and the accession of the filing it came from, plus EntityCommonStockSharesOutstanding, which is the newest COVER-PAGE share count the filer has published rather than an annual one, so its period_end is a cover date after the quarter closed and it is the right per-share denominator; a filer tagging a fallback concept appears under the name of that tag instead, e.g. PaymentsToAcquireProductiveAssets instead of PaymentsToAcquirePropertyPlantAndEquipment); patents (USPTO PatentsView API sunset May 2025, soft-fails until reactivated); federal_contracts (USAspending awards where the company is the recipient); fda_products (FDA-licensed biologics, vaccines, cell/gene therapies, from the Purple Book; a company with only small-molecule/generic drugs will show none here, that is expected, not a failure); hiring (H-1B sponsorship volume + salary range from DOL LCA filings); recent news mentions via GDELT -> GNews fallback; LEI via GLEIF. `sources_used` / `sources_failed` say which of these actually returned data for THIS company, an empty section is a real "no data", not a bug. `sources_skipped` is the third state: a leg we deliberately did NOT run, each entry

    Show parameters
    • typestringrequired"company" or "ticker", both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon.
    • valuestringrequiredTicker (e.g., "AAPL"), zero-padded CIK (e.g., "0000320193"), or company name (e.g., "Moderna"). A NAME now resolves through the national business registers as w
    • countrystringOPTIONAL ISO 3166-1 alpha-2 of the business register you mean ("NO", "FI", "GB", "JP", "FR", "EE", "BR"). Only affects a NAME lookup, and is often what separate
  • recent_changes3 params

    "What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple", change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since `since`), GDELT -> GNews fallback (news mentions in window, GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). `since` accepts ISO date ("2026-04-01") or relative shorthand ("7d", "30d", "3m", "1y"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.

    Show parameters
    • typestringrequiredEntity type. Only "company" supported today.
    • valuestringrequiredTicker (e.g., "AAPL") or zero-padded CIK (e.g., "0000320193").
    • sincestringrequiredWindow start, ISO date ("2026-04-01") or relative ("7d", "30d", "3m", "1y"). Use "30d" or "1m" for typical monitoring.
  • validate_claim2 params

    "Is it true that..." / "fact check" / "verify the claim that..." / "did X really..." / "was Y actually..." / "confirm or refute" / "true or false", natural-language claim verification against authoritative sources. Use whenever the agent needs to check whether something a user said is factually correct. Company-financial claims (revenue, net income, cash for public US companies) verify via the structured SEC EDGAR + XBRL fast path with exact percent-delta math; ANY OTHER factual claim (macro statistics, rates, prices, drug data, records) automatically falls through to the grounded pipeline, routed to the right live source, answered with verbatim evidence, then judged. Returns a verdict (confirmed / approximately_correct / refuted / inconclusive / unsupported / could_not_verify), the grounded or structured actual value with pipeworx:// citation, and reasoning. IMPORTANT for callers: could_not_verify means the check did not happen (our LLM or source failed) and carries verification_error{stage,detail}, it is NOT evidence for or against the claim, and must not be shown as one. unsupported means we looked and cover no source for it. Replaces 4-6 sequential calls (NL parsing -> entity resolution -> data lookup -> comparison).

    Show parameters
    • claimstringrequiredNatural-language factual claim, e.g., "Apple's FY2024 revenue was $400 billion" or "Microsoft made about $100B in profit last year".
    • tolerance_pctnumberMax percent deviation still graded approximately_correct (0.5-50). Overrides the tolerance implied by the claim wording, set 1-2 for hallucination detection whe
  • company_facts9 params

    TYPED, DETERMINISTIC financial facts for a US public company for an EXPLICITLY NAMED reporting period, "Apple revenue for fiscal 2023", "Walmart net income FY2026 Q3", "Microsoft cash at the end of fiscal 2024". PREFER OVER entity_profile / get_company_financials whenever the period matters: those answer "the most recent figures" and will happily hand back FY2025 when you asked about FY2019, and neither separates a discrete quarter from a year-to-date figure. This one refuses instead, it NEVER substitutes the latest period for the period requested, NEVER returns 0 for missing data, NEVER lets a 9-month YTD number answer a quarterly question, and NEVER converts a currency. Every answer carries the exact us-gaap concept it came from, what that concept MEASURES (NetIncomeLoss excludes non-controlling interests, ProfitLoss includes them, not synonyms), the accession number and a link to the filing on sec.gov, the restatement trail of any superseded figures, and a contract + derivation version to pin against. Fiscal periods are the FILER'S OWN, anchored on their fiscal-year end, so Walmart's year ending 2026-01-31 is FY2026 and Apple's ending 2025-09-27 is FY2025. Attributes: revenue, net_income, cash, gross_profit, operating_income, eps_diluted, capex, operating_cash_flow, long_term_debt, shares_outstanding (the dei COVER-PAGE share count, so its period end is the cover date, after the quarter closed, that is the most current count the filing carries). Units are not all USD: shares_outstanding is in `shares` with currency null, eps_diluted in `USD/shares`. A discrete quarter the filer never filed, every Q4, and Q2/Q3 of cash-flow lines, which are filed year-to-date, is DERIVED as YTD(q) minus YTD(q-1) and comes back with `reported: false`, the subtraction named in `derivation` (fy_minus_9m / ytd_9m_minus_6m / ytd_6m_minus_3m) and both legs with their filings in `derived_from`; test `reported` if you will only accept a figure lifted from a filing. Per-share and balance-s

    Show parameters
    • companystringrequiredTicker ("AAPL"), 10-digit CIK ("0000320193"), or company name. A name that matches two filers equally well returns status "ambiguous" with both named rather tha
    • attributestringrequiredWhich figure. "revenue" = total consolidated revenue; "net_income" = net income (loss); "cash" = cash and cash equivalents at the period end; "gross_profit"; "o
    • periodobjectrequiredThe reporting period, stated explicitly. There is no default and no "latest", that is the point of this tool.
    • freshnessstringcached (default) permits an eligible stored answer; fresh requires an upstream refresh and never silently falls back to stale data.
    • max_agenumberMaximum age in seconds of the upstream publication, not our fetch. Older or undated facts are withheld.
    • as_ofstringPast ISO timestamp with timezone. Replay the latest answer actually recorded by that instant; no invented history or live fallback.
    • restatementstringDefault "as_amended", the latest filed figure for the period, with everything it superseded listed. "as_originally_reported" takes the first filing instead.
    • basisstringOnly "consolidated" in v1. Segment and product-level figures are XBRL-dimensioned and are not reachable through this contract at any concept.
    • exclude_publishersarrayPublisher ids forbidden for fact retrieval: sec, fmp, alphavantage. Case and surrounding whitespace are normalized; unknown ids are refused. Excluding sec curre
  • company_register_search4 params

    Search the NATIONAL BUSINESS REGISTERS by company name and get the register's own id back, a Companies House number, a Norwegian organisasjonsnummer, a Finnish business id, a SIREN, a Japanese corporate number, an Estonian registry code, a CRO number, a CNPJ, a US state entity number, or an LEI. Use this when you want the OFFICIAL REGISTERED ENTITY. Registers searched: Companies House (GB), Enhetsregisteret (NO), PRH/YTJ (FI), Sirene (FR), 法人番号公表サイト (JP), RIK e-Business Register (EE), the Companies Registration Office (IE), the US STATE business registers (one per state the sos-entities pack covers; pass country "US", optionally with a two-letter `state`), and the GLEIF LEI crosswalk, which reaches jurisdictions we have no register pack for (DE, SE, AU, SG...). US EXAMPLE: {name: "IPQualityScore LLC", country: "US", state: "FL"} returns the Florida entity number. A US company is formed in ONE state and may also be registered as a FOREIGN entity in others, so without `state` every covered state register is searched and the several registrations of one company come back as ONE match, which says whether the register it names is the company's own or a foreign registration and names the state it was formed in (Browserbase Inc. is a Delaware corporation found in New York). A state we hold no register for (Delaware, California and most others) is SAID so, and is answered from GLEIF (the state file number GLEIF holds for the company, returned as `gleif_state_registration` and labelled as GLEIF's copy, not a lookup in the state's register) and SEC EDGAR (the registrant's state of incorporation, `sec_state_of_incorporation`), with the counts and what a miss means in `state_coverage.indirect_sources` and the explanation; the covered registers are also searched for foreign registrations of a company formed there. A company with neither an LEI nor an SEC filing is not found, so a miss is never proof it is not a company of that state. With `state`, `match_status: "matched"` means

    Show parameters
    • namestringrequiredThe company name as you have it, in its own script. Pass it VERBATIM, do not strip the legal form ("Oyj", "AS", "株式会社", "Ltd"): in Japanese the form is a PREFIX
    • countrystringOPTIONAL ISO 3166-1 alpha-2 of the register you mean ("GB", "NO", "FI", "FR", "JP", "EE", "IE", "US", "BR"). Narrows the fan-out, and is frequently the differen
    • statestringOPTIONAL two-letter US state ("FL", "NY", "CO"...), with country "US" (implied when country is absent). It means the state where the company is registered or wa
    • limitnumberMaximum candidates to return, 1-50 (default 10). Does not change which registers are asked, only how many rivals come back.
  • scan_dependency2 params

    Composite "should I add this npm package to my project" check in ONE call, fans out across deps.dev (license + advisories + version history) and bundlephobia (gzipped/minified bundle size, dependency count, ESM/tree-shake support). Use whenever an agent asks "is X safe / popular / small" or "what does adding lodash cost me". Returns a summary block (is_latest, license, published_at, advisory_count, bundle_kb_min, bundle_kb_gz, dependency_count, has_esm, tree_shakeable), per-advisory detail, links, and a list of recent alternative versions. NPM ecosystem only in v1; PyPI / Maven / Cargo / Go fall under deps.dev:version directly. Partial failures degrade gracefully, bundlephobia's first measurement on a new version can take 5-30s; sources_failed will list it if it times out, the rest still returns.

    Show parameters
    • packagestringrequirednpm package name. Scoped packages (e.g. "@types/node") are accepted.
    • versionstringSpecific version to check (e.g., "18.3.1"). Defaults to the latest published version when omitted.
  • bet_research3 params

    Research a Polymarket bet by pulling the relevant Pipeworx data for it in one call. Pass a market slug ("will-kristi-noem-win-the-2028-republican-presidential-nomination"), a polymarket.com URL, or a question text. A dated slug ("...-by-june-30-2026") still resolves after it settles, the resolver retries a closed-market lookup rather than giving up on the bare one, so either dated or undated works; prefer whichever slug you actually have. The tool resolves the market, classifies the bet, fans out to category-specific data packs in parallel, and returns an evidence packet + simple market-vs-model comparison. Use for "should I bet on X", "what does the data say about Y", or "is there edge in Z". CLASSIFIERS: crypto_price, fed_rate, geopolitical, sports, sports_championship, drug_approval, election_candidate, tech_launch, space_launch, corporate, corporate_earnings, corporate_event, public_figure_speech, weather, other. FAN-OUT EXAMPLES: BTC bet -> coingecko + fred + gdelt+gnews; Fed bet -> fred (DFEDTARU + EFFR + CPIAUCSL) + kalshi_macro (KXFED implied probs) + recent_fed_actions (federal-register rules, last 365d); Hormuz bet -> imf_portwatch + airspace + gdelt; Yankees WS -> mlb_stats_standings + parent_event partition + news; hottest-year bet -> climate_projection_nyc + gistemp_latest (NASA global anomaly, rank since 1880) + news; NVDA-vs-AAPL -> finnhub get_quote + edgar shares-outstanding (derived market cap) + edgar filings + news. RESPONSE SHAPES: result.market carries best_bid/best_ask/spread_pp/liquidity/price_change_1h/1d/1w; result.analysis carries model_probability/edge_pp/kelly_fraction_half when a closed-form model fires PLUS a 24h-move warning ("Market moved X.Xpp in 24h, comparable to model edge, your edge may already be priced in") when relevant; result.evidence is keyed by source. RESOLVER CONTRACT: result.market_match_confidence ∈ {high, medium, low, none}, market_match_score (0-1 token-overlap), market_match_alternatives[] (other candidate markets

    Show parameters
    • marketstringrequiredPolymarket slug ("will-kristi-noem-win-the-2028-republican-presidential-nomination"), full URL ("https://polymarket.com/event/..."), or question text ("Will Bit
    • depthstringquick = 2-3 evidence sources, thorough = full fan-out. Default thorough.
    • include_rawbooleanDefault false. When false (recommended), FRED/FDA/GDELT/Federal-Register evidence is summarized to the few fields agents actually use, keeps responses under ~20
  • polymarket_arbitrage2 params

    Find arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks. Call with NO args for a `trending_scan` of the top ~200 markets by weekly volume; pass `event` for the strongest per-event partition_check, or `topic` for a themed cross-event scan. `event` (recommended for a specific market): pass a Polymarket event slug like "fed-decision-may-2026" or "when-will-bitcoin-hit-150k"; walks child markets, checks date-axis / threshold-axis ordering AND computes the partition_check (sum of YES prices across mutually-exclusive legs, should ≈1; deviations >3pp emit a BUY/SELL EVERY LEG signal). `topic` (for cross-event scanning): pass a seed question like "Strait of Hormuz traffic returns to normal" or "Fed rate decision"; searches related events across the platform, flattens markets, runs the comparator on the union. Cross-event mode catches "...by May 31" vs "...by Jun 30" patterns that single-event misses. SEMANTIC ANCHOR: cross-event pairs require ≥0.30 Jaccard similarity on question tokens (prevents Powell-Fed-Pause being paired with Powell-DOJ-probe); skipped_low_similarity surfaces the rejected pair count. PARTITION FILTER: drops will-person-X / will-manager-Y / will-someone-else- placeholder slugs; partitions with >20% placeholder fraction return null arb signal. Response: opportunities[] (gap_pp, suggested_trade, reasoning, monotonicity violation context), and in event mode partition_check{sum_yes_prices, gap_from_1, placeholders_filtered, suggested_trade}. FEES: every opportunities[] row and partition_check.arbitrage carry edge_pp_gross (== gap_pp / overround_pp), fees_pp, edge_pp_net, net_positive, plus polymarket_fee_pp, fee_basis and fee_categories[]. BOTH cost components are modeled: Polymarket's own per-category TAKER FEE (fee = shares x rate x p x (1-p), rates crypto 0.07 / sports-economics-culture-weather-other 0.05 / finance-politics-mentions-tech 0.04, geopolitics and world events fee-free; verified against Polymarket's own do

    Show parameters
    • eventstringSingle-event mode (use this if you know the specific Polymarket event): event slug like "fed-decision-may-2026" or "when-will-bitcoin-hit-150k". Full Polymarket
    • topicstringCross-event mode (use this if you want to scan related events across the platform): a topic or seed question like "Fed rate decision" or "Strait of Hormuz traff
  • polymarket_edges9 params

    Scan top Polymarket markets and return opportunities where Pipeworx data disagrees with market price. Built for "what should I bet on today", agents discover opportunities without paging hundreds of markets. FIVE MODEL FAMILIES grouped into three response segments under by_segment: (1) MODEL_DRIVEN, crypto_price (lognormal barrier from 90d FRED log-returns) and news_momentum (GDELT 7d/21d article-volume ratio, soft signal w/ halved Kelly). (2) STRUCTURAL_ARBITRAGE, partition_overround on mutually-exclusive events; per-leg favorite-longshot bias correction with per-sport α (tennis 1.02, soccer 1.10, MMA 1.15, default 1.0); placeholder-slug filter drops will-person-X / will-team-Y / will-manager-Z / will-someone-else- backstops; partitions with >20% placeholder fraction skipped entirely. (3) CONCENTRATED_LONGSHOT, basket trade when one leg ≥75% AND ≥2 longshots ≤8% AND portfolio return ≥25:1; rare-by-design (gates relaxed Run 8 from prior 85%/5%/50:1). EVERY OPPORTUNITY carries edge_pp_net (net of slippage AND Polymarket's own taker fee, fees_pp_applied itemises the fee component; see fees.ts for the published per-category schedule), kelly_fraction + kelly_fraction_half (capped at 0.25), market.liquidity, market.spread_pp, market.volume, plus a 24h-move warning ("Market moved X.Xpp in 24h") when the recent move alone exceeds the edge, your edge may already be in the price. TRADEABLE-EDGE KNOBS: min_liquidity / max_spread_pp drop opportunities where edge isn't realizable; min_partition_leg_kelly filters partitions by best per-leg Kelly. RESPONSE TOP-LEVEL: by_segment{model_driven,structural_arbitrage,concentrated_longshot}, fed_candidates/fed_note (Fed bets surface here, excluded from ranking, 1m-T vs EFFR signal is unreliable at meeting-month horizons without paid OIS/SOFR-futures data), and _diagnostics{concentrated_longshot:{...funnel counters},category_counts,filter_skips} so callers can see WHY a segment is empty (top-N stale, all candidates failed gates, knob dro

    Show parameters
    • windowstringPolymarket volume window to filter markets. Default 1wk.
    • limitnumberTop N edges to return after ranking. Default 10, max 25.
    • min_edge_ppnumberMinimum |edge| in percentage points to include (default 0.5). Edge is evaluated NET of slippage and Polymarket's own taker fee.
    • slippage_ppnumberAssumed execution slippage in percentage points per leg (default 0.3), for bid/ask + thin depth cost that a last-trade price does not show. Subtracted from raw
    • category_filterstringComma-separated list to restrict the output: "model_driven" (crypto_price + news_momentum), "structural_arbitrage" (partition_overround), "concentrated_longshot
    • min_kellynumberMinimum half-Kelly fraction (as decimal, e.g. 0.005 = 0.5% of bankroll) to include single-leg opportunities. Default 0 (no filter). Skips opportunities that are
    • min_partition_leg_kellynumberMinimum BEST per-leg half-Kelly fraction across a partition_overround opportunity's top_legs (or longshot_basket legs). Default 0 (no filter). Partition arbs al
    • min_liquiditynumberTradeable-edge filter. Minimum $ liquidity on the representative market (or for partition_overround, on at least one top_leg). Default 0 (no filter). Set to 500
    • max_spread_ppnumberTradeable-edge filter. Maximum bid/ask spread in percentage points on the representative market. Default null (no filter). Set to 2 to require tight books, anyt
  • polymarket_kalshi_spread3 params

    Cross-venue spread between Kalshi and Polymarket for the same resolving question. The two venues sometimes price the same outcome 2-25pp apart because their participant pools differ, when the bet shapes are equivalent that delta is a real signal, when they aren't the tool says so. TWO MODES: (1) `topic`, 11 pre-mapped macro subjects ("fed", "btc", "eth", "cpi", "gdp", "sp500", "recession", "next_pope", "next_uk_pm", "next_israel_pm", "2028_president") auto-fetch the matching event on each venue. You do NOT have to use those exact keys: the topic is resolved through aliases and keywords, so "bitcoin", "fed rate decision", "inflation", "s&p 500" and "next pope" all land on the right subject, and `resolution.topic_matched_by` tells you whether it was an exact key, a known alias, a phrase found inside a longer question, or a single-keyword guess, treat "phrase" and "token" as a GUESS at what you meant. An unresolvable topic returns error:"mapping_failed" with mapping_stage:"topic_unrecognized" and known_topics[]; it never silently falls back to a default subject. (2) explicit `kalshi_event_ticker` + `polymarket_event_slug` for custom pairings, BOTH modes run the identical token-overlap matcher, so the same disclosures apply to both. `resolution` is returned in BOTH modes and says how each side's identifier was picked (which Kalshi series was queried, how many events came back, whether the chosen one had quoted markets; which Polymarket search query ran and why that event won). Fleet #2064: when two Polymarket candidates tie on resolution time `polymarket_selected_by` now SAYS so, names every tied slug, names the tie-break that actually decided it (the candidate whose metric_type matches the Kalshi series, else lexicographic slug order), and states whether the winner's metric matches the Kalshi series, it used to assert "picked the soonest-resolving" byte-identically on calls that returned DIFFERENT events, because the tie was settled by upstream fetch arrival order. RES

    Show parameters
    • topicstringSubject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president, plus the 15-minu
    • kalshi_event_tickerstringExplicit Kalshi event ticker, e.g. "KXFED-26OCT". Overrides the topic-mapped Kalshi side.
    • polymarket_event_slugstringExplicit Polymarket event slug, e.g. "fed-decision-in-june-825". Overrides the topic-mapped Polymarket side.
  • polymarket_fill_risk4 params

    Realizable-vs-theoretical edge check against live CLOB order-book depth, AND Polymarket's own taker fee, which is never zero and is folded in rather than left for you to add (fleet #3446: r/PredictionsMarkets flagged a "clean" fill that quietly omitted it as optimistic in the direction that loses money). REQUIRES one of `market` (single-market mode) or `event` (basket/partition mode). SINGLE-MARKET: pass a market slug/URL + side (buy_yes|sell_yes|buy_no|sell_no, default buy_yes) + size_usd (default 1000, max spend on buys, target proceeds on sells); walks the ladder and returns top_of_book, vwap_fill_price, slippage_pp, shares_filled, max_fillable_usd, verdict (clean|degraded|cannot_fill), fee_schedule ({category, taker_rate, exponent, maker_rebate_rate, fees_enabled, basis}, read off THIS market, never assumed free), fee_usd/fee_pp at the actual VWAP fill, breakeven_win_rate_taker (the win probability your side needs just to cover price + fee, ~51.8% on a 50c crypto taker fill, not 50%), breakeven_win_rate_maker (no fee charged to makers, any rebate is in fee_schedule.maker_rebate_rate), and all_in_cost_pp = slippage_pp + fee_pp. BASKET: pass an event slug/URL + side (sell_yes = capture overround by selling every leg, buy_yes = capture underround; default auto from partition sum) + size_usd interpreted as settlement notional S (shares per leg; each share pays $1); returns theoretical_sum vs realizable_sum (top-of-book vs VWAP across all legs), capture_ratio and profit_usd, both NET of every leg's own Polymarket taker fee (capture_ratio_gross/profit_usd_gross keep the pre-fee figures; per_leg[].fee_usd itemizes each leg, summed as fees_usd_total), per-leg fill detail, thin_legs[], max_clean_notional_usd, and forced_directional_risk naming the legs most likely to strand you unhedged. USE THIS before acting on any polymarket_arbitrage SELL/BUY-EVERY-LEG signal or any polymarket_edges trade above ~$500, theoretical overround on thin books is not capturable, and partial

    Show parameters
    • marketstringSingle-market mode: market slug or full polymarket.com URL.
    • eventstringBasket mode: event slug or full polymarket.com URL, checks every leg of the partition.
    • sidestringSingle-market: buy_yes | sell_yes | buy_no | sell_no (default buy_yes). Basket: sell_yes | buy_yes (default auto, sell if partition sum > 1, buy if < 1).
    • size_usdnumberSingle-market: USD to spend (buys) or target proceeds (sells). Basket: settlement notional, shares per leg, each paying $1 at resolution. Default 1000, clamp 10
  • polymarket_edge_tracker2 params

    Edge persistence and decay telemetry built from daily polymarket_edges snapshots. Answers "how long has this edge existed and is it shrinking?", a fresh wide edge and a 3-week-old wide edge are different trades (the latter is wide for a reason nobody is willing to take). Args: days (lookback, default 14, max 30), window (snapshot family, default "1wk"). RESPONSE: tracked[] = every opportunity in the LATEST snapshot with its full edge_pp_net time-series across prior snapshots, first_seen, trend (new | widening | stable | decaying) and decay_pp_per_day (both computed on |edge_pp_net|, the value itself is signed by trade direction, negative = SELL YES); expired[] = opportunities that appeared in earlier snapshots but are GONE from the latest (closed, resolved, or arbed away) with their lifespan_days, the median lifespan is your competition clock; snapshot_dates[] = which days actually have data (snapshots are written when polymarket_edges runs on a cache-miss, so gaps mean nobody scanned that day). LIMITS: history depth is bounded by the 60-day snapshot TTL and starts from when snapshotting was enabled; decay numbers come from daily closes of edge_pp_net (net of default slippage AND Polymarket's own taker fee, see polymarket_edges), not intraday.

    Show parameters
    • daysnumberLookback in days (default 14, clamp 2-30).
    • windowstringWhich polymarket_edges window family to read snapshots for: 24hr | 1wk | 1mo (default 1wk).
  • kalshi_weather_edge5 params

    Prices Kalshi daily high-temperature markets against the NWS forecast for the market's OWN settlement station, and measures whether that forecast actually beats the market. Two modes. LIVE (default): returns the full strike ladder for one city and settlement date with market_prob (mid), forecast_prob, and edge_pp per strike, plus the settlement clause verbatim. BACKTEST (`backtest_days: N`): scores an archived gridded forecast against the market on settled days and returns brier_market vs brier_forecast with a plain-English `verdict`, so the edge is MEASURED rather than asserted. READ THE WARNINGS, they are not boilerplate. (1) These markets DO NOT settle on the NWS. They settle on The Weather Company (weather.com) at a Kalshi station code such as CLINYC, which the response quotes verbatim; so part of every edge_pp is NWS-vs-Weather-Company disagreement about the same day at the same station, which is not mispricing and not tradeable. `settlement_vs_forecast_basis_f` from backtest mode is that part as a number. (2) The station is DERIVED from the settlement clause, never from the city name: Chicago settles at MIDWAY and New York at CENTRAL PARK, so a city-centre forecast would misprice a whole ladder. A station that cannot be resolved yields rows with no forecast and a reason, never a guessed coordinate. (3) forecast_prob assumes a normal distribution around the NWS high whose width is ASSUMED, not fitted (stated in `distribution_assumption`), run backtest mode to see whether it is calibrated. (4) edge_pp is gross: no Kalshi fees, no bid-ask. MEASURED RESULT, AND IT IS NOT THE FLATTERING ONE: on the first backtest (KXHIGHNY, 13 settled days to 2026-09-11, 58 market observations) the MARKET beat the forecast, Brier 0.1008 for the market against 0.1594 for the archived gridded forecast, lower being better. So on that sample there is NO forecast edge to sell, and a large edge_pp is more likely to be the model disagreeing with a better-informed market than an opportunit

    Show parameters
    • citystringCity to price, e.g. "nyc", "chicago", "los angeles", "miami", "austin", "houston", "denver", "philadelphia". Defaults to nyc. Unmapped cities return known_citie
    • series_tickerstringExplicit Kalshi series, e.g. "KXHIGHNY" or "KXHIGHTBOS" (Boston). Overrides `city`; use it for any of the 121 daily weather series not in the city list.
    • datestringSettlement date as YYYY-MM-DD. Defaults to the soonest open event. Daily weather markets open ~1-2 days ahead and close 05:00Z the next day.
    • market_typestring"high_temp" (default) | "precip". Precipitation markets return prices but no forecast_prob yet.
    • backtest_daysnumberRun measurement mode over the last N settled days (max 60) instead of pricing today. Returns brier_market vs brier_forecast, the settlement-vs-forecast basis, a
  • resolution_audit2 params

    Extract the settlement clause of a single Polymarket (.com or .us) or Kalshi market: who publishes the settling number (source), the clock time + timezone it is taken at (falling back to the market TITLE when the clause itself says "the time range specified in the title", e.g. Polymarket's 15-minute Chainlink TWAP family), the precision of the computation (e.g. "1-minute candle close" vs "60-second trailing average" vs "twap_60s_lookback"/"twap_30s_lookback" vs "election outcome"), comparison_basis, what is compared to what (end_average_vs_start_average | close_vs_open; orthogonal to precision, since venues can share this comparison shape while computing each endpoint differently), the evidence standard (official_source | consensus_reporting | any_credible_report | unspecified), and void_handling (cancellation/postponement settlement, reused verbatim from bet_research's cancellation_rule detector, not re-derived). Parses Polymarket's `description` field (fetched via polymarket_market, or via polymarket_us_search for the .us venue) or Kalshi's `rules_primary` + `rules_secondary` fields (fetched via kalshi_market) with regex + a small vocabulary, no LLM pass, so an unusual clause reports confidence:"low" rather than a guess. Pass `market` as a Polymarket slug/URL (either venue) or a Kalshi market ticker (e.g. "KXBTCD-26SEP1317-T66999.99"); a Kalshi EVENT ticker (e.g. "KXBTCD-26SEP1317") also works, it picks one representative market under that event, since the settlement mechanism is normally shared across all strikes/legs in one event. Use this before treating a polymarket_kalshi_spread row as a real arbitrage: two ladders that look alike can settle on different sources (Polymarket.com's Chainlink TWAP stream vs Kalshi/Polymarket US's CF Benchmarks BRTI), at different times, or with a different lookback window, this tool is how you check. Pair with resolution_diff to compare two markets directly. KNOWN GAP: idiosyncratic phrasing that doesn't match the vocabulary ret

    Show parameters
    • venuestringrequiredWhich venue to fetch the market from. "polymarket" is the offshore venue (polymarket.com); "polymarket-us" is the separate, CFTC-regulated polymarket.us venue,
    • marketstringrequiredPolymarket (.com or .us) market slug or URL, OR a Kalshi market ticker (preferred) or event ticker (falls back to a representative market under that event).
  • resolution_diff2 params

    Field-by-field diff of TWO markets' settlement clauses (one from each of `a` and `b`; either can be Polymarket .com, Polymarket US, or Kalshi), runs resolution_audit on both sides and compares source, settle time, precision, comparison_basis, and evidence standard. Returns `equivalent`: "true" only when both sides parsed with enough confidence to compare AND no field conflicts; "false" when a specific conflict was found (differing_fields names which, e.g. ["source","settle_time"] for a Polymarket Bitcoin market settling on Binance's 1-minute candle at noon ET versus a Kalshi KXBTCD market settling on CF Benchmarks' BRTI 60-second average at 5pm EDT, SAME asset, DIFFERENT contract; or ["source","precision"] for Polymarket.com's Chainlink 15-minute TWAP clause (precision "twap_60s_lookback") against Kalshi's 15-minute KXBTC15M clause (precision "60-second trailing average" off CF Benchmarks' BRTI), different source and a different lookback mechanism, even though BOTH compare an end-of-window average to a start-of-window average, so comparison_basis is EQUAL there and correctly NOT in differing_fields, verified live 2026-10-22, fleet #3447); "unclear" when one or both sides could not be confidently parsed (an absence of evidence is not evidence of equivalence, read raw_clause yourself in that case). comparison_basis is flagged as differing whenever both sides resolved one and they disagree, independent of whether source/precision also matched. Only flags source/evidence_standard as differing when BOTH sides gave a SPECIFIC comparable answer, a named source (e.g. "Associated Press, Fox News, NBC") against a generic one (e.g. Kalshi's "consensus of media organizations") is treated as the same evidence standard, not a conflict, since that is standard election-market boilerplate on both venues. Use this before sizing a polymarket_kalshi_spread pair as a real cross-venue arb, or standalone to sanity-check any two markets you suspect settle on different things.

    Show parameters
    • aobjectrequiredFirst market to compare.
    • bobjectrequiredSecond market to compare.
  • release_calendar_markets2 params

    JOIN of the official release calendar (econ data, the FOMC, FDA decisions, SEC rules) against LIVE Polymarket/Kalshi markets, which scheduled releases land in the next N hours, and which live markets resolve on them. This is a POSITIONING tool, not a speed product: results are cached like every other pack (≤ 60s TTL) and there is no push/webhook, do not use this to try to beat a release, use it to see what is coming and what is already priced. CATEGORIES: econ (CPI, Employment Situation/jobs report, GDP, PCE, PPI, retail sales, housing starts, jobless claims, via fred_release_dates per known release_id, since FRED's own cross-release calendar mostly returns recent actuals, not future dates), fed (the next FOMC meeting's rate decision, via fomc_calendar), fda (PDUFA action dates + FDA advisory-committee meetings, via pdufa_catalysts / fda_adcom_calendar), sec (SEC final rules whose own DATES clause names an effective date in the window, via federal-register recent_rules, usually finds nothing in a short window since SEC rules typically take effect 30-60 days out, which is an accurate answer, not a bug), court (ALWAYS EMPTY today, court-listener has no forward-looking scheduled-hearing calendar, only filing/termination dates, so this category returns zero releases with unsupported:true rather than fabricate one). Omit `categories` or pass "all" for every category. MATCHING AND ITS HONESTY CONTRACT: every release is returned even when it has ZERO matched markets, a release is never dropped just because nothing on Polymarket or Kalshi resolves on it (most FDA/SEC releases will show markets:[]; that is signal, not a gap). Every matched market carries resolves_on_this_release: "true" (the venue's own close/end date sits within ~36h of the release AND the question passed a subject filter, econ and fed only), "likely" (same subject filter, but the venue closes days away from the release date), or "unclear" (a keyword hit with no date to anchor against, always true for the f

    Show parameters
    • hoursnumberLook-ahead window in hours from now. Default 48. Capped at 720 (30 days), econ/fed releases are dated weeks apart, so a short window is often empty; widen rathe
    • categoriesstringComma or space separated subset of econ|fed|fda|sec|court, or "all" (default). E.g. "econ,fed" or "fda".
  • prediction_calibration6 params

    REALIZED win rate by shown price and minutes elapsed for short-horizon crypto up/down markets, net of taker fee, read from our own settled-outcomes archive, not from live prices. Answers the one question no venue will: "a side shown at 82 with five minutes left, how often did it ACTUALLY win?" Returns a grid of (price bucket x minute elapsed) -> n, realized_win_rate_pp, mean_shown_price_pp, calibration_gap_pp (realized minus shown, zero means the book is calibrated), breakeven_win_rate_pp (the shown price plus the taker fee that was actually in force for that market), and net_edge_pp (realized minus breakeven, which is what a taker would have kept). WHY AN ARCHIVE EXISTS AT ALL: a settled 15-minute window is exactly what these venues stop serving. Measured 2026-10-22, a polymarket.com window drops out of the default market listing within minutes of closing (its trade tape and resolution stay retrievable by a closed-market lookup, which the collector now uses), and the other venues serve settled windows only briefly or thinly. So this tool reads a local archive collected window-by-window as they settle. THE THREE VENUES ARE NEVER POOLED. all three compare an END 60-second average with a START 60-second average, but on different feeds: polymarket.com on a Chainlink TWAP, polymarket-us and Kalshi on a CF Benchmarks BRTI simple average. The feeds disagree near the threshold (measured 2026-10-24 on btc: polymarket.com and Kalshi settled differently on 1.6% of windows both hold, polymarket-us and Kalshi on none), so venue:"all" returns one grid PER VENUE and `venues_pooled` is always false. EVERY RATE CARRIES ITS 95% INTERVAL, AND EVERY EDGE SAYS WHETHER IT SURVIVES IT. Each cell gives realized_win_rate_ci95_lo/hi_pp (Wilson, so it never reports an impossible win rate above 100), the same interval carried onto net_edge_ci95_lo/hi_pp, and net_edge_distinguishable_from_zero. READ THAT BOOLEAN BEFORE net_edge_pp: at these sample sizes most cells are false, meaning the interv

    Show parameters
    • venuestringpolymarket | polymarket-us | kalshi | all (default polymarket). "all" returns one grid per venue, never a merged one.
    • assetstringbtc (default) | eth | sol | xrp | bnb. Coverage differs by venue: polymarket and polymarket-us carry btc/eth/sol/xrp, Kalshi carries btc/eth/bnb.
    • horizonstring15m (default). 5m | 1h | 1d are accepted but only 15m is collected today, so another value returns coverage.windows_total 0 rather than an error.
    • bucket_ppnumberPrice-bucket width in percentage points: 5 | 10 (default) | 20 | 25 | 50. Must divide 100, so the last bucket is never narrower than the rest.
    • minutenumberMinutes elapsed since window open, 0-based. Omit for the full grid; pass 5 for the "five minutes in" row only, which is also the cheapest query.
    • side_conventionstring"favorite" (default) folds each window onto whichever side was the favorite, the frame published claims about early favorites use. "yes" keeps the venue own YES
  • updown_venue_compare3 params

    The same 15-minute crypto "up or down" window priced on polymarket.com, Polymarket US and Kalshi, side by side, with whether each pair is actually the same contract. Pass asset (btc | eth | sol | xrp | bnb) and window ("current" default, "next", "previous", or the window START as ISO such as 2026-10-27T14:15:00Z, on a 15-minute boundary). Per venue: question, Up bid / ask / mid / last, spread_pp, quote_state, volume WITH ITS UNIT, open interest, liquidity, settlement source, comparison basis, when it settles. THE VENUES ARE NOT ONE CONTRACT. Kalshi and Polymarket US settle on CF Benchmarks' BRTI (60-second average at the end against the same at the start): the same bet, so a gap between them is a real disagreement. polymarket.com settles on a Chainlink 60-second TWAP, end against start: same comparison shape, different feed, so a gap against either is partly the contract. `pairs[]` gives equivalent ("true"|"false"|"unclear"|"not_comparable") from resolution_diff for every pair, material_differences, mid_diff_pp (a minus b, in percentage points) and read_as in words. Measured over 30 days of settled windows the Chainlink and BRTI feeds settle a window differently about 1.2-1.8% of the time, almost entirely windows that ended near the threshold (see updown_divergence_rate). `net_spread` is computed only for the pair that is equivalent: the gap in mid terms and at top of book (buy Up where cheaper at the ask, Down where Up is dearer at 1 minus the bid) after BOTH venues' taker fees, each fee carrying its verified-as-of date. Top-of-book size is shown where the venue publishes it (Polymarket US); the Kalshi figure is not in its market payload, so read its order book before sizing. A venue with no market for the window is {status:"not_listed", reason}; one that could not be read is {status:"unavailable", refusal} -- never an empty object, and never the same thing. A one-sided book (typical Polymarket US just before a window is decided) has quote_state "bid_only", a null

    Show parameters
    • assetstringbtc (default) | eth | sol | xrp | bnb. Coverage differs by venue; a venue that does not list the asset answers not_listed.
    • horizonstring15m (default and the only value offered).
    • windowstring"current" (default), "next", "previous", or the window START as an ISO-8601 timestamp on a 15-minute boundary, e.g. 2026-10-27T14:15:00Z. An unaligned timestamp
  • updown_divergence_rate2 params

    How often two venues settled the SAME 15-minute crypto window differently, over every settled window on record. Compares polymarket.com (Chainlink TWAP) with Kalshi and with Polymarket US (both CF Benchmarks BRTI), and Kalshi with Polymarket US as the same-feed control. Per pair: windows both venues settled, divergent count, the rate with its 95% Wilson interval (withheld under 30 paired windows), which direction they split, and what was excluded (unsettled on a side, 50-50). A HEADLINE RATE IS A CONCENTRATION QUESTION, so every pair also carries `concentration` (UTC days and hours the divergent windows fell in, the busiest day, the top-3-day share, and a plain reading) and `by_how_decided` (the rate by how far the reference venue's mid was from 50 at its last priced minute: the rate is a fraction of a percent for windows that were decided by the end and tens of percent for the ones that were not). `divergent_path` gives the mean Up mid by minute on both venues over the divergent windows only, split by who said Up, so the "early spike that fades" story can be checked rather than assumed. Measured on the archive 2026-10-27 over 30 days of btc: polymarket.com vs Kalshi diverged on 48 of 2,847 windows (1.69%, interval 1.27-2.23), spread over 27 of 31 UTC days, 0.19% of windows decided by the end and 17-29% of the ones still undecided; Polymarket US vs Kalshi on 0 of 1,838. asset btc | eth | sol | xrp | bnb (bnb has no pair: Kalshi only); days 1-90 (default 30), capped by what the archive holds (it starts 2026-09-22 for polymarket.com and Kalshi, 2026-10-07 for Polymarket US). Read-only; cheap enough to call, it reads several thousand archive rows.

    Show parameters
    • assetstringbtc (default) | eth | sol | xrp | bnb. The archive holds btc/eth on all three venues, sol/xrp on polymarket.com and Polymarket US, bnb on Kalshi only (no pair).
    • daysnumberLook-back in days, 1-90 (default 30). The archive starts 2026-09-22 (polymarket.com, Kalshi) and 2026-10-07 (Polymarket US, btc), so a longer span is capped by
  • archive_evidence4 params

    What did a web page say on a given date? Finds the archived capture of a URL nearest that date across the Internet Archive Wayback Machine, Common Crawl and Arquivo.pt, reads it, and returns the readable text (HTML stripped) with the capture timestamp, a link to the archived copy, and the GAP between the date asked for and the capture actually used (e.g. "Captured 1.5 day(s) before the requested date"). One call replaces the find-capture, fetch-record, parse-HTML chain. If no archive holds a capture within max_gap_days (default 30) it answers status "no_capture" and names the nearest capture before and after the date with their gaps, so a distant capture is never passed off as the page on that date. Every archive's outcome is listed in sources[]; one that timed out or errored says so with its upstream status, and if all of them failed the answer is error "archives_unavailable", not no_capture. Captures are immutable and cached by capture id; served_from says whether the text came from cache or upstream. Use archive_compare to see what changed between two dates.

    Show parameters
    • urlstringrequiredThe page address, e.g. "https://www.sec.gov" or "https://www.ftc.gov/policy-notices/privacy-policy".
    • datestringrequiredThe date to look up, as YYYY-MM-DD (e.g. "2023-06-01"), YYYYMMDD, or a full ISO timestamp.
    • max_gap_daysnumberFurthest a capture may be from the date and still be used, in days. Default 30, max 3650.
    • max_charsnumberCharacters of page text to return. Default 12000, max 60000.
  • archive_compare4 params

    What changed on a web page between two dates? Resolves the archived capture nearest each date (Internet Archive Wayback Machine, Common Crawl, Arquivo.pt), extracts the readable text of both, and returns a text-level diff: the segments removed and added, a similarity score, and both capture timestamps with their gaps from the requested dates. It diffs readable text, not markup, so a restyled page with the same words reads changed:false. Identical captures answer changed:false with the reason (same capture, identical content digest, or identical text), never an empty diff. A date with no capture within max_gap_days (default 30) answers status "no_capture", naming which side is missing and the nearest captures to it. Typical uses: how a privacy policy, terms of service, pricing or product page changed; whether a statement was on a page at a given time.

    Show parameters
    • urlstringrequiredThe page address, e.g. "https://www.ftc.gov/policy-notices/privacy-policy".
    • date_astringrequiredThe earlier date, as YYYY-MM-DD (e.g. "2021-06-01").
    • date_bstringrequiredThe later date, as YYYY-MM-DD (e.g. "2024-06-01").
    • max_gap_daysnumberFurthest a capture may be from each date and still be used, in days. Default 30, max 3650.
  • research_row5 params

    Claygent-style per-row research: answer ONE question about ONE company and return a JSON object matching your output_schema, with every field wrapped in its own evidence, {value, evidence_url, quote, status}. status is NEVER self-reported by the model: "found" means this code independently verified the model's quote is a VERBATIM substring of text actually fetched; "inferred" means a value was given but the quote could not be verified; "not_established" means no source answered the field, and its value is always null, never guessed, never a blended score. Sources: "web" fetches the company's own site (entity.domain required, homepage, /about, /leadership) via fetch_url; "catalog" checks entity_profile (SEC EDGAR; resolved:false for a private company is expected, not a failure); "both" (default) tries both. max_cost (USD, default 0.02, max 0.50) scales how many pages are fetched and refuses up front if it is too small to pay for even one extraction call (floor $0.002), never silently overspends. A row where every source comes back empty costs nothing: every field is mechanically not_established with NO model call made. For a boolean/derived field (e.g. "does this company sell to healthcare"), the quote only has to SUPPORT the value, a descriptive sentence about customers/products counts, the source need not state the answer verbatim. leadership_page_status ("fetched"|"not_found"|"not_attempted", plus leadership_note) says plainly whether a leadership/team page was actually read, so a named-person field (head_of_sales) coming back not_established is distinguishable from "this company just doesn't publish one" vs. "we never checked". model_output_empty:true means the model returned nothing usable (a transport/budget problem), every field is not_established for THAT reason, never read as 20 individual "no" judgments. Use with a fixed question + schema across many rows for "Claygent over N companies with a hard cost cap" (composes with batch callers). For picking from a

    Show parameters
    • entityobjectrequiredThe row/company to research. At least one of name/domain required.
    • questionstringrequiredThe question to answer about this company, in natural language, e.g. "Does this company sell to healthcare, and who is the head of sales?"
    • output_schemaobjectrequiredJSON Schema object naming the fields to extract, e.g. {"properties":{"sells_to_healthcare":{"type":"boolean"},"head_of_sales":{"type":"string"}}}. Up to 20 fiel
    • sourcesstringWhere to look: "web" (company site only), "catalog" (entity_profile only), "both" (default).
    • max_costnumberCost ceiling in US dollars for this one row. Default 0.02, max 0.50, minimum viable 0.002 (below that the call is refused rather than silently exceeding it).
  • classify_row3 params

    Cheap categorization: given a company and a list of candidate labels, decide which labels apply, the most common GTM/AI usage shape (tagging a list by industry, ICP fit, etc.), one small model call. Same evidence contract as research_row: each label comes back {label, applies, evidence_url, quote, status: found|inferred|not_established}, "found" only when the model's quote is independently verified as a verbatim substring of the text used. Pass text directly (cheapest, no fetch) or entity.domain to fetch the homepage once as a fallback. No text and no domain means every label is not_established with no model call made.

    Show parameters
    • entityobjectrequiredThe row/company to classify. At least one of name/domain required.
    • labelsarrayrequiredCandidate labels to test, 2-30 strings, e.g. ["healthcare","fintech","logistics"].
    • textstringText to classify directly (a description, a page you already fetched, etc.), cheapest path, skips any fetch.
  • pipeworx_trending1 param

    What other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d). Useful for: (1) discovering what data sources are hot for current events, (2) confirming a popular tool is the canonical choice before asking your own question, (3) seeing whether your use case aligns with what most agents need. Self-aggregating signal, derived from CF analytics-engine, no PII, just (pack, tool, count). Cached 5min-1h depending on window.

    Show parameters
    • windowstring24h (default) | 7d | 30d. Shorter windows surface what's hot right now; longer windows show steady-state demand.
  • suggest_questions1 param

    What can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have?, the onboarding entry point for an agent that just connected and wants to know what is worth asking. Returns category-bucketed example questions (company financials, drugs & clinical trials, economics, real estate, prediction markets, weather, government & patents, science & academia, news), each with the exact tool + argument shape that answers it, drawn from the live catalog of thousands of tools. Call with no arguments for the full spread, or pass `topic` (e.g. "finance", "pharma", "betting") to focus. Use this FIRST when you do not yet know what Pipeworx can do for you, or to learn how to call the meta-tools (ask_pipeworx, entity_profile, compare_entities, etc.).

    Show parameters
    • topicstringOptional focus area: finance | pharma | economics | real-estate | betting | weather | government | science | news. Omit for a cross-category spread.
  • generate_llms_txt2 params

    Generate a production-ready llms.txt file for any URL so AI crawlers (ChatGPT, Claude, Perplexity) can index the site cleanly. Fetches the page, extracts title/description/key links, and emits the standard llms.txt markdown format. Output is a single text blob ready to drop at site-root/llms.txt. Useful for: getting a client's site indexed by AI, drafting llms.txt for your own project, or auditing how an AI crawler would see a competitor.

    Show parameters
    • urlstringrequiredFull URL of the site to summarize, e.g. "https://example.com" or a specific landing page.
    • max_linksnumberMaximum number of link entries to include (default 25, max 50).
  • ai_visibility_check4 params

    Probe one or more LLMs for what they know about a business / brand / product / topic and score visibility (0-100) per model. Default model is Workers AI Llama-3.3-70b (free); pass `_apiKey` to also probe Anthropic (BYO key, you pay Anthropic directly for those calls). Returns per-model {score, confidence, signals, raw_response} + a combined view. Useful for AI-marketing audits, pre-launch brand checks, competitive monitoring.

    Show parameters
    • entitystringrequiredThe thing to ask about. Brand/business name, product name, person, or topic. E.g. "Pipeworx", "OpenInvoice", "Acme Corp pricing".
    • contextstringOptional: a phrase locating the entity (e.g. "Boston restaurant", "B2B SaaS"). Helps disambiguate common names.
    • modelsarrayWhich models to probe. Supported: "workers-ai" (free default), "anthropic" (requires _apiKey). Omit for just workers-ai.
    • _apiKeystringOptional Anthropic API key (sk-ant-...), only needed if "anthropic" is in models. Passed straight through to api.anthropic.com.
  • scan_competitor_ai_presence4 params

    Compare AI visibility across multiple entities side-by-side. Probes each entity (your brand + N competitors) with ai_visibility_check, ranks by score, surfaces which is most/least recognized. Useful for competitive AI-marketing audits: "does Claude know about us as well as our competitors?". Returns ranked list with score, confidence, signal density per entity.

    Show parameters
    • entitiesarrayrequiredArray of 2-8 entities to compare (brand/business/product names). First entry treated as the "subject" for narrative; rest are competitors.
    • contextstringOptional shared context applied to every probe (e.g. "B2B SaaS", "Boston restaurant"). Disambiguates common names.
    • modelsarrayWhich models to probe. Supported: "workers-ai" (free default), "anthropic" (requires _apiKey). Omit for just workers-ai.
    • _apiKeystringOptional Anthropic API key, only if "anthropic" is in models. Passed to api.anthropic.com per probe.
  • pipeworx_feedback4 params

    Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection, if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs, don't paste the end-user's prompt. Filing without an account returns a `claim_token`; pass it back later as pipeworx_feedback({claim_token:"pwfb_..."}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

    Show parameters
    • typestringbug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise =
    • messagestringYour feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
    • contextobjectOptional structured context: which tool, pack, or vertical this relates to.
    • claim_tokenstringRead the reply to a report you filed earlier: pass the `pwfb_...` token that filing returned, with no other arguments. Returns the status and, once resolved, wh
  • remember9 params

    Save data the agent will need to reuse later, across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

    Show parameters
    • keystringrequiredMemory key (e.g., "subject_property", "target_ticker", "user_preference"). Accepts name, k, label as aliases.
    • valuestringrequiredValue to store (any text, findings, addresses, preferences, notes). Accepts content, text, data, v as aliases; a non-string value is stored as JSON.
    • namestringAlias for key.
    • kstringAlias for key.
    • labelstringAlias for key.
    • contentstringAlias for value.
    • textstringAlias for value.
    • datastringAlias for value.
    • vstringAlias for value.
  • recall4 params

    Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier, the user's target ticker, an address, prior research notes, without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

    Show parameters
    • keystringMemory key to retrieve (omit to list all keys). Accepts name, k, label as aliases.
    • namestringAlias for key.
    • kstringAlias for key.
    • labelstringAlias for key.
  • forget4 params

    Delete a previously stored memory by key. Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier. Pair with remember and recall.

    Show parameters
    • keystringrequiredMemory key to delete. Accepts name, k, label as aliases.
    • namestringAlias for key.
    • kstringAlias for key.
    • labelstringAlias for key.
  • ashares_limit_up2 params

    The Chinese A-share market's LIMIT-UP board (涨停板) for a trading day, how many stocks hit their daily price limit (+10%, or +20% for STAR/ChiNext) and the ranked list of those stocks. Answers 'how many A-shares hit limit up today', 'top limit-up stocks', 'which stocks 涨停'. Each stock includes code, name, price, change %, turnover (成交额), float market cap, turnover rate (换手率), consecutive-board count (连板数 lbc), first/last seal time, seal fund (封板资金), and industry (行业). Source: Eastmoney (keyless).

    Show parameters
    • datestringTrading day as YYYYMMDD or YYYY-MM-DD (default: most recent trading day).
    • limitnumberHow many stocks to return, 1-100 (default 30). The total count is always returned regardless.
  • ashares_limit_down2 params

    The Chinese A-share market's LIMIT-DOWN board (跌停板) for a trading day, how many stocks hit their daily DOWN price limit (-10%, or -20% for STAR/ChiNext) and the ranked list of those stocks. Answers 'how many A-shares hit limit down today', '跌停家数', 'which stocks 跌停', 'limit-down stock count for a China A-share trading day', the counterpart to ashares_limit_up, together giving market-wide limit-up/limit-down breadth. Each stock includes code, name, price, change % (negative), turnover (成交额), float market cap, turnover rate (换手率), seal fund (封板资金), last seal time, industry (行业), and P/E. Source: Eastmoney (keyless).

    Show parameters
    • datestringTrading day as YYYYMMDD or YYYY-MM-DD (default: most recent trading day).
    • limitnumberHow many stocks to return, 1-100 (default 30). The total count is always returned regardless.
  • ashares_margin_financing7 params

    China A-share margin financing and securities lending balance (融资融券余额/两融余额), the market-wide leverage gauge: aggregate financing balance (融资余额, money borrowed to buy stock), securities-lending balance (融券余额, shares borrowed to short), and their combined total (融资融券余额), for the Shanghai (SSE) and Shenzhen (SZSE) exchanges separately and combined, with day-over-day change. Answers '融资余额', '两融余额', '融资融券余额', 'margin financing balance', 'China A-share margin debt', 'how much margin debt is in the A-share market', 'margin balance day over day change'. Pass a 6-digit SZSE code (0/3/159-prefixed) in `symbol` for that stock's own 融资余额/融券余额/融资融券余额 instead of the market aggregate, SSE (6xxxxx) per-stock detail is not available via any verified keyless route, so a SH code returns a clear not_available message rather than silently substituting. Margin data publishes T+1 (today's figures appear tomorrow morning); a request for a day with nothing published yet or a non-trading day (weekend/holiday) automatically falls back to the last trading day that published, and says so. Amounts in CNY (converted from each exchange's native 元/亿元/万元 units and labelled). HISTORY: pass start_date/end_date or days (and interval=month_end for one row per month) for a dated series of SSE, SZSE and combined financing balances back to 2010-03-31, each row with the balance as a percent of float market value (e.g. 'A-share margin financing balance, last 6 month-ends'). Source: SSE margin trading figures via Eastmoney per-exchange margin history (keyless) + SZSE margin trading summary (keyless).

    Show parameters
    • symbolstringOptional 6-digit SZSE code (0/3/159-prefixed, e.g. "000001" 平安银行) for that stock's own margin balance instead of the market-wide aggregate. SSE codes (6xxxxx) a
    • datestringTrading day as YYYY-MM-DD or YYYYMMDD (default: most recent day with published data). Margin data is T+1, so "today" usually has nothing yet.
    • start_datestringHISTORY MODE: first day of a series, YYYY-MM-DD or YYYYMMDD. Returns one dated row per trading day (or per month, see interval) with SSE, SZSE and combined fina
    • end_datestringHISTORY MODE: last day of the series (default: most recent published day).
    • daysnumberHISTORY MODE alternative to start_date: the most recent N trading days (1-250). With interval month_end, N is a CALENDAR-day window back from end_date (1-7300):
    • monthsnumberHISTORY MODE, interval month_end only: the most recent N month-ends (1-240). Ignored for daily.
    • intervalstringHISTORY MODE: "daily" (default; at most 250 rows) or "month_end" (the last published trading day of each calendar month; at most 240 rows).
  • ashares_market_snapshot

    Overall snapshot of the Chinese A-share market, the headline index levels (Shanghai Composite, Shenzhen Component, ChiNext, STAR 50, CSI 300) with change %, day range and turnover, plus market-wide breadth as a sentiment gauge: how many stocks hit limit-up (涨停) and limit-down (跌停) today. Answers 'how is the China A-share market doing', 'Shanghai Composite today', 'A-share market snapshot at close', 'how did Chinese stocks close', '涨跌停家数', 'limit-up limit-down counts today'. For the ranked pools use ashares_limit_up / ashares_limit_down; for market-wide margin financing leverage use ashares_margin_financing. Source: Tencent Finance (indices) + Eastmoney (limit counts), keyless.

  • ashares_quote1 param

    Real-time quote(s) for Chinese A-share stocks by 6-digit code (Shanghai 6xxxxx, Shenzhen 0xxxxx/3xxxxx, STAR 688xxx, ChiNext 30xxxx, Beijing 8xxxxx/4xxxxx). Returns name, current price, change and change %, open, previous close, day high/low, volume, turnover, and the quote timestamp. Accepts one code or a comma-separated list. Example: ashares_quote({ symbols: "600519,000858" }) for Kweichow Moutai and Wuliangye. Volume is reported in whole 100-share lots. Source: Tencent Finance (keyless).

    Show parameters
    • symbolsstringrequiredOne 6-digit code or a comma-separated list, e.g. "600519" or "600519,000001,300750". sh/sz/bj prefixes are accepted but optional.
  • ashares_turnover_ranking5 params

    Market-wide ranking of Chinese A-share stocks by turnover / 成交额排名, 成交额前30名, 成交量排名, or 涨跌幅排名, the whole board (not specific codes), sorted server-side and returned as a ranked list. Answers 'A股成交额前30名', 'top 30 A-shares by turnover today', 'A股成交量排名', 'A-share market-wide ranking by amount/volume/change %', 'which A-shares traded the most today'. Each row has code, name, price, change %, volume (shares), turnover in CNY (成交额), turnover rate %, and industry (行业/板块, when resolvable). Omit `date` (or pass today) for the LIVE board (Sina, real-time). Pass a PAST trading day in `date` for that day's ranking instead of today's, this uses a different, Eastmoney-sourced historical path and only supports `sort:'changepercent'` (涨跌幅排名): no keyless bulk source for a PAST day's turnover amount or volume ranking was found (Sina's live board is the only amount/volume source), so `date` + `sort:'amount'|'volume'` throws a clear error naming that gap rather than silently substituting today's board. A non-trading `date` (weekend/holiday) walks back to the prior trading day automatically.

    Show parameters
    • limitnumberHow many stocks to return, 1-100 (default 30).
    • sortstringRank by turnover amount (成交额, default), change % (涨跌幅), or share volume (成交量). For a PAST `date`, only 'changepercent' is available, 'amount'/'volume' throw a c
    • orderstringdesc (default, highest first) or asc.
    • boardstringWhich board to rank: hs_a = all Shanghai+Shenzhen A-shares (default, 沪深A股), sh_a = Shanghai only (沪市A股), sz_a = Shenzhen only (深市A股), cyb = ChiNext (创业板).
    • datestringA PAST trading day, YYYY-MM-DD or YYYYMMDD, for that day's ranking instead of today's live board. Only `sort:'changepercent'` is supported with a past date. Omi
  • ashares_capital_flow2 params

    Per-stock daily main-capital net inflow history (主力净流入 / 超大单+大单净流入, often called '超大单净流入' in retail trackers) for a Chinese A-share stock or ETF, one row per trading day with net inflow broken down by order size: 超大单 (super-large/institutional), 大单 (large), 中单 (medium), 小单 (small), plus 主力净流入 (main = 超大单+大单combined) in both CNY amount and as a % of that day's turnover. Answers '主力净流入历史', '超大单净流入', '000768最近20个交易日的主力资金流向', 'main capital net inflow history for a China A-share stock', 'which days did big money flow into/out of a stock'. A positive net inflow means net buying pressure from that order-size bucket that day, negative means net selling. Source: Eastmoney push2his fflow/daykline (keyless).

    Show parameters
    • codestringrequired6-digit A-share or ETF code, e.g. "000768" (中航西飞) or "515050". sh/sz/bj prefixes accepted but optional.
    • daysnumberHow many of the most recent trading days to return, 1-200 (default 20).
  • ashares_billboard2 params

    The Chinese A-share market's daily 龙虎榜 (dragon-tiger list / billboard) for a trading day, stocks flagged for unusual price/turnover deviation, with the top seats' buy/sell/net amounts, plus (when present that day) institution-seat (机构专用) net-buy detail and that day's most-active brokerage branches (营业部) market-wide as a 'top brokerages' signal. Answers '龙虎榜', 'dragon tiger list for a date', 'which stocks were on the billboard on 2026-09-24', '机构净买入', 'institution seat net buys', 'top active brokerage seats'. Each listed stock has the reason it was flagged (EXPLANATION, e.g. daily move ≥7%), close price, change %, and billboard buy/sell/net amounts in CNY; stocks that also had institutional-seat activity that day carry institution_net_buy_cny/institution_buy_seats/institution_sell_seats. A non-trading `date` (weekend/holiday) walks back to the prior trading day automatically. Source: Eastmoney datacenter-web (keyless).

    Show parameters
    • datestringTrading day as YYYY-MM-DD or YYYYMMDD (default: most recent trading day).
    • limitnumberHow many billboard-listed stocks to return, 1-100 (default 50).
  • ashares_etf_shares3 params

    Disclosed fund-share-count (基金份额) and net-asset history for a Chinese-listed ETF, period-end total shares outstanding (期末总份额), the period's subscriptions/redemptions (期间申购/赎回), and period-end net assets (期末净资产), in shares and CNY. Answers '基金份额变动', 'ETF shares outstanding history', '515050规模变动', 'how many shares outstanding does this ETF have over time'. IMPORTANT: this is NOT a daily series, Chinese ETFs publicly disclose 份额 only at quarter-end plus occasional ad-hoc material-change dates (confirmed live for 515050/561980/588170/588200), not every trading day; a `from`/`to` window with no disclosure inside it returns found:false naming the nearest disclosed dates rather than fabricating daily rows. For a daily PRICE series use ashares_daily_history; this tool is share-count/AUM only. Source: Eastmoney fund F10 archive (keyless).

    Show parameters
    • codestringrequired6-digit ETF code, e.g. "515050", "561980", "588170", "588200", or "512000".
    • fromstringEarliest disclosure date to include, YYYY-MM-DD or YYYYMMDD (inclusive). Default: no lower bound (full history, newest first, capped).
    • tostringLatest disclosure date to include, YYYY-MM-DD or YYYYMMDD (inclusive). Default: today (no upper bound in practice).
  • ashares_earnings_forecast2 params

    Company-issued earnings guidance (业绩预告) for a Chinese A-share stock, the company's own forecast announcements with predicted profit range (lower/upper bounds in CNY), year-over-year change %, forecast type (略增/预增/扭亏 etc.), and the company's stated reason. Answers '业绩预测', '业绩预告', 'earnings forecast/guidance for a China A-share company like 华工科技 000988'. Most recent reports first. Source: Eastmoney datacenter (keyless).

    Show parameters
    • symbolstringrequired6-digit A-share code, e.g. "000988" (华工科技) or "600519" (贵州茅台).
    • limitnumberHow many forecast announcements to return, 1-20 (default 4, newest first).
  • ashares_analyst_consensus1 param

    Analyst consensus estimates (盈利预测) for a Chinese A-share stock, per forecast year: consensus EPS, P/E at current price, net profit attributable to parent (归母净利润), and total operating revenue, in CNY. Answers "analyst estimates / 盈利预测 / forecast EPS for a China A-share like 000988". Source: Eastmoney datacenter (keyless).

    Show parameters
    • symbolstringrequired6-digit A-share code, e.g. "000988" or "300750" (宁德时代).
  • ashares_daily_history4 params

    Daily OHLCV history (历史日线) for one or more Chinese A-share stocks over a date range, open, high, low, close, volume, and day-over-day change % per trading day. Answers '300418在2026-08-31到2026-09-03的收盘价和涨跌幅', 'daily closes for 600519 last week', 'history for 000858 and 300750 this month', '涨跌幅历史', '历史成交量'. Up to 20 comma-separated 6-digit codes. change_pct is computed from consecutive closes within the returned range (the first row has no prior close in range, so it is null); turnover amount (成交额) is not exposed by this daily-bar source, so amount_cny is reported as "not_available" rather than estimated, use ashares_quote or ashares_turnover_ranking for same-day turnover amount. Source: Tencent/gtimg fqkline (keyless).

    Show parameters
    • codesstringrequiredOne 6-digit code or a comma-separated list, up to 20, e.g. "300418" or "300418,300364,002131". sh/sz/bj prefixes accepted but optional.
    • startstringrequiredStart date, YYYY-MM-DD or YYYYMMDD (inclusive).
    • endstringEnd date, YYYY-MM-DD or YYYYMMDD (inclusive). Default: today.
    • adjuststringPrice adjustment for splits/dividends: qfq = forward-adjusted (default, prices comparable to today), hfq = backward-adjusted, none = raw unadjusted prices.
  • ashares_intraday_bars4 params

    Intraday minute bars (分钟线/分时/分钟K线) for Chinese A-share stocks/ETFs on a given trading日/交易日, with cumulative volume and turnover (累计成交量/累计成交额) computed up to a requested time of day (截至<time>, e.g. 截至11:05), answers '515050在2026-09-01这个交易日截至11:05的累计成交量和累计成交额', '600519某个交易日截至某时刻的累计成交量和成交额', 'cumulative volume for 600519 up to 11:05 on a past trading day', 'intraday minute bars for an A-share on a specific date'. ashares_quote is realtime-only (today, right now) and ashares_daily_history is end-of-day-only (no intraday granularity), this tool is for a PAST trading日's intraday trajectory. Returns the interval bars for that day plus cumulative_volume_shares/cumulative_turnover_cny summed from the day's open through `up_to` (or the whole day if `up_to` is omitted). `symbols` takes a bare 6-digit code (e.g. "515050") or the sh/sz/bj-prefixed form, same as ashares_quote. Bounded lookback: the upstream caps total bars at ~1950 regardless of interval, so retention shrinks as the interval shrinks, roughly 8 trading days at 1-minute, 40 at 5-minute (the default), 110 at 15-minute, a year at 30-minute, two years at 60-minute, and it slides forward daily. A `date` older than a result's `earliest_bar_date_available` is out of range for that interval; try a coarser interval, or use ashares_daily_history for daily (not intraday) history further back. Source: Sina (keyless).

    Show parameters
    • symbolsstringrequiredOne 6-digit code or a comma-separated list, up to 5, e.g. "515050" or "600519,000001". sh/sz/bj prefixes accepted but optional. ETF codes work the same as stock
    • datestringrequiredThe trading day the bars are for, YYYY-MM-DD or YYYYMMDD, e.g. "2026-09-01".
    • up_tostringTime of day (24-hour, Beijing time) to cumulate volume/turnover through, e.g. "11:05". Omit for the whole trading day (or "as of now" if `date` is today and the
    • intervalstringBar interval in minutes. Default "5". Smaller intervals keep a shorter lookback window, see the tool description.
  • ashares_technical_indicators14 params

    Technical indicators for Chinese A-share stocks and ETFs (均线/布林/MACD/KDJ), MA (moving averages, any windows, default MA5/MA10/MA20/MA60), BOLL (Bollinger Bands, default 20-period x2 std dev), MACD (DIF/DEA/柱, default 12/26/9), and KDJ (K/D/J, default 9/3/3), computed from this pack's own daily OHLCV history (same source and codes as ashares_daily_history, ETF codes like 515050/588170/561980 work the same as stock codes). Answers '515050通信ETF华夏最近20个交易日MA5/MA10/MA20/BOLL/MACD/KDJ', '603986兆易创新周线MACD是否死叉', 'MA20 and BOLL for an A-share ETF', '布林带', '均线', '金叉死叉'. Internally fetches extra lookback history before `start` so the indicators are warmed up (MA60/MACD need ~60+ trading days of prior data), only the requested [start, end] range is returned. MACD histogram uses the common Chinese charting convention 柱=2x(DIF−DEA); KDJ smoothing is the standard 3/3 recursive form seeded at 50. Up to 5 comma-separated codes per call (indicator math is heavier than a plain OHLCV pull). Source: Tencent/gtimg fqkline (keyless), same as ashares_daily_history.

    Show parameters
    • codesstringrequiredOne 6-digit code or a comma-separated list, up to 5, e.g. "515050" or "600519,300750". sh/sz/bj prefixes accepted but optional. ETF codes work the same as stock
    • startstringrequiredStart date for the RETURNED indicator range, YYYY-MM-DD or YYYYMMDD (inclusive). Extra history before this date is fetched automatically to warm up the indicato
    • endstringEnd date, YYYY-MM-DD or YYYYMMDD (inclusive). Default: today.
    • adjuststringPrice adjustment for splits/dividends: qfq = forward-adjusted (default), hfq = backward-adjusted, none = raw.
    • indicatorsarrayWhich indicator families to compute. Default: all four.
    • ma_windowsarrayMA window lengths in trading days. Default [5, 10, 20, 60].
    • boll_periodnumberBOLL period, default 20.
    • boll_multnumberBOLL standard-deviation multiplier, default 2.
    • macd_fastnumberMACD fast EMA period, default 12.
    • macd_slownumberMACD slow EMA period, default 26.
    • macd_signalnumberMACD signal (DEA) EMA period, default 9.
    • kdj_nnumberKDJ RSV lookback period, default 9.
    • kdj_m1numberKDJ K smoothing factor, default 3.
    • kdj_m2numberKDJ D smoothing factor, default 3.
  • ashares_sector_capital_flow4 params

    China A-share INDUSTRY-SECTOR net capital inflow ranking (行业资金流向排名/板块资金流) for a trading day -- ranks Eastmoney's ~128 industry boards (行业板块) by main-capital net inflow (主力净流入), with the breakdown by order size (超大单/大单/中单/小单 net inflow in CNY), the day's change %, and each sector's single stock with the largest net inflow. Answers '今日行业资金流向排名', 'which industry sectors had the biggest net capital inflow today', '板块资金流排名', 'sector fund flow ranking', 'semiconductor sector money flow today'. This is a DIFFERENT metric from china-exchange-data's ashares_sector_flows, which is SZSE's own official per-industry TURNOVER ranking -- this tool is Eastmoney's vendor-computed NET INFLOW (主力净流入) classification, the sector-level counterpart to this pack's own per-stock ashares_capital_flow. A non-trading date (weekend/holiday, or before today's session has published -- publication usually lags a day) walks back automatically to the nearest prior trading day with data. Source: Eastmoney datacenter (keyless).

    Show parameters
    • datestringTrading day as YYYY-MM-DD or YYYYMMDD (default: most recent day with published data -- today's session often has not published yet).
    • limitnumberHow many sectors to return, 1-130 (default 20).
    • sortstringRank by net inflow amount in CNY (主力净流入, default), net inflow as a % of turnover (净流入占比), or the day's change % (涨跌幅).
    • orderstringdesc (default, biggest net inflow first) or asc (biggest net outflow first).
  • ashares_sector_capital_flow_window6 params

    China A-share INDUSTRY-SECTOR main-capital net inflow summed over the last N trading days (default 5; use 3, 5 or 10), with how many days in a row each sector has had net inflow or outflow. Answers '最近5日行业主力资金净流入排名', '板块连续3日净流入', '连续流入天数', 'which sectors had the most main-capital net inflow over the last 10 trading days', 'sectors with net inflow for 3 days running', 'sector fund flow 5-day ranking'. Per sector: summed main net inflow (主力净流入) and its order-size split (超大单/大单/中单/小单) in CNY, inflow and outflow day counts, the current consecutive inflow or outflow streak, cumulative change %, and the day-by-day net inflow. Rank with `sort` (summed inflow, streak length, cumulative change, inflow days) and filter one sector with `sector` (name fragment or board code). Eastmoney industry boards (行业板块), roughly 128 sectors, history from 2021-11; not the Shenwan classification. For a single day use ashares_sector_capital_flow. Source: Eastmoney datacenter (keyless).

    Show parameters
    • daysnumberWindow length in trading days, 1-20 (default 5; 3, 5 and 10 are the common asks).
    • end_datestringLast day of the window, YYYY-MM-DD or YYYYMMDD (default: most recent day with published data).
    • sortstringRank by summed net inflow (default), current consecutive inflow streak, cumulative change %, or number of inflow days.
    • orderstringdesc (default, largest first) or asc (largest net outflow / shortest streak first).
    • sectorstringOnly sectors whose name contains this text (e.g. "半导体") or whose board code equals it (e.g. "BK1036").
    • limitnumberHow many sectors to return, 1-130 (default 20).
  • ashares_stock_connect1 param

    Stock Connect (沪深港通) daily channel statistics: GROSS TURNOVER for Northbound (mainland A-shares bought via Hong Kong -- 沪股通/深股通/combined) and Southbound (Hong Kong-listed stocks bought by mainland investors -- 港股通沪/港股通深/combined), plus a best-effort per-stock "top traded stocks" list for Northbound. Answers "northbound stock connect turnover today", "沪深股通成交额", "how much did northbound/southbound trade today", "stock connect top traded stocks". IMPORTANT: mainland regulators (CSRC) stopped publishing DAILY net fund-flow figures (net buy/sell, daily inflow, remaining quota) for NORTHBOUND Stock Connect in August 2024 -- every Northbound channel's net_flow field says so explicitly rather than returning null as if it were real data; gross turnover is unaffected and is published daily for every channel. Southbound net flow is still disclosed by Hong Kong Exchanges and Clearing and is returned when available. A turnover-ranked top-10-stocks list for Northbound depends on an Eastmoney report that has returned a server error on every live probe during this build -- the tool still attempts it live on every call and reports plainly under top_traded_stocks.northbound whether real data came back, rather than silently omitting the field or faking rows. Source: Shanghai Stock Exchange / Shenzhen Stock Exchange / Hong Kong Exchanges and Clearing, via Eastmoney datacenter (keyless).

    Show parameters
    • datestringTrading day as YYYY-MM-DD or YYYYMMDD (default: most recent day with published data -- today's session often has not published yet).
  • ashares_unlock_calendar6 params

    China A-share restricted-share unlock calendar (限售股解禁): which stocks have locked-up shares becoming tradable on a given day or date range, ranked by unlock market value or by share of float. Answers "today's unlock list", "解禁日历", "限售股解禁 2026-11-06 top 10 by market value", "how many stocks unlock next week", "when does 603376 unlock", "解禁市值排名". Each unlock has the stock, unlock date, restricted-share type (e.g. first-day original-holder shares, IPO strategic placement, private-placement shares), shares unlocking, market value at the latest price in CNY, percent of total shares and percent of the pre-unlock tradable float, number of holder batches, and the stock's price change over the 20 trading days before and after. Also returns the per-day total: number of unlocking stocks and their combined market value. Give `date`, or `from` and `to` (max 31 days), or neither for today; `symbol` (6-digit code) lists that stock's unlock dates. Source: Eastmoney datacenter, restricted-share unlock report (keyless).

    Show parameters
    • datestringSingle unlock day, YYYY-MM-DD or YYYYMMDD (default: today).
    • fromstringRange start (YYYY-MM-DD); use with `to`. Max span 31 days.
    • tostringRange end (YYYY-MM-DD).
    • symbolstring6-digit A-share code (e.g. "603376"): list only that stock's unlocks (default window: 1 year back to 1 year ahead if no date given).
    • sortstringRank by unlock market value (default) or by percent of pre-unlock tradable float.
    • limitnumberMax unlock rows returned, 1-100 (default 20). Per-day totals always cover every unlock fetched.
  • ashares_sw_industries5 params

    Shenwan (申万) industry index board for a trading day: close, change %, turnover rate, trading amount (unit as published), share of market turnover, P/E, P/B and dividend yield for every Shenwan level-1 (31 industries), level-2 (131) or level-3 (336) industry. Answers "申万一级行业涨跌幅", "Shenwan industry PE PB", "which Shenwan industry rose most on 2026-11-06", "半导体 801081 市盈率 市净率", "SW industry valuation ranking", "行业估值". Filter to one industry with `code` (e.g. 801081 semiconductors, level 2) and rank with `sort`. Up/down stock counts, limit-up counts and 20-day highs per industry are NOT published by this source and are listed under not_provided. Source: Shenwan Hongyuan Research, SW industry index daily publication.

    Show parameters
    • levelnumberShenwan industry level: 1 (31 industries, default), 2 (131) or 3 (336). A code given in `code` selects its level automatically.
    • datestringTrading day, YYYY-MM-DD or YYYYMMDD (default: latest published trading day). A non-trading date returns found:false with the nearest prior trading day.
    • codestringOne 6-digit Shenwan industry code, e.g. "801080" (Electronics, L1) or "801081" (Semiconductors, L2).
    • sortstringSort descending by this field (default: by code).
    • limitnumberMax rows returned, 1-400 (default: all rows of the level).
  • ashares_sw_industry_history6 params

    Daily HISTORY of Shenwan (申万) industry indices: dated open, high, low, close, change %, trading amount for one industry code, a list of codes, or all 31 level-1 industries (level=1), trimmed to a window. Answers "申万一级行业近120个交易日收盘", "Shenwan industry index closing prices over 60 days", "which Shenwan industries turned strong over 20/60/120 days", "801010 农林牧渔 historical close", "SW index relative strength". Each industry also gets window_return_pct (first to last close, computed). Window: `limit` most recent trading days (default 60) or start_date/end_date. Multi-industry calls fetch each series separately (slow: allow ~30 s for level=1); any series that fails is listed under failed, never dropped silently. For ONE day across all industries with P/E and P/B use ashares_sw_industries. Source: Shenwan Hongyuan Research, SW industry index publication.

    Show parameters
    • codestringOne 6-digit Shenwan industry code, e.g. "801010" (Agriculture), "801080" (Electronics).
    • codesarrayList of 6-digit Shenwan codes (max 31).
    • levelnumberPass 1 to fetch all 31 level-1 industries in one call (names from the latest board).
    • start_datestringWindow start, YYYY-MM-DD or YYYYMMDD.
    • end_datestringWindow end, YYYY-MM-DD or YYYYMMDD (default: latest).
    • limitnumberMost recent N trading days within the window, 1-2000 (default 60 when no start_date).
  • ashares_market_overview4 params

    A-share market-wide DAILY OVERVIEW by date, per exchange and combined: number of listed stocks, trading amount, total market cap, float (tradable) market cap and turnover rate (换手率), for the Shanghai (SSE) and Shenzhen (SZSE) exchanges, all in 100 million CNY (亿元). Answers "A-share daily turnover rate for 60 trading days", "全市场换手率", "沪深流通市值", "A-share total and float market cap on 2026-11-12", "margin balance as a share of float market cap" (divide ashares_margin_financing by float_market_cap_100m_cny), "两市成交额". Pass `date`, or `start_date` + `end_date` (or `days`, default 1 = latest trading day) for a history of one row per trading day, newest first. The SSE turnover rate is the exchange's published float-based figure; the SZSE rate and the combined rate are COMPUTED as trading amount / float market cap and labelled so. Covers stocks only (not funds or bonds). If either exchange cannot be read for a day, that day carries the error and no combined figure rather than presenting half the market as the market. Non-trading days are skipped. Source: Shanghai Stock Exchange and Shenzhen Stock Exchange, daily market overview.

    Show parameters
    • datestringOne trading day, YYYY-MM-DD or YYYYMMDD. A non-trading day returns found:false with the nearest prior trading day.
    • start_datestringRange start (YYYY-MM-DD). Use with end_date (default: latest).
    • end_datestringRange end (YYYY-MM-DD).
    • daysnumberMost recent N trading days, 1-90 (default 1). Closed days are served from a stored copy (each day says per exchange whether it came from the store or a live rea
  • cn_index_valuation2 params

    Index VALUATION for a China Securities Index Co. (CSI) or SSE index code: the latest trading day's P/E and dividend yield plus roughly the last 20 trading days, dated. Answers "CSI Dividend Index 000922 latest P/E and dividend yield", "SSE Dividend 000015 valuation", "H30269 dividend low volatility index P/E", "930955 红利低波100 市盈率 股息率", "中证红利指数估值". Returns four published figures per day: P/E1 (total shares), P/E2 (calculation shares), D/P1 (dividend yield on total shares, %) and D/P2 (dividend yield on calculation shares, %). NOT in this source, and never estimated: P/B (市净率) and valuation percentile / history rank (估值分位) -- the response lists them under not_provided. Code is case-sensitive upstream: numeric codes as 6 digits (000922, 000300, 930955), letter-prefixed ones with an upper-case letter (H30269). An unknown or unpublished code returns found:false. Source: China Securities Index Co., daily index indicators.

    Show parameters
    • index_codestringrequiredCSI/SSE index code, e.g. "000922" (CSI Dividend), "000015" (SSE Dividend), "H30269" (CSI Dividend Low Volatility), "930955" (CSI Dividend Low Volatility 100), "
    • daysnumberHow many trading days of history to return, 1-30 (default: everything published, about 20).
  • cn_index_constituents2 params

    CONSTITUENTS and WEIGHTS of a China Securities Index Co. (CSI) or SSE index by code: every constituent stock with its weight (%), exchange and the file date, the weight total, plus the index's sector weights (CSI level-1 sectors such as Financials 22.6%, Information Technology 19.3%, and level-2 industry groups such as Banks) and its top-10 holdings with their sector. Answers "CSI 300 constituents and weights", "沪深300 成分股 权重", "CSI 300 sector weights", "沪深300 行业权重", "what are the biggest holdings of CSI 500 (000905)", "CSI 1000 constituents 000852". Constituent weights come from the index's daily close-weight publication and are dated by `constituents_as_of`; sector weights and top-10 come from CSI's index page data and carry their own `sector_weights_as_of` (the two can differ by days). Per-constituent sector is published only for the top 10; for the rest use the stock's own profile. Code is case-sensitive upstream: numeric codes as 6 digits (000300, 000905, 000852, 000016), letter-prefixed ones upper-case (H30269). An unknown or unpublished code returns found:false. Source: China Securities Index Co., index constituent weights and sector weights.

    Show parameters
    • index_codestringrequiredCSI/SSE index code, e.g. "000300" (CSI 300), "000905" (CSI 500), "000852" (CSI 1000), "000016" (SSE 50), "000922" (CSI Dividend).
    • limitnumberMax constituents returned, largest weight first, 1-2000 (default: all). constituent_count and weight_total_pct always cover the whole index.

Checked by Serverdex with a plain initialize + tools/list call to gateway.pipeworx.io/china-stocks/mcp, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 18, 2026
Stars
0
Forks
0
Last push
Nov 9, 2026
License
MIT

JavaScriptchina-stocksmcpmcp-servermodel-context-protocolpipeworx

From the README

@pipeworx/china-stocks Live data for the Chinese A-share market (Shanghai / Shenzhen / STAR / ChiNext) — real-time quotes, intraday minute bars, daily OHLCV history, technical indicators, the limit-up/limit-down boards, market-wide margin financing balance, market-wide turnover ranking, and company earnings guidance/analyst consensus. Part of Pipeworx — an MCP gateway connecting AI agents to 1863+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider. Tools • asharesmarketsnapshot() — headline index levels (Shanghai Composite, Shenzhen Component, ChiNext, STAR 50, CSI 300) plus limit-up/limit-down counts as a sentiment gauge. • ashareslimitup({ date?, limit? }) — the daily limit-up board (涨停板): how many stocks hit their daily price limit and the ranked pool with consecutive-board count, seal fund, industry, turnover. • ashareslimitdown({ date?, limit? }) — the daily limit-down board (跌停板), the counterpart to ashareslimitup: how many stocks hit their daily down price limit and the ranked pool. Source: Eastmoney getTopicDTPool (same host/shape as the limit-up pool). • asharesmarginfinancing({ symbol?, date? }) — China A-share margin financing and securities-lending balance (融资融券余额/两融余额): market-wide aggregate by exchange (SSE + SZSE) with day-over-day change when symbol is omitted, or one SZSE-listed stock's own balance when symbol is a 6-digit SZSE code (0/3/159-prefixed).…

Read the full README on GitHub →

Remotes

  • streamable-httphttps://gateway.pipeworx.io/china-stocks/mcp

The most-starred Finance servers in the index, with their live-check result.

ServerStarsLast pushLive check
CCXT44,949Nov 2026Local / not checked
QR Rápido7,477Nov 2026Needs sign-in
Finance Toolkit5,554Nov 2026Needs sign-in
AKQuant2,627Nov 2026Local / not checked
com.stripe MCP2,072Nov 2026Needs sign-in

China Stocks: questions people ask

Is China Stocks a remote or a local MCP server?
According to its entry in the official MCP registry, China Stocks ships as a hosted endpoint (streamable-http) that your client connects to by URL and as a local package (npm) that your client starts on your machine. Use the hosted endpoint when your client supports Streamable HTTP; use the package when you want it to run locally.
Does China Stocks need an API key?
Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 22, 2026. Individual tools may still ask for a key when called.
Is China Stocks safe to use?
Looks healthy: China Stocks is maintained, open source, hosted endpoint answering without a key. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: Local package or hosted; credentials: None needed to connect. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is China Stocks still maintained?
Active: the repository's last commit 13 days ago. Last push Nov 9, 2026, 0 GitHub stars, MIT licence. Read from GitHub on Nov 18, 2026.
What tools does China Stocks expose?
67 tools as listed by the server itself during the live check, including ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, search_within, deep_research. The full list with parameters is in the Live check section above.
How do I add China Stocks to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
  1. PipeworxLive data gateway for AI — 3,300+ tools across 750+ sources, with citations★ 11
  2. WiktionaryWiktionary MCP — multilingual dictionary via Wikimedia REST + MediaWiki Action API★ 4
  3. Football DataFootball-Data.org MCP — soccer competitions, matches, standings★ 3
  4. ArtArt MCP — Metropolitan Museum of Art Collection API (free, no auth)★ 3
Browse all Finance →

Add the badge to your site

Show visitors that China Stocks is listed here — it’s also the link we check for a free listing.

China Stocks — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-pipeworx-io-china-stocks?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="China Stocks — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![China Stocks — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-pipeworx-io-china-stocks?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/io-github-pipeworx-io-china-stocks) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/io-github-pipeworx-io-china-stocks) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/io-github-pipeworx-io-china-stocks)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/io-github-pipeworx-io-china-stocks"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-pipeworx-io-china-stocks"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-pipeworx-io-china-stocks"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).