Back to Browse

Pulse MCP Server

Developer ToolsLow Risk10.0MCP RegistryLocal
Free

Server data from the Official MCP Registry

Free, agent-first social-post metrics — a post URL in, views/likes/comments out.

About

Free, agent-first social-post metrics — a post URL in, views/likes/comments out.

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (2 strong, 4 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry. Trust signals: trusted author (3/3 approved).

3 files analyzed · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-patwalls-pulse-mcp": {
      "args": [
        "-y",
        "pulse-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

pulse-mcp

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 five new tools.

Tools

ToolInputOutput
metricsone post URL (short links like vm.tiktok.com/t.co OK){ platform, views, likes, comments, shares, quotes, bookmarks, publishedAt, title, author, thumbnail }
metrics_batchmany URLs (mixed post + profile URLs welcome)the same, one per URL (partial failures don't fail the batch)
historyone 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
profileone profile URLaccount-level metrics — { handle, name, followers, following, posts, verified, avatar } (YouTube, TikTok, Instagram, X, Bluesky, Mastodon)
profile_batchmany profile URLs (max 50)same as profile, one per URL — order preserved; partial failures don't fail the batch. Compare follower counts across a list of creators.

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 coverage

PlatformReturnsNotes
YouTubeviews, likes
X / Twitterviews, likes, comments, shares (retweets), quotes, bookmarksviews via X's own guest API (tweets since ~Dec 2022)
TikTokviews, likes, comments, shares
Blueskylikes, comments, shares (reposts), quotespublic AppView API; Bluesky has no view counts
Mastodonlikes, boosts, repliesper-instance public REST API (major instances)
Instagramviews, likes, commentspublic posts via the guest API
Threadspost metrics need a loginpost metrics → login_required; profile metrics (followers/verified) work via /profile
LinkedIn— (posts need login)post metrics → login_required; profiles also login-walled

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.

Config

  • Free — no account, no key, no wallet.
  • 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.

Reviews

No reviews yet

Be the first to review this server!