Is the Stub Page MCP server down?

mcp-registry/page.stub/stub-page · v0.1.0

healthy
Last checked 2026-10-27 04:15 UTC · handshake 732ms

As of 2026-10-27 04:15 UTC, the Stub Page MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 9 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
99.8%
checks observed
4,682
outages (90d)
9
tools
4

Publish plain-text posts at a public URL. No account, no sign-up.

Point your MCP client at this streamable-http endpoint: https://stub.page/mcp

Agent-readiness: C (72/100)

C (72/100): 0 error(s), 3 warning(s) across 4 tool(s); ~538 tokens of tool definitions.
Scores higher than 7% of 15,786 MCP servers Glimind has audited.
Its tool list costs an agent ~538 tokens per session — lighter than 90% of servers.
70 → 72 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions55
Safety hints0
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (4)

4 of 4 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. How to fix →

Tools: create_page, delete_page, get_page, update_page

3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: create_page, delete_page, update_page

4 parameter(s) across 2 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. How to fix →

Tools: delete_page, update_page

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. How to fix →

Auto-fix: 4 corrected tool definitions

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

create_page 1 change
{
  "name": "create_page",
  "description": "Publish a new text post and return its slug, public URL and edit_key. Content is Markdown (paragraphs, headings, bold, italic, lists, quotes, code, links, and images via external https URLs — images are embedded, never hosted). The returned edit_key is shown exactly once and cannot be recovered. Keep it in context — without it the page can never be edited or deleted again.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "title",
      "content"
    ],
    "properties": {
      "title": {
        "type": "string",
        "maxLength": 200,
        "minLength": 1,
        "description": "Title of the post. The URL is derived from it and never changes afterwards."
      },
      "content": {
        "type": "string",
        "minLength": 1,
        "description": "Markdown content of the post."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Create a page"
}
delete_page 1 change
{
  "name": "delete_page",
  "description": "Permanently delete a post. Requires the edit_key. The slug is never reused and the deletion cannot be undone.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "slug",
      "edit_key"
    ],
    "properties": {
      "slug": {
        "type": "string"
      },
      "edit_key": {
        "type": "string",
        "description": "The key returned by create_page."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  },
  "title": "Delete a page"
}
get_page 1 change
{
  "name": "get_page",
  "description": "Fetch a published post by slug. Public — no edit_key required.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "description": "The slug from the page URL."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Read a page"
}

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/page.stub/stub-page"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/page.stub/stub-page"}) 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%2Fpage.stub%2Fstub-page.svg)](https://glimind.com/server/mcp-registry%2Fpage.stub%2Fstub-page?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fpage.stub%2Fstub-page?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fpage.stub%2Fstub-page.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fpage.stub%2Fstub-page.svg
   :target: https://glimind.com/server/mcp-registry%2Fpage.stub%2Fstub-page?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:e0fb5dea8d083c5d…, first seen 2026-10-17, included at leaf 5583 of 77,299. Version history · verify what your client received.

Tools (4)

Compare: most reliable knowledge 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 Stub Page MCP server down right now?

As of 2026-10-27 04:15 UTC, the Stub Page MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 9 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Stub Page MCP server provide?

Stub Page MCP server advertises 4 tools, including create_page, delete_page, get_page, update_page.

How do I install Stub Page MCP server?

Point your MCP client at this streamable-http endpoint: https://stub.page/mcp

Is the Stub Page MCP server safe to connect to an AI agent?

Glimind scanned all 4 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 Stub Page 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.

Feedback
Help us improve