Verify a software artifact before installing, executing or depending on it. Accepts a package URL such as pkg:npm/express@4.18.2 or pkg:pypi/requests@2.32.3. Returns ALLOW, WARN or BLOCK with a risk score and findings. Call this before suggesting an install command for any third party package.

Verify many artifacts in a single call. Use when checking a dependency list, a lockfile, or several candidate packages at once. Preferred over calling verify_artifact repeatedly.

Verify a Model Context Protocol server before connecting to it or enabling its tools. Checks provenance, requested permissions, the tool surface for unsafe operations, and known risk signals. Call before adding any third party MCP server.

Fetch the signed attestations behind an artifact verdict. Use when the user asks for evidence, provenance detail, or wants to verify offline.

Evaluate an artifact against an organization policy and return the decision. Use when the user asks whether something is allowed by their rules, rather than whether it is generally safe.

Search Phylax for artifacts by name. Use to resolve a vague package name to a concrete package URL before verifying it.

Check that the Phylax API is reachable, the token works, and report the current plan and remaining quota. Use when other tools fail, to tell an outage apart from a plan or credential problem.