Agent MCP Directory

TweetSave: MCP server, CLI and agent surfaces

Yes: TweetSave runs a public MCP server at mcp.tweetsave.org that listed 5 tools to a client with no credentials on 4 November 2026. Examples: tweetsave_get_tweet, tweetsave_get_thread, tweetsave_to_blog. It speaks sse, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool.

Fact sheet

CompanyTweetSave
Domaintweetsave.org
CategoryUncategorised (assigned by this directory from the registry description)
MCP serverVerified (No authentication)
Ora scorenone: Ora returned no cached score for tweetsave.org when asked on 5 November 2026
Company found throughthe awesome-remote-mcp-servers list
Last verified4 November 2026

MCP server

Endpointhttps://mcp.tweetsave.org/sse
How it was foundlisted in the awesome-remote-mcp-servers list
Transportsse
HTTP status200
Protocol version2025-11-25
Servertweetsave-mcp-server 1.0.0
Capabilitiestools
Tools5
Resources0
Prompts0
Connected4 November 2026, 20:04 UTC
Handshake time870 ms over 2 attempts

Tools listed

5 tools

  • tweetsave_get_tweet
  • tweetsave_get_thread
  • tweetsave_to_blog
  • tweetsave_batch
  • tweetsave_extract_media

Connector log

2 connections on 4 November 2026, read-only methods only

  • 20:00:03Z https://mcp.tweetsave.org/sse sent initialize, initialize, notifications/initialized, tools/list result verified (HTTP 200) 791 ms
  • 20:04:57Z https://mcp.tweetsave.org/sse sent initialize, initialize, notifications/initialized, tools/list result verified (HTTP 200) 870 ms

Authentication

Auth typeNo authentication
Auth as listed by a registryOpen (a claim, not checked by connecting)

The sign-in route, step by step

  1. Send the handshake to https://mcp.tweetsave.org/sse over sse. Servers on the 2026-07-28 revision answer server/discover; older servers answer initialize.
  2. Send tools/list, then resources/list and prompts/list if the capabilities name them.
  3. Send no token. The connector sent none and the server answered, so any MCP client can read this list.
  4. Calling a tool is a separate step this directory never takes.

See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.

CLI

No CLI is on record for TweetSave. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See shipping a CLI agents can use.

Other agent surfaces

Agent surfaces other than MCP and CLI
SurfaceResult
OpenAPI fileNo OpenAPI file at the root paths checked.
WebMCP in the initial HTMLNot checked: the home page was not read by the shared crawl.
MCP discovery fileNot checked: the domain is not in the shared crawl for this edition.
A2A agent cardNot checked: the domain is not in the shared crawl for this edition.
A2A agent card (older path)Not checked: the domain is not in the shared crawl for this edition.
agents.jsonNot checked: the domain is not in the shared crawl for this edition.
OAuth authorization server metadataNot checked: the domain is not in the shared crawl for this edition.
NLWeb endpointNot checked in this edition.

Registry listings

Registry listings
RegistryListed
Official MCP RegistryNo
GitHub MCP RegistryNo
awesome-remote-mcp-serversYes
SmitheryNot checked: Smithery's listing pages and search API were unavailable on 4 November 2026.
GlamaNot checked: Glama's API needs a key and attribution terms.