jurisprudenciaia-mcp

The material explicitly states that no keys or environment variables are required, and no API key, token, or other sensitive credential is declared; based on the available facts, credential exposure or misuse risk appears low.

Although the declared remote endpoint host is 'none', the description says it queries Brazilian legal jurisprudence 'via JurisprudenciaIA', which functionally suggests outbound lookups may occur; the specific domains, transmitted content, and whether user prompts are sent are not disclosed, so network egress transparency is insufficient and warrants caution.

The objective checks mark this tool as executes-code, meaning it runs code/processes in the local environment; this is a normal MCP capability and not a high-risk signal by itself, but it should still be run in a constrained environment with its actual execution capabilities reviewed.

The README is absent and does not specify what local files, caches, logs, or other resources it may read or write; there is no explicit over-privilege red flag from the material, but the data access scope is under-documented and should be verified in source.

A positive factor is that the project is open source and can be audited; however, it comes from a third-party registry, has no declared license, shows 0 stars, and has unknown maintenance status, so the evidence of maturity and trust is limited and the supply-chain posture warrants caution.