SureCheck MCP

io.github.Killfear1Published by GitHub account Killfear1v0.1.1Updated Oct 26, 2026

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

The publisher's own server: check.tattoo: tattoo size and placement guide

Overview

AI-generated overview

Local stdio server that lets an assistant run phone numbering-plan and email syntax/DNS checks, plus paid Killfear One lead and SEO/AEO agent drafts.

What you can do
  • Check phone numbers for numbering-plan metadata and country codes
  • Check email addresses for syntax and DNS validity
  • Run the Killfear One business agent on a lead CSV to get review-only outreach drafts, sequences and an optional landing page draft
  • Run the AEO/SEO agent on a site's public pages, robots.txt, sitemap.xml and llms.txt to get scores and a fix list
  • Preserve null, unknown and error states in results
When to use it
Useful when an assistant needs quick, cheap validation of phone and email formats during data cleanup or lead preparation, or when you want draft outreach and SEO/AEO audit material generated for human review. It is not a live carrier or mailbox verification service.
Requirements
Local Python 3.8+ runtime with no third-party dependencies; install the wheel from the GitHub release or the older .mcpb bundle, then register the absolute path to the surecheck-mcp executable as the client command. Requires SURECHECK_API_KEY in the environment and network access to the Killfear One host (SURECHECK_BASE_URL, defaulting to a Render URL). A paid plan is needed for new keys; a Dockerfile is included but unverified.
Before you install
New API keys require a paid subscription ($29/mo or $79/mo), and agent calls consume credits (1 per lead, +1 for page builder, 3 per AEO audit). The API key and the phone numbers or emails you submit are sent over HTTPS to Killfear One, and DNS checks send the domain to DNS infrastructure; the host may sleep and time out on first request. Drafts are review-only and nothing is sent, but avoid sensitive personal data and use synthetic data for demos. The .mcpb bundle is unsigned and desktop GUI…

Installation

In SourceWeft

  1. Open SureCheck MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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.

Source: README.md at commit 04e6733

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestOct 13, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Check integrations