Is the Serpzilla MCP server down?

mcp-registry/com.serpzilla/mcp · v2.0.0

down
Last checked 2026-10-18 09:19 UTC · handshake 10.5s

As of 2026-10-18 09:19 UTC, the Serpzilla MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 21 outages in 90 days, with a median recovery of 5 minutes.

uptime (30d checks)
99.6%
checks observed
3,444
outages (90d)
21
tools
28

Enables AI assistants to natively interact with the Serpzilla link-building marketplace.

Point your MCP client at this streamable-http endpoint: https://mcp.serpzilla.com/mcp

Agent-readiness: F (53/100)

F (53/100): 1 error(s), 6 warning(s) across 28 tool(s); ~14,872 tokens of tool definitions.
Scores higher than 0% of 15,312 MCP servers Glimind has audited.
Its tool list costs an agent ~14,872 tokens per session — more than 90% of servers.
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints3
Token cost45
Client compatibility100
Protocol100
Reliability0
Stability100

What to fix (7)

The endpoint did not complete an MCP handshake.

Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →

3 tool definition(s) exceed ~1,200 tokens each (largest: search_rent_sites, ~2,292).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~4,915 tokens every session. How to fix →

Tools: search_rent_sites, search_context_sites, search_sites · saves ~4,915 tokens/session

28 of 28 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: add_article, add_texts, blacklist_add_domains, blacklist_delete_domains, blacklist_get and 23 more

26 parameter(s) across 26 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: add_article, add_texts, blacklist_add_domains, blacklist_delete_domains, blacklist_get and 21 more

6 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: blacklist_delete_domains, create_project, favorites_delete_domains, favorites_move_domains, set_limits and 1 more

Loading this server's tool list costs an agent ~14,872 tokens before any work — more than 90% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

Handshake + tools/list takes ~2,599 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

Auto-fix: 24 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 26 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.serpzilla%2Fmcp/fixes

