Server data from the Official MCP Registry
URL reality check for agents: status, content hash, classification, wayback fallback.
URL reality check for agents: status, content hash, classification, wayback fallback.
Remote endpoints: streamable-http: https://linkpulse-neon.vercel.app/mcp
Valid MCP server (1 strong, 0 medium validity signals). 5 known CVEs in dependencies Imported from the Official MCP Registry.
4 tools verified · Open access · 5 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"io-github-walkojas-boop-linkpulse": {
"url": "https://linkpulse-neon.vercel.app/mcp"
}
}
}From the project's GitHub README.
URL reality check for AI agents. Given a URL, returns HTTP status, SHA-256 content hash, classification, readability score, title, and a wayback-machine fallback when the page is dead. Cached 10 minutes. $0.001 per call. Agents only.
Live endpoint: https://linkpulse-neon.vercel.app/
curl https://linkpulse-neon.vercel.app/ returns a full machine-readable manifest. No HTML. No humans.
Four tools, all agent-callable, structured outputs:
| Endpoint | Purpose |
|---|---|
POST /v1/check | Fetch a URL. Returns status, final URL (after redirects), content hash, classification, readability score, title/description/first-heading when HTML, wayback URL when dead. |
POST /v1/diff | Re-check a URL and tell the agent whether its hash changed since a prior hash. |
POST /v1/resolve | Resolve redirect chain without downloading the body. |
POST /v1/classify | Classify content the agent already has (status + content-type + body sample) — no outbound fetch. |
Every error response includes { error, code, message, fix, docs, http_status } — agents never have to guess.
alive_html · alive_json_api · alive_xml_feed · alive_markdown · alive_pdf · alive_image · alive_binary · empty · dead · redirect_loop · moved_permanent · login_wall · challenge_wall · rate_limited · server_error · unreachable
GET /.well-known/ai-plugin.jsonGET /.well-known/mcp.jsonGET /llms.txtGET /openapi.jsonGET /v1/pricingGET /v1/errors# 1. Mint a key (100 free credits)
curl -X POST https://linkpulse-neon.vercel.app/v1/keys
# 2. Use the key
curl -X POST https://linkpulse-neon.vercel.app/v1/check \
-H "Authorization: Bearer lp_live_..." \
-H "Content-Type: application/json" \
-d '{"url":"https://example.com"}'
Prepaid credits. Single POST returns a payment URL the agent follows autonomously:
curl -X POST https://linkpulse-neon.vercel.app/v1/credits \
-H "Authorization: Bearer lp_live_..." \
-H "Content-Type: application/json" \
-d '{"pack":"starter"}'
Returns { payment_url, x402: { ... } }.
https://linkpulse-neon.vercel.app/mcp (JSON-RPC 2.0, protocol 2024-11-05). Tools: linkpulse_check, linkpulse_diff, linkpulse_resolve, linkpulse_classify.
Apache 2.0.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.