Free, agent-first social-post metrics — a post URL in, views/likes/comments out.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-patwalls-pulse-mcp": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Free, agent-first social-post metrics — a post URL in, views/likes/comments out.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in analytics
⚡ A Simple / Speedy / Secure Link Shortener with Analytics, 100% run on Cloudflare.
MCP Server for GCP environment for interacting with various Observability APIs.
Data observability tools for engineering teams: alerts, freshness, schema drift, lineage, quality.
MCP server for Dynatrace Managed to access logs, events, and metrics.
MCP Security Weekly
Get CVE alerts and security updates for io.github.patwalls/pulse-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
MCP server for Pulse — a free, agent-first social-post metrics API. Give any MCP client (Claude Desktop, Cursor, …) the numbers behind any public post: hand it a URL, get back views, likes, comments, and the publish date as clean JSON. No signup, no API key.
{ "mcpServers": { "pulse": { "command": "npx", "args": ["-y", "pulse-mcp"] } } }
That's it — drop it in your MCP config and your agent has four new tools.
| Tool | Input | Output |
|---|---|---|
metrics | one post URL (short links like vm.tiktok.com/t.co OK) | { platform, views, likes, comments, shares, quotes, bookmarks, publishedAt, title, author, thumbnail } |
metrics_batch | many URLs (mixed post + profile URLs welcome) | the same, one per URL (partial failures don't fail the batch) |
history | one post or profile URL (+ optional since for the delta) | the recorded growth curve — { count, points } (posts: { t, views, likes, comments }, profiles: { t, followers, posts }), a snapshot per fresh fetch |
profile | one profile URL | account-level metrics — { handle, name, followers, following, posts, verified, avatar } (YouTube, TikTok, Instagram, X, Bluesky, Mastodon) |
Example — ask your agent "how did this video do?" with a link, and it gets:
{
"platform": "youtube",
"views": 1781088936,
"likes": 19147197,
"comments": null,
"publishedAt": "2009-10-25T06:57:33.000Z",
"title": "Rick Astley - Never Gonna Give You Up (Official Video)"
}
| Platform | Returns | Notes |
|---|---|---|
| YouTube | views, likes | |
| X / Twitter | views, likes, comments, shares (retweets), quotes, bookmarks | views via X's own guest API (tweets since ~Dec 2022) |
| TikTok | views, likes, comments, shares | |
| Bluesky | likes, comments, shares (reposts), quotes | public AppView API; Bluesky has no view counts |
| Mastodon | likes, boosts, replies | per-instance public REST API (major instances) |
| views, likes, comments | public posts via the guest API | |
| Threads, LinkedIn | — | need a logged-in session; returns a clear login_required (never fake zeros) |
It reads each platform's own public pages from a residential IP, so it sees what a browser
sees — and it's honest about the edges: a deleted/private post comes back content_unavailable,
a login-walled one login_required, never a silent row of zeros.
PULSE_API_URL — override the backend (defaults to https://pulse.walls.sh).Built in public as Wall #002 of walls.sh. Docs: https://pulse.walls.sh/docs ·
machine-readable: /llms.txt · OpenAPI.
MIT.