
Ecosystem Aec Regulatory
io.github.carruda-GlobalPublished by GitHub account carruda-Globalv1.0.0Updated Oct 24, 2026
NR-1 psychosocial risk, LGPD, whistleblower, pay equity & anti-corruption tools (Brazil)
Overview
A remote MCP server offering Brazilian regulatory tools covering NR-1 psychosocial risk, LGPD, whistleblower channels, pay equity and anti-corruption.
- What you can do
- Work with Brazilian NR-1 psychosocial risk requirements, including related assessment or documentation tasks as exposed by the server's tools, which are not itemized in the listing. Handle LGPD (Brazilian data protection) topics. Support whistleblower channel and pay equity matters. Address anti-corruption compliance topics. The exact tool set is not published, so capabilities should be confirmed against the live endpoint.
- When to use it
- Useful when an assistant needs to help with Brazilian workplace and compliance topics such as NR-1 psychosocial risk, LGPD, whistleblower reporting, pay equity or anti-corruption obligations, and a hosted service is acceptable.
- Requirements
- A remote MCP client that supports the SSE transport, connecting to the provider's hosted endpoint. No authentication, environment variables or headers are declared, and no local package is needed.
Installation
In SourceWeft
- Open Ecosystem Aec Regulatory in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via SSE. 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/io.github.carruda-Global%2Fecosystem-aec-regulatory/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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"ecosystem-aec-regulatory": {
"type": "sse",
"url": "https://engenheiro-producao-ai.onrender.com/mcp/regulatory/sse"
}
}
}README
This repository has no README.
Tools
0Version history
1- v1.0.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 listedRequired15 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.