Connect your assistant
to Haze.

Connect a remote MCP client

Use a client that supports remote Streamable HTTP MCP servers. Add this server URL:

https://haze.danielk.am/mcp

No Haze account, API key or OAuth login is required. The server is public and read-only. It provides request-time tools, not background monitoring or push notifications.

1. Open your client’s MCP or connector settings and choose its remote HTTP server option.
2. Enter the endpoint above. Choose Streamable HTTP if the client asks for a transport.
3. Connect and inspect the four Haze tools. Approve a tool call using your client’s normal controls.
4. Ask for a region and the source times, for example: “Show central Singapore’s 24-hour PSI and 1-hour PM2.5, including their source times and any warnings.”

Client support depends on the installed version, account features and administrator policy. Some clients accept only local commands or a different transport. Check your client’s documentation if the URL field is missing; the public REST API remains available.

Codex CLI

In a Codex CLI version with remote MCP support, add the server:

codex mcp add haze --url https://haze.danielk.am/mcp

Then reopen your Codex session and check that Haze’s tools are available. OpenAI’s official Codex MCP documentation covers MCP configuration and environment-specific restrictions.

A remote-client JSON example

For clients that use the portable mcpServers format with HTTP entries, the configuration is:

{
  "mcpServers": {
    "haze": {
      "type": "http",
      "url": "https://haze.danielk.am/mcp"
    }
  }
}

This is not a universal client configuration file. For example, VS Code’s .vscode/mcp.json uses servers as the top-level key. The official VS Code guide documents both formats. Use the format and location your client requires.

Choose a Haze tool

Results include structured data and a text representation. Product results also include Markdown affiliate links and a commission disclosure. The tools do not place orders, change accounts or store a location. For individual product links, preserve the returned affiliate URL rather than constructing one from the product ID.

Try: “Compare the five regions’ PM2.5 trend over the last 24 hours. Mark missing points.” Or: “Show two air purifiers with their price-check times, product links and affiliate disclosure.”

Test the connection with curl

These requests use the 2025-11-25 MCP protocol version. A normal browser GET to /mcp is not a connection test: this stateless endpoint uses HTTP POST and JSON-RPC.

1. Initialize. Send the client information and the protocol version.

curl --fail-with-body https://haze.danielk.am/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  --data '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-11-25","capabilities":{},"clientInfo":{"name":"haze-curl","version":"1.0.0"}}}'

Expect a JSON-RPC result with the negotiated protocolVersion, server information and tool capability. Use that negotiated version in MCP-Protocol-Version on later requests. The examples below use 2025-11-25.

2. Finish initialization. Send the notification. A notification has no JSON-RPC id.

curl --fail-with-body https://haze.danielk.am/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'MCP-Protocol-Version: 2025-11-25' \
  --data '{"jsonrpc":"2.0","method":"notifications/initialized"}'

3. List the tools. Confirm that the four Haze tool names appear.

curl --fail-with-body https://haze.danielk.am/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'MCP-Protocol-Version: 2025-11-25' \
  --data '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}'

4. Call a tool. Request the west region’s readings.

curl --fail-with-body https://haze.danielk.am/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'MCP-Protocol-Version: 2025-11-25' \
  --data '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"haze_get_conditions","arguments":{"region":"west"}}}'

Read the tool’s result and any isError flag, not just the HTTP status. Haze is stateless, so no session ID needs to be saved. With the 2025 protocol used in these curl examples, the JSON-RPC result is wrapped in a Server-Sent Events response: read the JSON after data:. The response then finishes. This is Streamable HTTP, with no separate /sse endpoint or persistent GET subscription. The MCP transport specification explains the headers and initialization sequence.

Keep readings and recommendations accurate

Tell your assistant to retain each source timestamp and any delayed, partial or unavailable status. A fetch time is not a measurement time. A null value means unavailable data, never zero. Keep gaps in trends visible.

The 24-hour PSI is a measured index; 1-hour PM2.5 is a concentration in µg/m³. The PSI health-advisory table applies to a forecast category and must not be presented as a live forecast from a measured reading. The air-quality guide explains the distinction.

Product links may earn us a commission. Keep the affiliate disclosure beside those links, and show the returned price-check time when quoting a price. Ask readers to check their variant and final price on Shopee. Commercial results do not imply NEA endorsement.

Readings are from NEA via data.gov.sg under the Singapore Open Data Licence. Preserve attribution, source dates and the independent-project disclaimer. Haze’s hosting providers process standard web request information. Your client’s own privacy policy also applies to prompts and tool results it handles.

If the client cannot connect

400 · Request or protocol problem

Use valid JSON-RPC, an accepted protocol version and the exact tool argument names. Don’t add query parameters to the MCP URL.

403 · Host or origin rejected

Use the public HTTPS hostname directly. Browser-based clients with an unapproved Origin cannot call this endpoint. Use a remote client with a server-side HTTP connection, or the public REST API for a browser integration.

405 · Method not allowed

Use the HTTP POST requests above. A normal browser visit or an older SSE-only client does not use this transport.

406 · Response type not accepted

Send Accept: application/json, text/event-stream.

413 · Request too large

Keep the JSON request below 64 KiB. Send the tool arguments only, rather than a conversation history.

415 · Wrong content type

Send Content-Type: application/json.

429 · Request limit reached

Wait for Retry-After seconds. Stop automatic rapid retries and respect the 10-minute data refresh interval.

503 or an error tool result

Read the message, back off and try later. If a source is delayed or unavailable, preserve that state in your answer rather than filling in a value.

If curl succeeds but your assistant cannot connect, check its remote Streamable HTTP support, version and administrator settings. Don’t add an API key: Haze does not require one. To build a direct integration instead, follow the REST API guide.