Baselight Datasets MCP · Baselight

Not responding as MCP

https://api.baselight.app/mcp

Badge

Not responding as MCPHTTP 530 with content-type text/plain; charset=utf-8 — this does not look like an MCP endpoint.

Since Aug 6, 2026 — 4:55 AM (88 d ago)

0.0%

Availability · 30 days · 8 checks

58 ms

Latency (last observation)

—

Contract

—

Schema stable

Incidents · 30 days

—

Observed since

No failures Some failures Mostly failing Auth required No observations

Last observed 1 d ago by MCP Tools Edge Scanner · scheduled every 120 min

First observation failed Informational Aug 6, 2026 — 4:55 AM

HTTP 530 with content-type text/plain; charset=utf-8 — this does not look like an MCP endpoint.

VerifiedObservation result: not_mcp (HTTP 530).

InterpretationThis endpoint has no successful observation yet. It may be misconfigured, offline, or not an MCP endpoint.

Observed by MCP Tools Edge Scanner

Latest check — evidence & validation Oct 31, 2026 — 7:05 PM

Not an MCP response MCP Tools Edge Scanner ScheduledHTTP 53058 ms

Error detailHTTP 530 with content-type text/plain; charset=utf-8 — this does not look like an MCP endpoint.

response headers (as observed)

{
  "server": "cloudflare",
  "content-type": "text/plain; charset=UTF-8"
}

response body — first bytes

error code: 1016