Pulse Mcp

io.github.patwallsPublished by GitHub account patwallsv0.12.0Updated Oct 10, 2026

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

VerifiedSTDIODesktop onlyWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

A local MCP server that turns public social post and profile URLs into metrics such as views, likes, comments and followers.

What you can do
Fetch metrics for a single post URL, including short links, as structured JSON with views, likes, comments, shares and publish date. Batch-fetch metrics for many post or profile URLs at once, with partial failures not failing the whole batch. Retrieve recorded growth history for a post or profile, optionally since a given time. Look up account-level profile metrics such as followers, following, posts and verification. Batch-compare profiles, up to 50 URLs, with order preserved.
When to use it
Useful when an assistant needs to answer questions about how a public social post or creator account is performing, or to compare follower counts across several creators, without signing up for an API.
Requirements
Runs locally over stdio, typically launched with npx from the npm package pulse-mcp. No account, API key or wallet is needed. Network access is required; the optional PULSE_API_URL environment variable overrides the default backend endpoint.
Before you install
Requests are routed through the provider's backend, which reads platform pages from a residential IP, so the URLs you submit and the results pass through a third party. Some platforms are login-walled: LinkedIn post metrics and profiles, and Threads post metrics, return login_required. Coverage and returned fields vary by platform, and some values may be null.

Installation

In SourceWeft

  1. Open Pulse Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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.

json
{ "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:

json
{  "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.

Source: README.md at commit e9f4eff

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.12.0LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.