Data · Remote MCP server
lintlab SEO Site QA
Crawl a site for broken links, redirects and missing SEO tags. Pay per page on Apify.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.lintlab/seo-site-qa- Version
- 1.0.0
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP
- Published
- 2026-09-26
- Updated
- 2026-09-26
- Publisher
- lintlab (GitHub) · 4 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/lintlab) · how
- Listed under
- Apify MCP servers
- Website
- apify.com/lintlab/seo-site-qa
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.apify.com?tools=lintlab/seo-site-qa | Authorization (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; a Bearer token is asked for
- Checked on
- 2026-10-05
How to connect lintlab SEO Site QA
lintlab SEO Site QA is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.apify.com?tools=lintlab/seo-site-qa, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from lintlab (GitHub)
| Server | Runs |
|---|---|
| lintlab PDF To MarkdownConvert PDF URLs to clean Markdown and text for RAG and LLM input. Pay per PDF on Apify. | Remote · HTTPLive check: sign-in required |
| lintlab Screenshot DiffFull-page website screenshots and visual diffs between two captures. Pay per capture on Apify. | Remote · HTTPLive check: sign-in required |
| lintlab Sitemap ValidatorFind, validate and extract XML sitemaps (gzip, indexes) with lastmod. Pay per result on Apify. | Remote · HTTPLive check: sign-in required |
More data servers
| Server | Runs |
|---|---|
| LinklyCreate short links, manage domains, and track click analytics. | Local · stdio |
| LinkShrink MCPPrivacy-first URL shortener with analytics. | Local · stdio |
| LinkupSearch the web and fetch pages with sourced results, optimized for AI agents. | Local · stdio |
| LinkupSearch the web in real time to get trustworthy, source-backed answers. | Remote · HTTP, SSELive check: ✓ SSE reachable |
| LINZALocal-first MCP sidecar for Markdown artifacts, review intents, and supervised knowledge growth. | Local · stdio |
| LION - Trend Intent MCP + Marketplace Visibility AuditX402-paid MCP data: trend feed + visibility audit. USDC/Base. No API key. No PII. | Remote · HTTPLive check: ✓ handshake |
| LiongardMCP server for Liongard - inspectors, environments, metrics, detections, and timeline data. | Local · stdio |
| LiongardMCP server for Liongard - inspectors, environments, metrics, detections, and timeline data. | Local · stdio |