DataJud (CNJ)

The materials explicitly state that no keys or environment variables are required and describe the service as 'Free, no login'; no account credentials, API tokens, or other sensitive authentication data are requested, so credential leakage and abuse exposure appears low.

The system checks show outbound access to the remote endpoint api.mcp.ai; the tool’s stated function also depends on remote lookups via the CNJ/DataJud API, so user queries and returned case data will traverse the network. This kind of connectivity to a declared endpoint is normal for an MCP tool, but the materials do not further detail the data flow or whether any additional endpoints are involved.

The system marks this tool as executes-code, meaning it has the usual MCP ability to start local processes or run code on the client side. The provided materials do not specify any concrete system commands or privileged actions, and they do not show requests for execution rights unrelated to case lookup, so this warrants caution rather than a higher risk rating.

The description only indicates lookup of public Brazilian court case information (metadata and docket) and does not state any need to read local files, write to disk, access databases, or reach other resources. Based on the available materials, there is no clear sign of overbroad data access.

The source is an official registry entry and has a public source repository updated within the last year, which are strong positive trust signals. Although community adoption is limited and the license is undeclared, the project remains auditable overall, with no clear high-risk red flags such as being closed-source, abandoned, or of dubious origin.