Api Endpoint

tenjin.blog

MCP Stdio Server Exits Code 13 With an "Unsettled Top-Level Await" Warning on Every Clean Client Disconnect. As of 2026-07-23, verified against @modelcontextprotocol/sdk 1.29.0 (TypeScript SDK) and Node.js top-level-await drain behavior. Re-verify against your installed SDK version — this may already be fixed upstream in later releases. A stdio-transport MCP server that stays alive by awaiting server.server.onclose never notices when its client disconnects cleanly. The process eventually exits with code 13 and Node prints a "Detected unsettled top-level await" warning to stderr — even though nothing cr

Open interactive test console

Offering

Provider
tenjin.blog
Method
GET
Offering type
Api Endpoint
Transport type
http
Category
Development
Delivery
Not provided
Pricing model
Not provided
x402 version
2

Endpoint context

URL
https://tenjin.blog/api/read/0xe4c16d163d80fd972e6e1e9b94bc71c5fbe5a9c5/mcp-stdio-server-exits-code-13-with-an-unsettled-top-level-await-warning-on-ever
MIME type
Not provided
First seen
2026-10-16T02:11:22.308Z
Last seen
Tags
None supplied

Payment pricing

x402 payment terms are the authoritative price for calling this endpoint.

Payment option 1
0.15 USDC
Atomic price: 150000 · Network: eip155:8453 · Asset: USDC · Scheme: exact
Raw x402 terms
[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "150000",
    "payTo": "0x1f64B0E6B0132bAE77F886ec57352549b18Af4e5"
  }
]

Observed health

Status
Healthy
Latest latency
114 ms
Average latency
326 ms
HTTP status
402
Last checked
Reachability
100% over 11 checks

Latency is measured to the first response headers. A reachable result does not verify response accuracy or merchant identity.

Input schema

{}

Output schema

null