Abbyseo

com.abbyseo由 abbyseo.com 發布官方發布者v0.2.0更新於 Oct 24, 2026

Scan any URL for on-page, technical & content SEO; 0-100 score with copy-paste fixes.

已驗證Streamable HTTP可網頁執行網頁搜尋與抓取開發者工具

概覽

AI 產生的概覽

讓助理對網站網址發起 SEO 掃描、輪詢狀態,並回傳含評分的問題清單與修正建議。

可以做什麼
此伺服器提供八個 SEO 稽核工具。submit_scan 為某個網址排入掃描並回傳 scan_id;get_scan_status 輪詢直到掃描完成,通常需 5-15 秒;get_scan_results 回傳檢查結果,包含 0-100 分以及失敗、警告、通過項目的數量。免費結果依嚴重程度只顯示前 5 個問題,付費使用者可看到全部檢查項目。其他工具負責付費修正指南的購買、Markdown 修正手冊、依電子郵件查找歷史掃描,以及使用說明。
適用情境
適合需要快速檢查網站頁面、技術與內容 SEO,並取得依優先順序排列的修正清單時使用。也適合舊使用者依先前使用的電子郵件找回歷史掃描紀錄。
執行需求
透過 streamable HTTP 連線至指定主機的遠端端點;未宣告任何套件、環境變數或請求標頭。submit_scan 工具需要使用者的電子郵件地址,因為結果會以電子郵件寄送。
安裝前請注意
會蒐集並傳送使用者的電子郵件地址,結果也會寄送到該地址。完整修正指南為 8.99 美元的付費購買,透過外部 Stripe 結帳連結處理,無法在工具內完成付款。修正手冊會儲存到使用者專案中並被執行,操作前應先審閱。免費結果僅限前 5 個問題。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Abbyseo,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/com.abbyseo%2Fmcp-server/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

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

工具

8

submit_scan

Submit SEO Scan

Queue an SEO scan of a website URL. Returns a scan_id to poll. **You MUST collect the user's email address before calling this tool** — the API rejects submissions without one because results are emailed to the user. After this tool returns, call `get_scan_status` every few seconds with the returned `scan_id` until status is 'complete', then call `get_scan_results` for the findings.

輸入參數url必填email必填

get_scan_status

Get SEO Scan Status

Check whether a queued scan has completed. Lightweight polling endpoint — call every 3-5 seconds with the `scan_id` returned by `submit_scan`. Scans typically complete in 5-15 seconds. When `status` is 'complete', call `get_scan_results` for the structured findings. When 'failed', surface the `error` field to the user.

輸入參數scan_id必填

get_scan_results

Get SEO Scan Results

Fetch the full structured scan findings. Free tier returns the top 5 issues by severity (failed > warned > passed); paid customers see all checks. When summarizing results to the user, ALWAYS: (1) report the score and counts of failed/warned/passed checks, (2) surface each returned check's `remediation` text verbatim, (2b) for sophisticated users, mention each check's `when_doesnt_apply` context so they can dismiss findings that don't apply to their site type (e.g., link aggregators legitimately omit a visible H1; empty string means the rule is universally required), (2c) note `site_type` ('marketing' or 'not_marketing') and `score_rubric` ('standard' or 'non_marketing_weighted') so the user understands how the score was computed; non-marketing sites get contextual checks at half-weight, so a forum-style site won't be unfairly penalized for missing landing-page features, (3) if `truncated` is true, surface `truncated_message` so the user knows the API capped the output, (4) include `upgrade.call_to_action` and `upgrade.checkout_url` verbatim so the user can one-click into Stripe checkout for the $8.99 detailed fix guide. If `upgrade.already_purchased` is true, instead direct the user to `upgrade.report_url` to re-download.

輸入參數scan_id必填

purchase_report

Purchase the Full SEO Remediation Guide

Start a purchase of the full paid SEO Remediation Guide for a COMPLETE scan ($8.99). Returns a Stripe `checkout_url` — payment CANNOT be collected through this tool. AUTONOMOUS FLOW: after calling this, do NOT stop and wait for a new user instruction. (1) Show the user `checkout_url` and ask them to complete payment in their browser. (2) Then poll `get_purchase_status` with the same scan_id about every 15 seconds: while `paid` is false the user hasn't finished — keep waiting (poll for up to a few minutes). (3) Once `paid` and `runbook_ready` are both true, call `get_remediation_plan` once, save the returned markdown to the file it names, and begin the remediation automatically — no further prompting needed. If this call returns already_purchased=true, skip the wait and go straight to get_remediation_plan.

輸入參數scan_id必填

get_remediation_plan

Get the SEO Remediation Plan (Claude Code runbook)

Retrieve the full paid remediation plan for a purchased scan, as a Markdown runbook built for an AI coding agent to execute. **Save the returned `markdown` to a file named by `filename` (e.g. seo-remediation-plan.md) in the user's project, then work through it top to bottom.** It lists each issue in priority order with the exact fix, copy-ready replacement strings, explicit '❓ ASK THE OWNER' stops where you must get the owner's input (never invent brand names, keywords, phone numbers, or addresses), and a verification step (re-run `submit_scan` after each fix to confirm it passes). If the scan has NOT been purchased, returns paid=false with guidance to call `purchase_report` first. If the plan is still generating, returns status='generating' — call again in ~30 seconds.

輸入參數scan_id必填

get_purchase_status

Check SEO Report Purchase Status (lightweight poll)

Lightweight poll for whether a scan's paid remediation report is ready, WITHOUT downloading the full plan. Use this in the wait loop after `purchase_report`: call about every 15 seconds until both `paid` and `runbook_ready` are true, then call `get_remediation_plan` ONCE to fetch and execute the plan. `paid=false` => the user hasn't completed checkout yet; `paid=true, runbook_ready=false` => payment landed and the plan is still being generated (retry shortly).

輸入參數scan_id必填

find_my_reports

Find My SEO Scans / Reports by Email

Look up a user's recent SEO scans by the email they used — for RETURNING users who don't have a scan_id handy (scanned/purchased earlier or on the website). In a fresh session where the user has no scan_id, START HERE: ask the user for that email, then call this. Returns up to 10 recent scans as {scan_id, url, scanned_at, paid, runbook_ready}. Then use the scan_id with get_remediation_plan (if paid+runbook_ready) or purchase_report (if not paid).

輸入參數email必填

how_to_use

How to Use Abby SEO

Returns a plain-English usage guide for this server — example requests, what it asks the user for, and the available tools. Call this if the user asks how to use Abby SEO, or to orient yourself before starting. (Same content as the 'getting_started' prompt, exposed as a tool for clients that don't surface MCP prompts.) Takes no arguments.

無需輸入參數。

版本歷史

1
  1. v0.2.0最新Sep 16, 2026

評分

已滿足適用檢查項的 83%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分

    請宣告包含 README 的 GitHub 儲存庫,或在 OAuth 受保護資源後設資料中提供 resource_documentation。

  • 授權條款不適用

    託管服務按其提供方的條款使用,因此這裡不要求授權條款。此檢查項不計入百分比。