add_article 1 change
{
  "name": "add_article",
  "description": "Create a new Serpzilla Guest Post article (Advertiser's Article) for a project. Returns articleId and urlId needed for purchase.",
  "inputSchema": {
    "type": "object",
    "$defs": {
      "AddArticleArgs": {
        "type": "object",
        "title": "AddArticleArgs",
        "required": [
          "project_id",
          "url",
          "title",
          "body",
          "meta_title"
        ],
        "properties": {
          "url": {
            "type": "string",
            "title": "Url",
            "description": "Promoted URL (e.g., https://example.com)"
          },
          "body": {
            "type": "string",
            "title": "Body",
            "maxLength": 64000,
            "description": "Article HTML text, must contain at least one link"
          },
          "title": {
            "type": "string",
            "title": "Title",
            "minLength": 2,
            "description": "Article title"
          },
          "meta_title": {
            "type": "string",
            "title": "Meta Title",
            "description": "META Title of the article"
          },
          "project_id": {
            "type": "integer",
            "title": "Project Id",
            "description": "Project ID"
          },
          "meta_keywords": {
            "type": "string",
            "title": "Meta Keywords",
            "default": "",
            "description": "META Keywords"
          },
          "limit_max_usages": {
            "type": "integer",
            "title": "Limit Max Usages",
            "default": 1,
            "description": "Maximum usage limit"
          },
          "meta_description": {
            "type": "string",
            "title": "Meta Description",
            "default": "",
            "description": "META Description"
          },
          "is_comments_disabled": {
            "type": "boolean",
            "title": "Is Comments Disabled",
            "default": false,
            "description": "Disable comments"
          }
        }
      }
    },
    "title": "add_articleArguments",
    "required": [
      "args"
    ],
    "properties": {
      "args": {
        "$ref": "#/$defs/AddArticleArgs"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
add_texts 1 change
{
  "name": "add_texts",
  "description": "Add promoted URLs with anchor texts to a Serpzilla project. Each URL can have multiple anchor texts. Use #a#...#/a# markup within each text to specify the link portion. Used for purchasing placements where the webmaster (copywriter) writes the content. Returns urlId and textId needed for purchase.",
  "inputSchema": {
    "type": "object",
    "$defs": {
      "AnchorText": {
        "type": "object",
        "title": "AnchorText",
        "required": [
          "text"
        ],
        "properties": {
          "text": {
            "type": "string",
            "title": "Text",
            "maxLength": 100,
            "minLength": 1,
            "description": "Anchor text. Use #a#...#/a# markup to mark the link portion."
          }
        }
      },
      "AddTextsArgs": {
        "type": "object",
        "title": "AddTextsArgs",
        "required": [
          "project_id",
          "urls_texts"
        ],
        "properties": {
          "project_id": {
            "type": "integer",
            "title": "Project Id",
            "description": "Project ID"
          },
          "urls_texts": {
            "type": "array",
            "items": {
              "$ref": "#/$defs/UrlWithTexts"
            },
            "title": "Urls Texts",
            "description": "List of URLs with their anchor texts"
          }
        }
      },
      "UrlWithTexts": {
        "type": "object",
        "title": "UrlWithTexts",
        "required": [
          "url",
          "texts"
        ],
        "properties": {
          "url": {
            "type": "string",
            "title": "Url",
            "maxLength": 1500,
            "minLength": 1,
            "description": "Promoted URL (e.g., https://example.com/blog/)"
          },
          "texts": {
            "type": "array",
            "items": {
              "$ref": "#/$defs/AnchorText"
            },
            "title": "Texts",
            "description": "Anchor texts for this URL"
          },
          "keywords": {
            "anyOf": [
              {
                "type": "array",
                "items": {
                  "type": "string"
                }
              },
              {
                "type": "null"
              }
            ],
            "title": "Keywords",
            "default": null,
            "description": "Optional key phrases (max 255 chars each)"
          }
        }
      }
    },
    "title": "add_textsArguments",
    "required": [
      "args"
    ],
    "properties": {
      "args": {
        "$ref": "#/$defs/AddTextsArgs"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
blacklist_add_domains 1 change
{
  "name": "blacklist_add_domains",
  "description": "Add domains to the Serpzilla Blacklist by domain IDs and/or domain names. Optionally scope the addition to project blacklists via project_ids. Returns a per-domain result (domainId, isError, errorMessage).",
  "inputSchema": {
    "type": "object",
    "$defs": {
      "BlacklistAddDomainsArgs": {
        "type": "object",
        "title": "BlacklistAddDomainsArgs",
        "properties": {
          "domains_ids": {
            "anyOf": [
              {
                "type": "array",
                "items": {
                  "type": "integer"
                }
              },
              {
                "type": "null"
              }
            ],
            "title": "Domains Ids",
            "default": null,
            "description": "Domain IDs to add"
          },
          "project_ids": {
            "anyOf": [
              {
                "type": "array",
                "items": {
                  "type": "integer"
                },
                "maxItems": 50
              },
              {
                "type": "null"
              }
            ],
            "title": "Project Ids",
            "default": null,
            "description": "Project IDs whose blacklists the domains are added to (max 50). If omitted, the domains are added to the global blacklist only."
          },
          "domains_names": {
            "anyOf": [
              {
                "type": "array",
                "items": {
                  "type": "string"
                }
              },
              {
                "type": "null"
              }
            ],
            "title": "Domains Names",
            "default": null,
            "description": "Domain names to add (without scheme and www)"
          }
        }
      }
    },
    "title": "blacklist_add_domainsArguments",
    "required": [
      "args"
    ],
    "properties": {
      "args": {
        "$ref": "#/$defs/BlacklistAddDomainsArgs"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.serpzilla/mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.serpzilla/mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.serpzilla%2Fmcp.svg)](https://glimind.com/server/mcp-registry%2Fcom.serpzilla%2Fmcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.serpzilla%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.serpzilla%2Fmcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.serpzilla%2Fmcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.serpzilla%2Fmcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:c4c6fcf34bd6ccda…, first seen 2026-10-17, included at leaf 16512 of 23,464. Version history · verify what your client received.

Working alternatives

Tools (28)

Compare: most reliable knowledge servers · most reliable security servers · most reliable data servers · most reliable other servers · most reliable finance servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Serpzilla MCP server down right now?

As of 2026-10-18 09:19 UTC, the Serpzilla MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 21 outages in 90 days, with a median recovery of 5 minutes.

How many tools does Serpzilla MCP server provide?

Serpzilla MCP server advertises 28 tools, including add_article, add_texts, blacklist_add_domains, blacklist_delete_domains, blacklist_get.

How do I install Serpzilla MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.serpzilla.com/mcp

Is the Serpzilla MCP server safe to connect to an AI agent?

Glimind scanned all 28 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Serpzilla MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve