NewTimeSpace MCP Integration Guide

search_articles

The tool returns a single block of Markdown text, not JSON. The structure is always: a header line, a divider, then one block per article. Below is a real language:"en" response:

📋 NewTimeSpace 资讯检索结果
关键词: NVIDIA | 分类: 全部 | 语言: en
日期: * ~ * | 排序: publish_time desc
第 1/20 页 · 本页 2 条 · 总计 40 条
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

【1】HK Stock Connect Daily Report: 51WORLD Rises 30.31% as Its 51Sim Unit Joins the NVIDIA Halos SAFE Ecosystem - 20261023 (ID: 1455605)
· 分类: Research | 语言: en | 发布时间: 2026-10-23T17:59:31+08:00
· 作者: 孙佳怡 | 来源: NewTimeSpace | 标签: NewTimeSpace,HK Stock Connect,HK Stock Connect ETF
· 摘要: On October 23, 2026, the HSTECH rose 2.05% and the HSI added 0.69%. 51WORLD led Stock Connect gainers, up 30.31%, as southbound net selling hit HK$1.67 billion.
· 链接: https://www.newtimespace.com/en/research/1455605.html

──────────────────────────────

【2】…

• The header line gives current page / total pages / items on this page / total matches — use it to decide whether to paginate.
• 摘要 (summary) may be truncated (ending with ......); fetch get_article_detail for the full text.
• 发布时间 is ISO 8601 with a timezone offset (+08:00).
• The 链接 path follows language (/zh-cn/, /zh-hk/, /en/).
• With include_content: true, each item becomes a 📰 文章详情 [ID: …] block that includes 正文内容 (N 字，Markdown).

get_article_detail

📰 文章详情 [ID: 1455605]
标题: HK Stock Connect Daily Report: 51WORLD Rises 30.31% as Its 51Sim Unit Joins the NVIDIA Halos SAFE Ecosystem - 20261023
分类: Research | 语言: en | 时间: 2026-10-23T17:59:31+08:00
作者: 孙佳怡 | 来源: NewTimeSpace | 标签: NewTimeSpace,HK Stock Connect,HK Stock Connect ETF
链接: https://www.newtimespace.com/en/research/1455605.html
────────────────────────────────────────
正文内容 (14137 字，Markdown):
I. Market Overview

 On October 23, 2026, the three major Hong Kong indices opened higher and briefly turned negative before rebounding with the A-share market in the afternoon and closing higher…

Multiple articles are returned as consecutive 📰 文章详情 [ID: …] blocks. A single body typically runs 800–2,800 characters in Chinese; English reports can be considerably longer.

The standard two-step pattern: search the list to get IDs, then fetch bodies on demand. This avoids pulling large volumes of text into your context at once.

1. Search: search_articles({"query":"Xiaomi","limit":10}). Check the total matches in the header line — tens of thousands means the keyword is too broad, zero means it is too narrow.
2. Pick targets: choose the 1–10 most relevant IDs from the list.
3. Fetch bodies: get_article_detail({"article_ids":"1455411,1455409"}).
4. Compose the answer: keep title + publish time + link in your output so the user can trace every claim.

Common scenarios

The server distinguishes two kinds of failure: out-of-range parameters return a tool error (isError: true), while no matches returns an empty result plus a hint.

If your environment cannot register an MCP server, you can still use this service as long as you can send a POST request. The flow takes two steps: initialize to obtain a session ID, then tools/call with that ID attached.

12.1 Hard requirements — all of them

12.2 Fastest path — one command

Both steps chained together, returning data directly:

SID=$(curl -si --max-time 40 -X POST https://mcp.newtimespace.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"web-agent","version":"1.0"}}}' \
  | grep -i '^mcp-session-id:' | tr -d '\r' | cut -d' ' -f2) && \
curl -s --max-time 40 -X POST https://mcp.newtimespace.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "Mcp-Session-Id: $SID" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"search_articles","arguments":{"query":"NVIDIA","language":"en","limit":2}}}'

This is simply the two steps in 12.3 joined with &&. If your runtime can only execute one command at a time, use this version.

12.3 Step by step

Step one — handshake and capture the session ID:

SID=$(curl -si --max-time 40 -X POST https://mcp.newtimespace.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"web-agent","version":"1.0"}}}' \
  | grep -i '^mcp-session-id:' | tr -d '\r' | cut -d' ' -f2)
echo "SID=$SID"

Step two — call the tool with the session ID:

curl -s --max-time 40 -X POST https://mcp.newtimespace.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "Mcp-Session-Id: $SID" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"search_articles","arguments":{"query":"NVIDIA","language":"en","limit":3}}}'

The response is an SSE stream; the payload sits on the data: line:

event: message
data: {"result":{"content":[{"type":"text","text":"📋 NewTimeSpace 资讯检索结果n…"}],"isError":false},"jsonrpc":"2.0","id":2}

To extract: take the JSON after data: and read result.content[0].text — that is the Markdown text shown in Section 8. If result.isError is true, text holds an error message instead of data.

12.4 Official SDK (Python)

If Python is available and you can pip install mcp, the official SDK is the least effort — it handles the handshake and session for you:

import anyio
from mcp import ClientSession
from mcp.client.streamable_http import streamable_http_client

async def main():
    async with streamable_http_client("https://mcp.newtimespace.com/mcp") as (read, write):
        async with ClientSession(read, write) as session:
            await session.initialize()
            tools = await session.list_tools()
            print([t.name for t in tools.tools])

            r = await session.call_tool(
                "search_articles", {"query": "NVIDIA", "language": "en", "limit": 3}
            )
            print(r.content[0].text)

anyio.run(main)

Written for mcp 2.x: passing the URL alone is enough, and the SDK negotiates the protocol version up to 2025-11-25. Note that fields became snake_case in 2.x (is_error, input_schema) — older tutorials using isError will raise an AttributeError.

12.5 Three things you can skip

• notifications/initialized is optional. The spec recommends it, but this server does not enforce it — calling tools/call straight after initialize works. Sending it returns an empty 202 response and causes no harm.
• The MCP-Protocol-Version header is optional; an incorrect value does not break the call either.
• A session ID can be reused for many calls — no need to re-initialize each time. If it expires mid-way, redo step one.

12.6 Troubleshooting