Is the Offdayly Site MCP server down?

mcp-registry/com.offdayly/site · v1.0.0

down
Last checked 2026-10-17 11:43 UTC · handshake 3.1s

As of 2026-10-17 11:43 UTC, the Offdayly Site MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 93.4% of Glimind's liveness checks. It had 310 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
93.4%
checks observed
3,728
outages (90d)
310
tools
7

Offdayly: the site's own MCP server — dataset; every answer cites the site.

Point your MCP client at this streamable-http endpoint: https://offdayly.com/mcp

Agent-readiness: D (63/100)

D (63/100): 2 error(s), 3 warning(s) across 7 tool(s); ~751 tokens of tool definitions.
Scores higher than 1% of 15,272 MCP servers Glimind has audited.
Its tool list costs an agent ~751 tokens per session — more than 15% of servers.
no tool-poisoning patterns
Schemas100
Descriptions40
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability0
Stability100

What to fix (6)

The endpoint did not complete an MCP handshake.

Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST.

Reachable 93.4% of the time over the last 30 days; median recovery 7 min.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

7 of 7 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones.

Tools: dataset_columns, dataset_compare, dataset_provenance, dataset_row, dataset_search and 2 more

8 parameter(s) across 5 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call.

Tools: dataset_compare, dataset_row, dataset_search, dataset_stats, dataset_top

Handshake + tools/list takes ~2,347 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably.

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 5 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.offdayly%2Fsite/fixes

dataset_compare 1 change
{
  "name": "dataset_compare",
  "description": "The rows of the Offdayly dataset whose column is any of the given values, in the order given — for \"X vs Y\" questions.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "column",
      "values"
    ],
    "properties": {
      "column": {
        "type": "string",
        "minLength": 1
      },
      "values": {
        "type": "array",
        "items": {
          "type": "string",
          "minLength": 1
        },
        "maxItems": 10,
        "minItems": 2
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Compare rows side by side"
}
dataset_search 1 change
{
  "name": "dataset_search",
  "description": "Rows of the Offdayly dataset whose cells contain the query (case-insensitive), up to 50.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "query"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "maximum": 50,
        "minimum": 1
      },
      "query": {
        "type": "string",
        "minLength": 1,
        "description": "text to look for in any cell"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Search the dataset"
}
dataset_stats 1 change
{
  "name": "dataset_stats",
  "description": "count, min, max, mean, median and sum of a numeric column of the Offdayly dataset (grouping commas and currency are handled; non-numeric rows are excluded and counted).",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "column"
    ],
    "properties": {
      "column": {
        "type": "string",
        "minLength": 1
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Summary statistics for a numeric column"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.offdayly/site"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.offdayly/site"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.offdayly%2Fsite.svg)](https://glimind.com/server/mcp-registry%2Fcom.offdayly%2Fsite?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.offdayly%2Fsite?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.offdayly%2Fsite.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.offdayly%2Fsite.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.offdayly%2Fsite?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:72e0dc02f4878085…, first seen 2026-10-17, included at leaf 1046 of 17,511. Version history · verify what your client received.

Working alternatives

Tools (7)

Compare: most reliable data servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Offdayly Site MCP server down right now?

As of 2026-10-17 11:43 UTC, the Offdayly Site MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 93.4% of Glimind's liveness checks. It had 310 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Offdayly Site MCP server provide?

Offdayly Site MCP server advertises 7 tools, including dataset_columns, dataset_compare, dataset_provenance, dataset_row, dataset_search.

How do I install Offdayly Site MCP server?

Point your MCP client at this streamable-http endpoint: https://offdayly.com/mcp

Is the Offdayly Site MCP server safe to connect to an AI agent?

Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Offdayly Site MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.