Ecoa

dev.ecoaPublished by ecoa.devOfficial publisherv1.1.0Updated Oct 24, 2026

Verificação de segurança e conformidade de sites: cabeçalhos, TLS, DNS, e-mail, LGPD e pentest.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

A remote MCP server that lets an assistant run website security and compliance checks covering headers, TLS, DNS, email, LGPD and pentest.

What you can do
Check website security configuration, including HTTP headers and TLS setup, and report findings to the assistant. Inspect DNS and email-related records for a domain. Assess compliance against LGPD requirements. Run pentest-style checks as part of a security review.
When to use it
Useful when reviewing a site's security posture or compliance before launch, during an audit, or when an assistant needs to check headers, TLS, DNS or email configuration for a domain.
Requirements
A remote endpoint at mcp.ecoa.dev over streamable HTTP. OAuth 2.1 is required: on first connection the client opens a browser for login and authorization, so no key is needed. For environments without a browser, an x-api-key header is offered as an alternative.
Before you install
The server performs pentest-style checks against sites, so only point it at domains you are authorized to test. Authorization goes through OAuth in the browser; the x-api-key header is a secret alternative for headless environments and should be kept private.

Installation

In SourceWeft

  1. Open Ecoa in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.ecoa%2Fecoa/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "ecoa": {
      "type": "http",
      "url": "https://mcp.ecoa.dev/api/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

60% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.