Arc Security Mcp

v0.2.1

AI-first security intelligence with LLM-powered intent analysis. 743+ findings from 361+ skill audits, 25 pattern rules, 22 attack classes.

0· 944·3 current·4 all-time
byArcSelf@trypto1019
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The name/description match the listed capabilities (skill safety checks, static analysis, intent analysis). Functionality is plausible for a remote MCP service. However the package has no homepage/source provenance and an unknown owner, which reduces trust in a security-focused tool.
!
Instruction Scope
SKILL.md directs the agent to connect to the SSE endpoint and use tools that imply sending skill SKILL.md/source for analysis. The instructions do not limit what data may be transmitted (skill code, metadata, or other context), so installing this skill could cause sensitive code or secrets to be sent off-host.
Install Mechanism
Instruction-only skill with no install spec or code files — nothing is written to disk by the package itself, which lowers installation risk.
!
Credentials
The skill requests no environment variables or credentials, which is expected, but its runtime behavior (remote analysis) can still exfiltrate sensitive data. Because there is no explicit data-usage/privacy policy in the SKILL.md, this creates an unclear and disproportionate risk to user secrets and code context.
Persistence & Privilege
always is false and there is no install hook. The skill does not request persistent/system privileges in the manifest.
What to consider before installing
This skill delegates analysis to a remote service (https://arcself.com) but provides no provenance or data-handling guarantees. Before installing: (1) confirm the vendor and review an official homepage or privacy/security policy; (2) do not send production or secret-containing skill source — test with non-sensitive samples first; (3) prefer solutions that can run locally if you need to analyze private code; (4) ask how submitted data is stored, who can access it, and how long it is retained; (5) monitor and limit network access for the agent if possible. If you cannot verify the service or are handling sensitive code/credentials, treat this skill as unsafe to use.

Like a lobster shell, security has layers — review code before you run it.

latestvk972sj8rsy6j66h977dq6k5t2h81bfdt

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments