io.github.CSOAI-ORG/tone-rewriter-ai-mcp

The materials explicitly state that no keys or environment variables are required, and there is no indication of API keys, OAuth tokens, or other sensitive credentials, so credential exposure and abuse risk appears low.

The materials state that there are no remote endpoint hosts, and the description does not claim any dependency on external services; based on the available facts, there is no evidence that user text is sent to third-party endpoints.

The objective checks include executes-code, which indicates the tool has the normal MCP capability to run code/processes locally. There is no evidence of system privileges beyond its stated purpose, but it should still be treated cautiously as a local execution component.

The description only mentions text-processing functions such as analyzing, rewriting, and comparing tone, with no stated need to read or write files, directories, databases, or other resources; the available materials show no sign of excessive data access.

Positive signals include its presence in the official registry, an auditable open-source repository, and updates within the last year, all of which materially reduce supply-chain risk. However, the missing README, undeclared license, and low community adoption (0 stars) limit transparency and maturity, so source and dependency review is still advisable before deployment.