Twitter Like Checker avatar
Twitter Like Checker

Pricing

$25.00/month + usage

Go to Store
Twitter Like Checker

Twitter Like Checker

Developed by

Deepanshu Sharma

Deepanshu Sharma

Maintained by Community

A Twitter Like Checker that checks if a specific user has liked your particular tweet. This tool is perfect for social media analytics, engagement tracking, and verification purposes.

0.0 (0)

Pricing

$25.00/month + usage

0

Total users

3

Monthly users

3

Runs succeeded

>99%

Last modified

3 days ago

You can access the Twitter Like Checker programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in Integrations settings in Apify Console.

{
"mcpServers": {
"apify": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.apify.com/sse?actors=deepanshusharm/twitter-like-checker",
"--header",
"Authorization: Bearer <YOUR_API_TOKEN>"
]
}
}
}

Configure MCP server with Twitter Like Checker

You have a few options for interacting with the MCP server:

  • Use mcp.apify.com via mcp-remote from your local machine to connect and authenticate using OAuth or an API token (as shown in the JSON configuration above).

  • Set up the connection directly in your MCP client UI by providing the URL https://mcp.apify.com/sse?actors=deepanshusharm/twitter-like-checker along with an API token (or use OAuth).

  • Connect to mcp.apify.com via Server-Sent Events (SSE), as shown below:

{
"mcpServers": {
"apify": {
"type": "sse",
"url": "https://mcp.apify.com/sse?actors=deepanshusharm/twitter-like-checker",
"headers": {
"Authorization": "Bearer <YOUR_API_TOKEN>"
}
}
}
}

You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other MCP client of your choice.

If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.