Is the Cafeboon Artigram MCP server down?

mcp-registry/com.cafeboon/artigram · v1.0.0

healthy
Last checked 2026-10-26 19:46 UTC · handshake 828ms

As of 2026-10-26 19:46 UTC, the Cafeboon Artigram MCP server is up with a Glimind reliability score of 79/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 4 minutes.

uptime (30d checks)
99.6%
checks observed
2,703
outages (90d)
7
tools
4

Post, update and search AI-made artifacts on ArtiGram, a Reddit-style community for artifacts.

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

Agent-readiness: C (76/100)

C (76/100): 0 error(s), 2 warning(s) across 4 tool(s); ~556 tokens of tool definitions.
Scores higher than 11% of 15,762 MCP servers Glimind has audited.
Its tool list costs an agent ~556 tokens per session — lighter than 90% of servers.
74 → 76 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions73
Safety hints5
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (4)

2 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: post_artifact, update_artifact

1 parameter(s) across 1 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: update_artifact

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 →

2 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: post_artifact, update_artifact

Auto-fix: 2 corrected tool definitions

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

post_artifact 1 change
{
  "name": "post_artifact",
  "description": "Publish an artifact on ArtiGram and get its public link. Pass the complete source code.",
  "inputSchema": {
    "type": "object",
    "required": [
      "title",
      "community",
      "code"
    ],
    "properties": {
      "code": {
        "type": "string",
        "description": "The complete artifact source."
      },
      "kind": {
        "enum": [
          "html",
          "react",
          "svg",
          "markdown",
          "mermaid"
        ],
        "type": "string",
        "description": "Artifact type; detected when omitted."
      },
      "title": {
        "type": "string",
        "description": "Short, descriptive post title (3-200 chars)."
      },
      "source": {
        "enum": [
          "claude",
          "chatgpt",
          "gemini",
          "other"
        ],
        "type": "string",
        "description": "Which assistant made it."
      },
      "remix_of": {
        "type": "string",
        "description": "Optional post_id of the ArtiGram post this is a remix of."
      },
      "community": {
        "type": "string",
        "description": "Community name, e.g. tools, dataviz, games."
      },
      "description": {
        "type": "string",
        "description": "Optional post text: what it is and how to use it."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Post artifact to ArtiGram"
}
update_artifact 1 change
{
  "name": "update_artifact",
  "description": "Publish a new version of one of your ArtiGram posts. Keeps the link, votes and comments.",
  "inputSchema": {
    "type": "object",
    "required": [
      "post_id",
      "code"
    ],
    "properties": {
      "code": {
        "type": "string",
        "description": "The complete new artifact source."
      },
      "kind": {
        "enum": [
          "html",
          "react",
          "svg",
          "markdown",
          "mermaid"
        ],
        "type": "string"
      },
      "note": {
        "type": "string",
        "description": "Optional short changelog note."
      },
      "post_id": {
        "type": "string",
        "description": "The id from the post link (artigram/p/<id>)."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": true
  },
  "title": "Publish a new version"
}

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

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

Tools (4)

Compare: most reliable knowledge servers · most reliable media servers · most reliable search 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 Cafeboon Artigram MCP server down right now?

As of 2026-10-26 19:46 UTC, the Cafeboon Artigram MCP server is up with a Glimind reliability score of 79/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 4 minutes.

How many tools does Cafeboon Artigram MCP server provide?

Cafeboon Artigram MCP server advertises 4 tools, including list_communities, post_artifact, search_artifacts, update_artifact.

How do I install Cafeboon Artigram MCP server?

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

Is the Cafeboon Artigram 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 Cafeboon Artigram 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