mcp-registry/app.sprkly/sprkly · v1.0.0
As of 2026-10-23 17:23 UTC, the Sprkly MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 7 minutes.
Schedule, publish and track social posts across TikTok, Instagram, Threads and YouTube Shorts.
Claude Code
claude mcp add --transport http sprkly-mcp-server https://sprkly.app/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"sprkly-mcp-server": {
"type": "http",
"url": "https://sprkly.app/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
1 tool definition(s) exceed ~1,200 tokens each (largest: sprkly_schedule_post, ~1,793).
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 ~1,193 tokens every session. How to fix →
1 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 →
Handshake + tools/list takes ~2,144 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. How to fix →
In the last 30 days: 0 tool(s) removed and 19 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 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/app.sprkly/sprkly"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/app.sprkly/sprkly"}) over MCP.
sprkly_schedule_post ~1,793 tokenssprkly_create_automation_from_template ~519 tokenssprkly_upload_media ~474 tokenssprkly_update_scheduled_post ~344 tokenssprkly_validate_post_policy ~316 tokensStatic 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:
[](https://glimind.com/server/mcp-registry%2Fapp.sprkly%2Fsprkly?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fapp.sprkly%2Fsprkly?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.sprkly%2Fsprkly.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.sprkly%2Fsprkly.svg :target: https://glimind.com/server/mcp-registry%2Fapp.sprkly%2Fsprkly?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3038dc5987577dda…, first seen 2026-10-23, included at leaf 50309 of 53,281. Version history · verify what your client received.
Compare: most reliable media servers · most reliable communication servers · most reliable productivity servers · most reliable analytics servers · most reliable finance servers
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.
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"
}
}
}
As of 2026-10-23 17:23 UTC, the Sprkly MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 7 minutes.
Sprkly MCP server advertises 31 tools, including sprkly_add_media_from_url, sprkly_create_automation_from_template, sprkly_delete_scheduled_post, sprkly_draft_post, sprkly_export_automation_template.
Point your MCP client at this streamable-http endpoint: https://sprkly.app/api/mcp
Glimind scanned all 31 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.
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.