Is the Juzpost MCP server down?

mcp-registry/com.juzpost/mcp · v2.0.0

healthy
Last checked 2026-10-26 20:18 UTC · handshake 345ms

As of 2026-10-26 20:18 UTC, the Juzpost MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
2,242
outages (90d)
0
tools
19

Draft, schedule and publish social posts to X, LinkedIn, Instagram, TikTok, YouTube and more

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

Agent-readiness: B (88/100)

B (88/100): 0 error(s), 2 warning(s) across 19 tool(s); ~13,508 tokens of tool definitions.
Scores higher than 63% of 15,761 MCP servers Glimind has audited.
Its tool list costs an agent ~13,508 tokens per session — more than 85% of servers.
89 → 88 since 2026-10-18
no tool-poisoning patterns
Schemas100
Descriptions57
Safety hints100
Token cost82
Client compatibility100
Protocol100
Reliability100
Stability88

What to fix (3)

3 tool definition(s) exceed ~1,200 tokens each (largest: schedule_post, ~3,367).

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 ~7,947 tokens every session. How to fix →

Tools: schedule_post, update_post, create_post · saves ~7,947 tokens/session

15 parameter(s) across 9 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: create_post, delete_post, list_posts, schedule_post, update_post and 4 more

In the last 30 days: 0 tool(s) removed and 3 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.juzpost/mcp"],"email":"[email protected]"}'

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

Tools (19)

Compare: most reliable communication servers · most reliable files servers · most reliable knowledge servers · most reliable social servers · most reliable workspace 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 Juzpost MCP server down right now?

As of 2026-10-26 20:18 UTC, the Juzpost MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Juzpost MCP server provide?

Juzpost MCP server advertises 19 tools, including create_post, create_upload_url, delete_post, get_context, get_platform_limits.

How do I install Juzpost MCP server?

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

Is the Juzpost MCP server safe to connect to an AI agent?

Glimind scanned all 19 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 Juzpost 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