LinkPulse

io.github.walkojas-boopPublished by GitHub account walkojas-boopv1.0.0Updated Oct 25, 2026

URL reality check for agents: status, content hash, classification, wayback fallback.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingSecurity & Monitoring

Overview

AI-generated overview

LinkPulse is a remote MCP server that lets an assistant check a URL's live status, content hash, redirects and classification, with a Wayback fallback for dead.

What you can do
Check a URL's current state: HTTP status, final URL after redirects, SHA-256 content hash, classification, readability score, title and meta description, with a Wayback archive fallback if the page is dead (results cached 10 minutes). Compare a URL's content hash against a previous hash to see whether its content changed. Resolve a URL's redirect chain without downloading the full body. Classify content the assistant already has, from a status code, content type and body sample, without an outbound fetch.
When to use it
Useful when an assistant needs to verify that links are alive, detect whether a page's content changed, trace where a URL redirects, or classify pages it has already fetched. A lightweight fit for link checking and content monitoring in agent workflows.
Requirements
A remote streamable HTTP endpoint; no local runtime, package, account, API key or header is declared. The server fetches URLs on its behalf, so it needs network access.
Before you install
The server performs outbound fetches of URLs you give it, so those URLs are sent to a third-party service. Results are cached for 10 minutes, so very recent changes may not appear. No authentication is declared, so anyone with the endpoint can use it.

Installation

In SourceWeft

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

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.walkojas-boop%2Flinkpulse/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "linkpulse": {
      "type": "http",
      "url": "https://linkpulse-neon.vercel.app/mcp"
    }
  }
}

README

This repository has no README.

Tools

4

linkpulse_check

Fetch a URL and return its current state: HTTP status, final URL after redirects, SHA-256 content hash, classification, readability score, title/meta-description, and wayback archive fallback if dead. Cached 10 minutes.

Parametersurlrequiredmax_bytestimeout_msforce_freshinclude_body_sample

linkpulse_diff

Re-check a URL and tell you whether its content hash has changed since a previous hash you supply. Returns boolean + new hash.

Parametersurlrequiredprevious_hashrequired

linkpulse_resolve

Resolve redirect chain for a URL without downloading the full body. Returns final URL + redirect count.

Parametersurlrequired

linkpulse_classify

Classify content you already have (status code + content-type + body sample) without an outbound fetch. Useful if your agent already fetched the URL via another tool.

Parametersstatusrequiredbody_samplerequiredcontent_typerequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.