Is the Spica Post MCP server down?

mcp-registry/com.spicapost/spica-post · registry v1.0.3 · server reports v0.1.0

Also listed as github/unbowedgod/spica-post-mcp

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 14:57 UTC · handshake 533ms

As of 2026-11-22 14:57 UTC, the Spica Post MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
99.9%
checks observed
418
outages (90d)
1
tools
133

Your AI assistant drafts, schedules and posts to your social accounts once you approve.

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

Agent-readiness: B (80/100)

B (80/100): 0 error(s), 3 warning(s) across 133 tool(s); ~45,650 tokens of tool definitions.
Scores higher than 24% of 27,588 MCP servers Glimind has audited.
Its tool list costs an agent ~45,650 tokens per session — more than 99% of servers.
84 → 80 since 2026-11-19
no tool-poisoning patterns
Descriptions100
Safety hints100
Schemas100
Protocol100
Stability20
Token cost22
Reliability100
Client compatibility70

What to fix (5)

7 tool definition(s) exceed ~1,200 tokens each (largest: brand_save, ~2,217).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~8,835 tokens every session. How to fix →

Tools: brand_save, drafts_create_batch, drafts_edit, drafts_create, profile_save and 2 more · saves ~8,835 tokens/session

133 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

Loading this server's tool list costs an agent ~45,650 tokens before any work — more than 99% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

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 →

In the last 30 days: 0 tool(s) removed and 72 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

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.spicapost/spica-post"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.spicapost/spica-post"}) 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.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fcom.spicapost%2Fspica-post.svg)](https://glimind.com/server/mcp-registry%2Fcom.spicapost%2Fspica-post?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.spicapost%2Fspica-post?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fcom.spicapost%2Fspica-post.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:b66d83f8e2935cd0…, first seen 2026-11-21, included at leaf 376244 of 384,105. Version history · verify what your client received.

Tools (133)

Compare: most reliable social servers · most reliable other servers · most reliable communication servers · most reliable productivity servers · most reliable files 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?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the Spica Post MCP server down right now?

As of 2026-11-22 14:57 UTC, the Spica Post MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.

How many tools does Spica Post MCP server provide?

Spica Post MCP server advertises 133 tools, including accounts_board, accounts_connect, accounts_create_test, accounts_disconnect, accounts_list.

How do I install Spica Post MCP server?

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

Is the Spica Post MCP server safe to connect to an AI agent?

Glimind scanned all 133 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 Spica Post 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