mcp-registry/com.tweetsmash/mcp · v2.1.0
As of 2026-10-17 21:26 UTC, the Tweetsmash MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 5 minutes.
Search, label, and manage your X (Twitter) bookmarks from any MCP client via Tweetsmash
Claude Code
claude mcp add --transport http tweetsmash-mcp-server https://mcp.tweetsmash.com/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"tweetsmash-mcp-server": {
"type": "http",
"url": "https://mcp.tweetsmash.com/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
53 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.
36 parameter(s) across 12 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.
3 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays.
Handshake + tools/list takes ~1,918 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.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 12 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.tweetsmash%2Fmcp/fixes
{
"name": "create_smart_view",
"description": "Create a Smart View from a filter so the user can reuse it. Provide a name and the base_query (filter).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"minLength": 1,
"description": "View name."
},
"base_query": {
"type": "string",
"description": "The filter query that defines the view."
},
"description": {
"type": "string"
},
"default_sort": {
"type": "string"
},
"triage_buckets": {
"description": "Optional tab/bucket definitions.",
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"title": "create_smart_view",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}{
"name": "update_digest_preference",
"description": "Update a digest schedule (enable/pause, frequency, time) by id.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "The digest preference id to update."
},
"is_paused": {
"type": "boolean"
},
"week_info": {
"type": "string"
},
"is_enabled": {
"type": "boolean"
},
"time_to_read": {
"type": "string"
},
"schedule_time": {
"type": "string"
},
"send_frequency": {
"type": "string",
"description": "e.g. DAILY, WEEKLY."
}
},
"additionalProperties": false
},
"annotations": {
"title": "update_digest_preference",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}{
"name": "update_smart_view",
"description": "Update a Smart View (name, filter, tabs, sort) by slug.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"slug"
],
"properties": {
"name": {
"type": "string"
},
"slug": {
"type": "string",
"minLength": 1,
"description": "The smart view slug to update."
},
"base_query": {
"type": "string"
},
"description": {
"type": "string"
},
"default_sort": {
"type": "string"
},
"triage_buckets": {
"type": "string"
}
},
"additionalProperties": false
},
"annotations": {
"title": "update_smart_view",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}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.tweetsmash/mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.tweetsmash/mcp"}) over MCP.
search_bookmarks ~706 tokenslist_bookmarks ~602 tokenslist_likes ~581 tokenstag_bookmarks_by_filter ~507 tokensget_bookmark_count ~403 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%2Fcom.tweetsmash%2Fmcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.tweetsmash%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.tweetsmash%2Fmcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.tweetsmash%2Fmcp.svg :target: https://glimind.com/server/mcp-registry%2Fcom.tweetsmash%2Fmcp?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:653548e13054ff41…, first seen 2026-10-17, included at leaf 2432 of 18,672. Version history · verify what your client received.
Compare: most reliable social media servers · most reliable files servers · most reliable knowledge servers · most reliable data servers · most reliable email 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-17 21:26 UTC, the Tweetsmash MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 5 minutes.
Tweetsmash MCP server advertises 53 tools, including add_labels_to_tweets, archive_bookmarks, archive_bookmarks_by_filter, compose_mash_digest, correct_interest.
Point your MCP client at this streamable-http endpoint: https://mcp.tweetsmash.com/api/mcp
Glimind scanned all 53 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.