Ip2Locationio
v1.0.2IP2Location.io integration. Manage data, records, and automate workflows. Use when the user wants to interact with IP2Location.io data.
⭐ 0· 92·0 current·0 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (IP2Location.io integration) match the SKILL.md: it describes using the Membrane CLI to run connector actions and proxy API requests to IP2Location.io. No unrelated credentials, binaries, or capabilities are requested.
Instruction Scope
Instructions are narrowly scoped to installing and using the Membrane CLI, creating a connector, listing actions, running actions, and proxying requests. They do not instruct the agent to read local files, harvest unrelated environment variables, or exfiltrate data to unexpected endpoints. The guidance explicitly says not to ask users for API keys.
Install Mechanism
The skill is instruction-only (no install spec). It instructs users to run `npm install -g @membranehq/cli` to obtain the Membrane CLI — this is a normal, registry-based install but does require installing a global npm package from the public registry, so verify the package's source and trustworthiness before proceeding.
Credentials
The skill declares no required environment variables, credentials, or config paths. However, it depends on a Membrane account and uses Membrane to hold credentials and proxy requests (server-side). That means request/response data (including IP addresses and any request payloads) will transit through Membrane's service — a legitimate design choice but a privacy/trust consideration.
Persistence & Privilege
The skill does not request always:true or other elevated persistence. It's user-invocable and can be used by the agent when allowed; there are no instructions to modify other skills or system-wide settings.
Assessment
This is an instruction-only integration that uses the Membrane CLI to access IP2Location.io. Before using it: (1) confirm you trust Membrane (data and credentials are proxied through their service); (2) inspect the @membranehq/cli package on npm/GitHub before running a global install; (3) prefer running CLI installs in a controlled environment (e.g., container or dedicated machine) if you have strong security requirements; and (4) review what data you send through the proxy (IP addresses or other PII) to ensure it meets your privacy/compliance needs.Like a lobster shell, security has layers — review code before you run it.
latestvk97fe7gk345fwb25e3es07bkvn842zea
License
MIT-0
Free to use, modify, and redistribute. No attribution required.