ai.saifs/data-cleaning

Data Cleaning & Validation for AI Agents

Is the Data Cleaning & Validation for AI Agents MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-14.

Turn messy exports into clean, consistent data agents can trust, with every change logged.

needs auth probed 2026-11-15 · unchanged since 2026-11-14 · HTTP 401 · Bearer

Streamable HTTP error: Error POSTing to endpoint: {"error":"unauthorized","error_description":"Missing or invalid authorization header"}

Endpoint: https://data-cleaning-mcp.saifs.ai/mcp (streamable-http)
Host: data-cleaning-mcp.saifs.ai
Getting access: OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://data-cleaning-mcp.saifs.ai/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server multiplewords.in, PKCE S256, grants authorization_code, client_credentials, refresh_token, urn:ietf:params:oauth:grant-type:device_code.
Scopes read write.
Read from the server's public OAuth metadata, without a token. Method.
Repository: https://github.com/Saify-Technologies/saifs-ai-mcps-docs
Website: https://saifs.ai
Registry: active, updated 2026-11-13 · registry entry

More servers

Servers that mention cleaning.

Servana ai.servana/servana · alive
HomeMaster co.homemaster/homemaster · alive
BackResto Partner API com.backresto/partner-api · needs auth
Black Water Window Cleaning Website MCP com.blackwaterwindowcleaning/site-mcp · not found
Boulder County Dryer Vent Booking com.bouldercountydryervent/booking · no DNS
Sonlight Window Cleaning com.sonlightwindow/booking · alive
Ezi Home Services io.github.EziServices/mcp-public · alive
claw.cleaning io.github.cnnrobrn/claw-cleaning · alive

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.

Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.