GDELT Global Events

The materials state that no keys or environment variables are required. No API token, account credential, or other sensitive secret is requested, so credential exposure and abuse risk appears low.

The tool connects to the declared endpoint gdelt-events-mcp.atlasword.workers.dev, which means user queries or parameters may be sent to that remote service. Only a single known endpoint is disclosed and there is no evidence of exfiltration to unrelated domains, but remote data transfer still warrants caution.

System checks indicate that the tool executes code or starts a process, which is a standard MCP runtime behavior. The provided materials do not show requests for unusual system-level privileges or suspicious execution beyond its stated data-query purpose.

The materials do not state any need to read or write specific local files, directories, or databases; the known functionality is mainly remote event-data querying. Since it runs as an MCP process, its visible working directory and input data scope should still be limited by default, but no clear signs of excessive access are shown.

Positive signals include listing in an official registry, a public open-source repository, and updates within the last year; these reduce supply-chain risk. Points to watch are the missing license declaration, very low community adoption (0 stars), and sparse README information, which leave maturity and dependency transparency only moderate.