Should my agent depend on the MCP server com.tweetsmash/mcp?

Verdict: allow — rich-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

mcp

com.tweetsmash/mcp

Search, label, and manage your X (Twitter) bookmarks from any MCP client via Tweetsmash

— the operator's own registry description reported

Publisher com.tweetsmash · first seen 2026-08-12 · endpoint https://mcp.tweetsmash.com/api/mcp

allow

verdict

rich-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-solo — safe to depend on

Cluster rich-solo · distinctiveness 0.386 (moderate). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency121 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools39

vs populationhigh

capabilities1

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_c1e22b47de424b27234a24ec · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

add_labels_to_tweets archive_bookmarks archive_bookmarks_by_filter create_share_link create_smart_view delete_digest_preference delete_smart_view fetch_recent_bookmarks forget get_bookmark get_bookmark_count get_bookmark_sync_status get_connection_status get_list_digests get_list_tweets get_me get_smart_view get_smart_view_bookmarks get_sync_status list_bookmarks list_digest_preferences list_labels list_past_digests list_smart_views list_twitter_lists recall remember remove_labels_from_tweets revoke_share_link search_bookmarks search_docs send_list_digest setup_vector_store tag_bookmarks_by_filter trigger_csv_export trigger_json_export trigger_pdf_export update_digest_preference update_smart_view

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	39/39	✓
has a description	39/39	✓
description is substantive	37/39	37/39
parameters are typed	36/39	36/39
parameters are described	27/39	27/39

39 of 39 tools graded · 39 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

0.1.0

server version mcp-typescript server on vercel

Capabilities: tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:58:36Z	ok_tools	200	121	2025-06-18
2026-08-12T05:33:50Z	ok_tools	200	88	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/com.tweetsmash/mcp.svg)](https://robinsaige.com/s/com.tweetsmash/mcp)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview