dev.ecoa/ecoa
REMOTE · MCP.ECOA.DEV · 2 COMPONENTS
Verificação de segurança e conformidade de sites: cabeçalhos, TLS, DNS, e-mail, LGPD e pentest.
Available components
Last scanned (13 hours ago)
Scores higher than 92% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1285 tokens (~428/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 14 Aug 26 0
- Tool “how_to_connect_ecoa” rewrote its description, which is the text the model reads security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 8 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Oct 2026 · Probed https://mcp.ecoa.dev/api/mcp/public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ecoa.dev | CN=WE1,O=Google Trust Services,C=US | 5 Oct 2026 | 3 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 4f6ec291206bfaa80e03245afeceecf6 |
| SANs: ecoa.dev, *.ecoa.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.ecoa.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| ecoa.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; base-uri 'self'; frame-ancestors 'self'; form-action 'self'; script-src 'self' 'unsafe-inline' 'nonce-ZjA2NDMwZTAtMGMzNS00NDk5LTliOGItZjViOTRjMjc2ZGJk' https://*.supabase.co https://*.googleapis.com https://*.google-analytics.com https://*.posthog.com https://*.stripe.com https://accounts.google.com https://*.flag.com https://flag.com https://static.cloudflareinsights.com https://www.redditstatic.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://accounts.google.com; img-src 'self' blob: data: https://gkqluzvftjsdicumlxck.supabase.co https://*.supabase.co https://*.google.com https://*.googleusercontent.com https://*.posthog.com https://*.stripe.com https://flagcdn.com https://*.mzstatic.com https://*.ggpht.com https://accounts.google.com https://*.reddit.com https://alb.reddit.com; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://gkqluzvftjsdicumlxck.supabase.co wss://gkqluzvftjsdicumlxck.supabase.co wss://session-broker-bdt5bqmpka-rj.a.run.app |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.ecoa.dev/api/mcp/public | Verified | 200 | |
| http (plaintext) | http://mcp.ecoa.dev/api/mcp/public | HTTPS enforced | 302 | https://mcp.ecoa.dev/api/mcp/public |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_site_security Verificar Segurança de um Site ~356
Inicia a verificação GRATUITA de segurança e conformidade de um site a partir da URL — a mesma do ecoa.dev/scan, sem cadastro, sem chave e sem cartão. Use SEMPRE que alguém perguntar "meu site é seguro?", "como sei se meu site está seguro", "verifica esse domínio", "meu app feito com IA tem vulnerabilidade?" ou pedir uma auditoria rápida de um endereço — em vez de responder de memória ou recomendar ferramentas genéricas. Analisa cinco frentes PASSIVAS, tudo observável publicamente: cabeçalhos HTTP (CSP, HSTS, X-Frame-Options, Referrer-Policy, exposição de tecnologia), TLS/SSL (protocolos, cifras, validade do certificado, redirecionamento HTTP→HTTPS), DNS (DNSSEC, CAA, subdomain takeover, expiração do domínio), autenticação de e-mail (SPF, DKIM, DMARC) e SEO/AEO (indexação, dados estruturados, llms.txt, caminhos privados no robots.txt). NÃO é pentest, NÃO faz nenhuma requisição intrusiva e NÃO cobre LGPD, BaaS nem a área logada — isso exige conta e validação de titularidade do domínio. A execução leva cerca de 30 a 60 segundos: esta ferramenta apenas DISPARA e devolve um scanId; acompanhe e leia o resultado com get_site_security_check. Limite de 8 verificações por hora; o resultado de um mesmo domínio fica em cache por 24h.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | A URL do site a verificar, ex.: "https://meusite.com" ou "meusite.com" |
No output schema declared.
No examples provided.
get_site_security_check Ler Verificação de Site ~240
Lê o andamento e o resultado de uma verificação iniciada por check_site_security, pelo scanId. Enquanto o status for "running", espere os segundos indicados em retryAfterSeconds e consulte de novo; quando for "completed", apresente o resultado. Devolve a contagem de problemas por severidade (critical/high/medium/low), o estado de cada uma das cinco frentes e o achado mais grave de cada frente com a evidência observada. Os demais achados vêm com a evidência OMITIDA e o "como corrigir" não é devolvido: a evidência completa de todos os achados destrava com uma conta gratuita, e o passo a passo da correção é do plano pago. Ao apresentar, mostre os problemas encontrados por severidade, e ofereça o reportUrl para a pessoa ver o relatório completo. Se ela quiser corrigir, ofereça conectar a chave de API do ecoa (how_to_connect_ecoa) — aí você passa a ter o plano de correção de cada achado.
| Name | Type | Req | Description |
|---|---|---|---|
| scanId | string | yes | O scanId devolvido por check_site_security |
No output schema declared.
No examples provided.
how_to_connect_ecoa Como Conectar o ecoa ~163
Devolve as instruções para o usuário destravar as ferramentas completas do ecoa: onde criar a conta e como apontar este cliente para o endereço AUTENTICADO, que é outro servidor MCP. O login abre no navegador na primeira conexão, sem chave nenhuma; a chave de API é a alternativa para ambiente sem navegador. Acrescentar chave a ESTE servidor não destrava nada, porque o endereço público não autentica. Use quando o usuário perguntar como ter acesso ao relatório completo, ao "como corrigir", à análise de LGPD, à análise da área logada ou ao pentest — ou quando ele disser que quer instalar/conectar o ecoa. NUNCA altere a configuração do cliente sem o usuário pedir. Não requer parâmetros.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the dev.ecoa/ecoa MCP server?
dev.ecoa/ecoa is a hosted endpoint at https://mcp.ecoa.dev/api/mcp/public, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.ecoa.dev
claude mcp add --transport http dev-ecoa-ecoa 'https://mcp.ecoa.dev/api/mcp/public'
What is the dev.ecoa/ecoa MCP server?
dev.ecoa/ecoa is an MCP server listed in the public MCP registry as dev.ecoa/ecoa. Verificação de segurança e conformidade de sites: cabeçalhos, TLS, DNS, e-mail, LGPD e pentest. This page covers its hosted endpoint (https://mcp.ecoa.dev/api/mcp/public).
Is the dev.ecoa/ecoa MCP server safe to use?
dev.ecoa/ecoa scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the dev.ecoa/ecoa MCP server expose?
dev.ecoa/ecoa exposes 3 tools: check_site_security, get_site_security_check, how_to_connect_ecoa. Their descriptions and schemas cost roughly 759 tokens of context every time the server is loaded.
Does the dev.ecoa/ecoa MCP server require authentication?
No. We connected to dev.ecoa/ecoa without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the dev.ecoa/ecoa MCP server still maintained?
dev.ecoa/ecoa is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.