Is the Retampweb Pa1m Seo MCP server down?

mcp-registry/io.github.retampweb/pa1m-seo · v1.28.1

healthy
Last checked 2026-10-26 18:21 UTC · handshake 603ms

As of 2026-10-26 18:21 UTC, the Retampweb Pa1m Seo MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 25.6 hours.

uptime (30d checks)
99.9%
checks observed
4,897
outages (90d)
3
tools
36

Pay-per-call SEO agent: keyword research, SERP analysis, on-page optimization. x402, USDC on Base.

Point your MCP client at this streamable-http endpoint: https://seo.hypa1m.xyz/mcp

Agent-readiness: C (77/100)

C (77/100): 0 error(s), 3 warning(s) across 36 tool(s); ~7,199 tokens of tool definitions.
Scores higher than 13% of 15,768 MCP servers Glimind has audited.
Its tool list costs an agent ~7,199 tokens per session — more than 65% of servers.
76 → 77 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions71
Safety hints16
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (4)

36 of 36 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: analyze_endpoint, backlinks_check, backlinks_check_bulk, backlinks_status, brief and 31 more

16 parameter(s) across 10 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: analyze_endpoint, backlinks_status, brief, get_status, google_check_report and 5 more

2 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: google_index_submit, google_index_submit_bulk

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 32 corrected tool definitions

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

analyze_endpoint 1 change
{
  "name": "analyze_endpoint",
  "description": "Free-Form AI Analysis — $0.75\n\nAsk any SEO question about a website in plain text. The AI agent reads cached audit data for the URL, selects the relevant audit categories, and returns a structured answer with evidence from the audit results. Examples: 'Why is my Core Web Vitals score low?', 'What is blocking my site from ranking?', 'Compare my mobile vs desktop performance', 'What structured data should I add?'. Requires: url + task (your question). Optional: language, deep=true for deeper analy",
  "inputSchema": {
    "type": "object",
    "title": "analyze_endpointArguments",
    "required": [
      "url",
      "task"
    ],
    "properties": {
      "url": {
        "type": "string",
        "title": "url"
      },
      "deep": {
        "type": "boolean",
        "title": "deep",
        "default": false
      },
      "task": {
        "type": "string",
        "title": "task"
      },
      "language": {
        "type": "string",
        "title": "language",
        "default": "en"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
backlinks_check 1 change
{
  "name": "backlinks_check",
  "description": "Verify a backlink on one donor page — $0.02\n\nConfirm that a single donor page really links to your domain. Fetches each donor page with full JavaScript rendering, so links injected client-side are still found, and reports per donor: the exact target links present, domain authority, spam score, and whether the donor page itself is indexed by Google — a live link on an unindexed page passes nothing. Use it after a link-building campaign to see which placements survived and which were quietly remov",
  "inputSchema": {
    "type": "object",
    "title": "backlinks_checkArguments",
    "required": [
      "donor_urls",
      "target_domains"
    ],
    "properties": {
      "donor_urls": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "title": "donor_urls",
        "maxItems": 1,
        "minItems": 1,
        "description": "Exactly one donor page to inspect"
      },
      "target_domains": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "title": "target_domains",
        "minItems": 1,
        "description": "Domains to look for, e.g. [\"example.com\"]"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
backlinks_check_bulk 1 change
{
  "name": "backlinks_check_bulk",
  "description": "Verify backlinks across up to 500 donor pages — $6.00\n\nAudit up to 500 donor pages in one call ($0.012/donor). Fetches each donor page with full JavaScript rendering, so links injected client-side are still found, and reports per donor: the exact target links present, domain authority, spam score, and whether the donor page itself is indexed by Google — a live link on an unindexed page passes nothing. Use it after a link-building campaign to see which placements survived and which were quietly r",
  "inputSchema": {
    "type": "object",
    "title": "backlinks_check_bulkArguments",
    "required": [
      "donor_urls",
      "target_domains"
    ],
    "properties": {
      "donor_urls": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "title": "donor_urls",
        "maxItems": 500,
        "minItems": 1,
        "description": "Up to 500 donor pages to inspect"
      },
      "target_domains": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "title": "target_domains",
        "minItems": 1,
        "description": "Domains to look for, e.g. [\"example.com\"]"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

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/io.github.retampweb/pa1m-seo"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.retampweb/pa1m-seo"}) 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%2Fio.github.retampweb%2Fpa1m-seo.svg)](https://glimind.com/server/mcp-registry%2Fio.github.retampweb%2Fpa1m-seo?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.retampweb%2Fpa1m-seo?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.retampweb%2Fpa1m-seo.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.retampweb%2Fpa1m-seo.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.retampweb%2Fpa1m-seo?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:ae0bbd41401c9bcd…, first seen 2026-10-17, included at leaf 165 of 74,681. Version history · verify what your client received.

Tools (36)

Compare: most reliable knowledge servers · most reliable web servers · most reliable data servers · most reliable productivity servers · most reliable ml 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 Retampweb Pa1m Seo MCP server down right now?

As of 2026-10-26 18:21 UTC, the Retampweb Pa1m Seo MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 25.6 hours.

How many tools does Retampweb Pa1m Seo MCP server provide?

Retampweb Pa1m Seo MCP server advertises 36 tools, including analyze_endpoint, backlinks_check, backlinks_check_bulk, backlinks_status, brief.

How do I install Retampweb Pa1m Seo MCP server?

Point your MCP client at this streamable-http endpoint: https://seo.hypa1m.xyz/mcp

Is the Retampweb Pa1m Seo MCP server safe to connect to an AI agent?

Glimind scanned all 36 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 Retampweb Pa1m Seo 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