SignalDig

// Connection support

Check your SignalDig connection

Check whether this computer can reach SignalDig MCP. If it cannot, follow the guidance on this page.

Click to check this computer's connection now.

Observed from this browser

Connection result

Not checked yet.

Repair guidance

What to do about connection problems

Ask an AI if you are not comfortable in a terminal, or follow the steps below to run the script yourself.

The browser check passes, but your MCP client still shows a connection error?
Use the steps below for streamable HTTP, SSE, 127.0.0.1:443, or ::1:443 errors too. Run Diagnostic first; it checks this computer's network settings without changing anything. Run Repair only after it identifies a problem.

Not comfortable running scripts?

Copy once and ask an AI for help

Copy this request and paste it into the AI you use. It includes this page's results, system context, and safe handling requirements. Ask the AI to explain the diagnosis before deciding whether to repair anything.

Comfortable running scripts?

Run the script yourself

Windows

PowerShell repair script

A PowerShell .ps1 script, not a .bat file.

  1. 1.Download the script

    Save the .ps1 file to Downloads.

    Download PowerShell script

  2. 2.Open Administrator PowerShell

    Right-click PowerShell and select Run as administrator.

  3. 3.Copy and run a command

    Diagnose first; repair only after confirming the problem. Use restore to undo the repair.

    Diagnose: checks only

    PowerShell -ExecutionPolicy Bypass -File "$env:USERPROFILE\Downloads\server-check-dns.ps1" -Diagnose -Language en

    Repair: update connection settings

    PowerShell -ExecutionPolicy Bypass -File "$env:USERPROFILE\Downloads\server-check-dns.ps1" -Language en

    Restore: return to previous settings

    PowerShell -ExecutionPolicy Bypass -File "$env:USERPROFILE\Downloads\server-check-dns.ps1" -Restore -Language en

macOS and Linux

Bash repair script

A Bash .sh script for macOS and Linux.

  1. 1.Download the script

    Save the .sh file to Downloads.

    Download Bash script

  2. 2.Open Terminal

    Open Terminal on macOS or your Linux terminal app.

  3. 3.Copy and run a command

    Diagnose first; repair only after confirming the problem. Use restore to undo the repair.

    Diagnose: checks only

    bash ~/Downloads/server-check-dns.sh --diagnose --language en

    Repair: update connection settings

    sudo bash ~/Downloads/server-check-dns.sh --fix --language en

    Restore: return to previous settings

    sudo bash ~/Downloads/server-check-dns.sh --restore --language en

Common MCP connection questions

Seeing the same connection error across several MCP clients? Start with the address in the error, then check DNS before changing anything on this computer.

All three MCP servers fail. Is SignalDig down?

Not by itself. If signaldig-seo, signaldig-social and signaldig-seo-decisions all fail on the normal route, but all three work after you bypass the bad DNS path and return HTTP 200, SignalDig is probably available. That pattern usually points to DNS or network settings on the affected computer.

Why does the error mention 127.0.0.1:443 or ::1:443?

Both addresses mean 'this computer'. If mcp.signaldig.com resolves to 127.0.0.1 or ::1 instead of SignalDig's public endpoint, the MCP client is being sent back to the local machine. An empty hosts file does not rule this out: a router, VPN or proxy can rewrite DNS replies and return a fake IP.

How do I confirm that DNS is the problem?

Compare the answer from your current network's DNS with a trusted public resolver such as 1.1.1.1 or 8.8.8.8. If the public resolver returns a public address while the gateway or proxy returns 127.0.0.1 or ::1, the current DNS path is probably rewriting the result. Public IPs can change, so compare the kind of address and whether the connection works—not one fixed IP.

My hosts file is empty. What else could cause the error?

The DNS reply may be coming from your router, VPN or proxy. Tools such as Clash, Surge and V2RayN can use fake-IP or DNS interception, and a school or company network may filter the domain or block the outbound connection. If the same setup works on a network you are allowed to use, the original network path is the likely difference.

What is the safest way to fix it?

Start with Diagnose. If you manage the connection, temporarily try a network you are allowed to use or a trusted DNS resolver, and disable or adjust fake-IP/DNS interception in your proxy. Run the check again before using Repair. For a managed school or company network, contact the administrator or use the organisation's approved VPN rather than bypassing its rules.