slopnet-mcp

The server uses `subprocess.run` for Git operations (clone, add, commit, push), which are necessary for its functionality and appear to be well-controlled with predefined commands and arguments. It makes network requests to 'https://slop.at' (default) for knowledge graph queries, updates, and publishing slop content and extracted entities. This means user data (slops, extracted entities, RDF triples) is sent to an external service, which is inherent to its distributed design. SPARQL queries and updates are passed directly to the remote server. While `query_slops` is for data retrieval, `update_graph` explicitly warns 'Advanced users only - use with caution!', as arbitrary SPARQL UPDATE queries could be destructive if the backend server is not properly secured against such operations or if a malicious prompt were to generate one. No `eval` or obvious hardcoded secrets were found.