SureCheck MCP

io.github.Killfear1由 GitHub 帳號 Killfear1 發布v0.1.1更新於 Oct 26, 2026

Local stdio phone metadata and email syntax/DNS checks. Not live carrier or mailbox verification.

發布方自己的服務:check.tattoo: tattoo size and placement guide

概覽

AI 產生的概覽

本機 stdio 伺服器,讓助理執行電話號碼編碼計畫中繼資料與電子郵件語法/DNS 檢查,並呼叫付費的 Killfear One 潛在客戶與 SEO/AEO 代理產生草稿。

可以做什麼
  • 檢查電話號碼的編碼計畫中繼資料與國碼
  • 檢查電子郵件地址的語法與 DNS 有效性
  • 對潛在客戶 CSV 執行 Killfear One 商務代理,回傳僅供人工審閱的外聯草稿、序列及選用的落地頁草稿
  • 對網站公開頁面、robots.txt、sitemap.xml 與 llms.txt 執行 AEO/SEO 代理,回傳評分與修正清單
  • 在結果中保留空值、未知與錯誤狀態
適用情境
適合在資料清理或潛在客戶準備時需要快速、低成本驗證電話與電子郵件格式,或需要產生外聯草稿與 SEO/AEO 稽核素材供人工審閱的情況。它並非即時的電信業者或信箱存在性驗證服務。
執行需求
需要本機 Python 3.8+ 執行環境,無第三方執行期相依套件;從 GitHub 發行頁安裝 wheel 或較舊的 .mcpb 套件,再把 surecheck-mcp 執行檔的絕對路徑註冊為用戶端指令。需在環境中設定 SURECHECK_API_KEY,並能連線至 Killfear One 主機(SURECHECK_BASE_URL,預設指向一個 Render 位址)。新金鑰需付費方案;附有 Dockerfile 但尚未驗證。
安裝前請注意
新 API 金鑰需付費訂閱(每月 29 美元或 79 美元),代理呼叫會消耗額度(每筆潛在客戶 1 點,選用頁面建置再加 1 點,每次 AEO 稽核 3 點)。API 金鑰與送出的電話號碼或電子郵件會透過 HTTPS 傳送給 Killfear One,DNS 檢查會把網域送給 DNS 基礎設施;主機可能休眠,首次請求可能逾時。草稿僅供審閱、不會送出,但請勿提交敏感個人資料,示範請使用合成資料。.mcpb 套件未簽章,桌面圖形介面安裝尚未測試。

安裝

在 SourceWeft 中

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

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

Killfear One MCP server: tools for AI agents: phone check, email check and a small-business lead agent (0.2.0)

Phone checks return numbering-plan metadata; email checks are syntax/DNS only. Local stdio MCP server; Python 3.8+. No third-party runtime dependencies.

Download the wheel from the GitHub release for 0.2.0, then: python3 -m venv .venv .venv/bin/python -m pip install --no-index ./surecheck_mcp-0.2.0-py3-none-any.whl

Windows uses .venv\Scripts\python.exe and .venv\Scripts\surecheck-mcp.exe. Register the absolute path to .venv/bin/surecheck-mcp (Windows: .venv\Scripts\surecheck-mcp.exe) as the client command, with SURECHECK_API_KEY in its environment. No args required. Default SURECHECK_BASE_URL: https://surecheck-live-040.onrender.com

Alternatively, the older 0.1.1 .mcpb bundle (2 check tools only; no 0.2.0 bundle yet) can be opened in an MCPB-capable client and enter the API key in its secure settings. Python must be installed as python3 on macOS/Linux or python on Windows. Bundle is unsigned. Desktop GUI install has not been tested on macOS/Windows; manifest validation and extracted-bundle subprocess launch have been tested on Linux.

Supported transport: stdio only. No remote MCP endpoint, SSE, Streamable HTTP, OAuth, PyPI or npm publication. Protocol negotiation: 2024-11-05, 2025-03-26, 2025-06-18. Tools: check_phone(phone_number, country_code?), check_email(email), run_business_agent(csv, offer, sender, icp?, agents?, page_name?, page_points?), run_aeo_agent(url, extra_urls?). run_business_agent calls the Killfear One business agent: up to 10 leads per call, 1 credit per lead (+1 if page_builder is selected). It returns review-only drafts and sequences and an optional HTML landing page draft. Nothing is sent and nothing is stored by the wrapper. run_aeo_agent runs the Killfear One AEO/SEO agent: rule-based SEO and AEO checks on up to 3 public pages of one site plus robots.txt, sitemap.xml and llms.txt; returns two scores, a fix list and review-only drafts. 3 credits per audit. It does not measure rankings or AI citations and changes nothing on the audited site. Version 0.3.0 adds run_aeo_agent; 0.2.0 added run_business_agent. The wheel is built; the .mcpb bundle was not rebuilt and stays at 0.1.1 (2 tools). Results preserve null/unknown/error states. Phone checks are numbering-plan metadata only, not live carrier, HLR, reachability or ownership. Email checks are syntax/DNS only, not mailbox, catch-all or delivery verification. New API keys require a paid plan: $29/mo for 10,000 checks, $79/mo for 50,000. Keys from the earlier free beta keep their remaining checks. Host can sleep; a first request can time out. Retry after it wakes. The local wrapper stores no inputs or keys. It transmits the key and requested phone/email to Killfear One over HTTPS. DNS checks send the domain to DNS infrastructure. The host/client can keep logs according to their own settings; do not submit sensitive personal data without permission. Inputs are not saved to the API application database or access logs; account/key hashes and usage accounting are stored. Use synthetic data for demos. 0.2.0 adds the run_business_agent tool. Drafts, sequences and pages it returns are for human review; the server sends no email, SMS or posts.

Container (stdio)

A Dockerfile is included for clients that can run local stdio containers:

sh
docker build -t surecheck-mcp .docker run --rm -i -e SURECHECK_API_KEY surecheck-mcp

Set SURECHECK_API_KEY in the calling environment before running. Do not put the key in the Dockerfile or image. The container runs as an unprivileged user. Container build and execution are not yet verified. Including a Dockerfile does not establish compatibility with Glama's deployment service. No remote endpoint or HTTP transport is provided by this container.

Tests

sh
python3 -m unittest discover -s tests -v

The offline suite checks malformed input recovery, argument checks, protocol negotiation, HTTPS-only configuration, blocked redirects and error handling. API responses are mocked. The suite does not verify live paid provisioning.

來源:README.md,提交 04e6733

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.1.1最新Oct 13, 2026

評分

已滿足適用檢查項的 50%

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

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Check 整合