LinkPulse
Blocks loopback addresses as part of SSRF protection, preventing agents from accessing internal loopback interfaces and local network resources for security purposes.
Classifies and analyzes markdown content through the classification system, identifying markdown documents as 'alive_markdown' and providing content analysis capabilities for markdown-formatted web pages.
Hosted on Vercel with the live endpoint at linkpulse-neon.vercel.app, providing scalable deployment and serverless execution of URL checking and content analysis services.
Classifies and analyzes XML feeds through the classification system, identifying XML content as 'alive_xml_feed' and providing structured analysis of XML-based web content and feeds.
linkpulse
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.
What it does
Four tools, all agent-callable, structured outputs:
Endpoint | Purpose |
| Fetch a URL. Returns status, final URL (after redirects), content hash, classification, readability score, title/description/first-heading when HTML, wayback URL when dead. |
| Re-check a URL and tell the agent whether its hash changed since a prior hash. |
| Resolve redirect chain without downloading the body. |
| 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.
Classifications
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
Discovery (no humans required)
GET /.well-known/ai-plugin.jsonGET /.well-known/mcp.jsonGET /llms.txtGET /openapi.jsonGET /v1/pricingGET /v1/errors
Auth
# 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"}'Billing
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: { ... } }.
MCP
https://linkpulse-neon.vercel.app/mcp (JSON-RPC 2.0, protocol 2024-11-05). Tools: linkpulse_check, linkpulse_diff, linkpulse_resolve, linkpulse_classify.
Safety
SSRF blocked: loopback, RFC 1918, link-local, metadata.internal all refused with a structured error.
Max 1.5 MB body. 6 s default timeout.
License
Apache 2.0.
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/walkojas-boop/linkpulse'
If you have feedback or need assistance with the MCP directory API, please join our Discord server