@fyzno/mcp
A read-only MCP server for fyzno.com.
It runs three free reports on any domain, each scored out of 100 with one finding per section, and each stating plainly what could not be tested rather than guessing:
Potencialize seu agente
O comando do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
npx -y @fyzno/[email protected]O Claude Code não tem link de instalação para um comando local. Copie o comando abaixo e execute-o em um terminal.
claude mcp add fyzno-mcp -- npx -y @fyzno/mcp@2.0.0Execute em um terminal.
{ "mcpServers": { "fyzno-mcp": { "command": "npx", "args": [ "-y", "@fyzno/[email protected]" ] } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
A read-only MCP server for fyzno.com.
It runs three free reports on any domain, each scored out of 100 with one finding per section, and each stating plainly what could not be tested rather than guessing:
Read-only MCP server for fyzno.com. Three free reports on any domain: mail security (SPF, DKIM, DMARC, MTA-STS, live STARTTLS), website security (headers, CSP, TLS, cookies) and DNS hygiene (name servers, CAA, SOA). Zero dependencies.
Everything is read-only. No payload is ever sent, no form is probed, no path is guessed and no port is scanned.
No install. Point any MCP client at it:
{
"mcpServers": {
"fyzno": {
"command": "npx",
"args": ["-y", "@fyzno/mcp"]
}
}
}
That file is .mcp.json in a project for Claude Code, or
claude_desktop_config.json for Claude Desktop. Cursor, Windsurf, Zed and
VS Code use the same shape.
The transport is stdio, so the client runs it as a local process.
In a browser? ChatGPT and claude.ai cannot spawn a local process, so they
use the hosted endpoint instead: add https://fyzno.com/mcp as a custom
connector. Same seventeen tools, same results.
No MCP at all? Every report is plain JSON over HTTPS, so anything that can fetch a URL can read one. No key, no account, no client:
https://fyzno.com/api/mail?d=example.com
https://fyzno.com/api/web?d=example.com
https://fyzno.com/api/dns?d=example.com
That is what this package calls under the hood, so the answers are identical.
Useful for a shell script, a cron job, or an assistant whose tooling stops at
fetch.
You can also just paste one of those URLs into ChatGPT or Claude and ask them to read it, which usually works and needs no setup at all. The connector is still the better route for anything you care about: browsing is the model's decision rather than a tool it knows it has, and it will summarise the JSON rather than report it, which is a poor trade on a document whose value is that the numbers are exact.
The check_* tools each return one finding from the mail report. There are
no equivalents for the web and DNS reports: thirteen such tools already exist,
and every tool's description is spent from an agent's context on every
conversation.
Every check_* tool runs the same report and returns one finding from it, so
the numbers always agree with mail_health_check. If you want more than one
check on the same domain, call mail_health_check once rather than fanning
out, since that is one request instead of thirteen.
None. The JSON-RPC loop is written out rather than imported, so installing this
package adds exactly one directory and about 20 KB to your node_modules.
MIT
Read-only MCP server for fyzno.com. Three free reports on any domain: mail security (SPF, DKIM, DMARC, MTA-STS, live STARTTLS), website security (headers, CSP, TLS, cookies) and DNS hygiene (name serv
{ "mcpServers": { "fyzno-mcp": { "command": "npx", "args": [ "-y", "@fyzno/[email protected]" ] } }}Visão geral
Read-only MCP server for fyzno.com. Three free reports on any domain: mail security (SPF, DKIM, DMARC, MTA-STS, live STARTTLS), website security (headers, CSP, TLS, cookies) and DNS hygiene (name servers, CAA, SOA). Zero dependencies.
Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
@fyzno/mcp roda localmente via stdio.
Última verificação: 2026-11-16. Read-only MCP server for fyzno.com. Three free reports on any domain: mail security (SPF, DKIM, DMARC, MTA-STS, live STARTTLS), website security (headers, CSP, TLS, cookies) and DNS hygiene (name servers, CAA, SOA). Zero dependencies.