Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.oaslananka/infra-lens-mcp

NPM · INFRA-LENS-MCP · SCANNED SEP 20

SSH Linux metrics, baselines, anomaly detection, and plain-English infrastructure explanations.

Available components

0 this week 92 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 56 of 139 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to oaslananka/infra-lens-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 59 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 524 tokens (~52/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 43% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.oaslananka/infra-lens-mcp server?

io.github.oaslananka/infra-lens-mcp runs locally as an npm package, launched with npx -y infra-lens-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · infra-lens-mcp

# add to Claude Code
claude mcp add oaslananka-infra-lens-mcp -- npx -y infra-lens-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "oaslananka-infra-lens-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "infra-lens-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "oaslananka-infra-lens-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "infra-lens-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add oaslananka-infra-lens-mcp -- npx -y infra-lens-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "oaslananka-infra-lens-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "infra-lens-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add oaslananka-infra-lens-mcp --command npx --arg -y --arg infra-lens-mcp
# ~/.hermes/config.yaml
mcp_servers:
  oaslananka-infra-lens-mcp:
    command: "npx"
    args: ["-y", "infra-lens-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "oaslananka-infra-lens-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "infra-lens-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add oaslananka-infra-lens-mcp -t stdio -c npx -a -y infra-lens-mcp
// mcp.json
{
  "mcpServers": {
    "oaslananka-infra-lens-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "infra-lens-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −2
    • Security disclosure: unverified → pass functional
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: pass → unverified functional
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 8 Sept 26 +1
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/infra-lens-mcp@1.5.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo oaslananka/infra-lens-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/oaslananka/infra-lens-mcp/.github/workflows/publish-npm.yml@refs/heads/main
Rekor log index 2219062603
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:6c120dd4ffe5a10a96ab4a12421c2c19f1f00c566e1e75ad8fa1d4d5c58b7e8621da9cd7627a83d3d64ffaf789a85d7b1e037474838b3723e1a529e56

Background: How many MCP packages publish verified provenance →

Dependencies 139 packages
Packages resolved 139
Deprecated 1
Stale 55
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~524 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
analyze_server ~69

Collect metrics from a server and explain any anomalies in human language

NameTypeReqDescription
connectionobjectyes
duration_minutesintegerHow many minutes of metrics to collect for analysis
include_networkbooleanInclude network metrics
include_processesbooleanInclude top process analysis
NameTypeReqDescription
anomaliesarrayyes
collection_modestringyes
collection_window_minutesnumberyes
health_scorenumberyes
hoststringyes
metricsobjectyes
samples_collectedintegeryes
summarystringyes
timestampstringyes
warningsarrayyes

No examples provided.

analyze_server_snapshot ~59

Collect one immediate server snapshot, analyze it, and persist the completed observation without a sampling delay

NameTypeReqDescription
connectionobjectyes
include_networkbooleanInclude network metrics
include_processesbooleanInclude top process analysis
NameTypeReqDescription
anomaliesarrayyes
collection_modestringyes
collection_window_minutesnumberyes
health_scorenumberyes
hoststringyes
metricsobjectyes
samples_collectedintegeryes
summarystringyes
timestampstringyes
warningsarrayyes

No examples provided.

compare_incident_windows ~64

Compare adjacent time windows for one host or the same recent window across two hosts

NameTypeReqDescription
compare_hoststring
end_timestampinteger
hoststringyes
limitinteger
recent_hoursinteger
NameTypeReqDescription
leftobjectyes
left_invalid_rowsintegeryes
left_labelstringyes
metricsarrayyes
review_requiredbooleanyes
rightobjectyes
right_invalid_rowsintegeryes
right_labelstringyes
summarystringyes

No examples provided.

compare_to_baseline ~38

Compare current server state to a recorded baseline and explain the differences

NameTypeReqDescription
baseline_labelstring
connectionobjectyes
NameTypeReqDescription
anomaliesarrayyes
baseline_labelstringyes
baseline_samplesintegeryes
health_scorenumberyes
hoststringyes
summarystringyes
warningsarrayyes

No examples provided.

draft_incident_report ~46

Create a review-first incident report and postmortem draft from persisted observations

NameTypeReqDescription
hoststringyes
hoursinteger
limitinteger
NameTypeReqDescription
completenessstringyes
detection_evidencearrayyes
executive_summarystringyes
generated_atstringyes
hoststringyes
impact_signalsarrayyes
invalid_rowsintegeryes
postmortemobjectyes
remediationobjectyes
review_requiredbooleanyes
sample_countintegeryes
statusstringyes
timelinearrayyes
windowobjectyes

No examples provided.

get_history ~113

Get historical CPU, memory, or load values for a server

NameTypeReqDescription
cursorstringOpaque cursor returned by a previous history page
hoststringyesServer hostname or IP
hoursintegerHow many hours of history to return
labelstringOptional label filter; omitted returns observations, set returns matching records
limitintegerMaximum history points returned in one page; defaults to 100
metricstringMetric to return from historical snapshots
NameTypeReqDescription
data_pointsintegeryes
has_morebooleanyes
historyarrayyes
hoststringyes
hoursintegeryes
labelyes
metricstringyes
next_cursoryes

No examples provided.

inspect_host_capabilities ~28

Check whether a Linux host supports infra-lens collection

NameTypeReqDescription
connectionobjectyes
NameTypeReqDescription
capabilitiesarrayyes
checked_atstringyes
hoststringyes
warningsarrayyes

No examples provided.

plan_remediation ~32

Collect a current read-only snapshot and produce approval-required remediation guidance without executing changes

NameTypeReqDescription
connectionobjectyes
NameTypeReqDescription
confidencenumberyes
execution_performedbooleanyes
generated_atstringyes
health_scorenumberyes
hoststringyes
review_requiredbooleanyes
stepsarrayyes
summarystringyes

No examples provided.

record_baseline ~52

Record current metrics as baseline during normal operation for more accurate anomaly detection later

NameTypeReqDescription
connectionobjectyes
labelstringLabel for this baseline (e.g. "normal", "peak-hours")
NameTypeReqDescription
hoststringyes
labelstringyes
messagestringyes
sample_countintegeryes
savedbooleanyes
warningsarrayyes

No examples provided.

snapshot ~23

Collect and save current server metrics without analysis

NameTypeReqDescription
connectionobjectyes
NameTypeReqDescription
hoststringyes
savedbooleanyes
timestampintegeryes
warningsarrayyes

No examples provided.

Common questions

What is the io.github.oaslananka/infra-lens-mcp server?

io.github.oaslananka/infra-lens-mcp is listed in the public MCP registry as io.github.oaslananka/infra-lens-mcp. SSH Linux metrics, baselines, anomaly detection, and plain-English infrastructure explanations. This page covers its npm package (infra-lens-mcp).

Is the io.github.oaslananka/infra-lens-mcp server safe to use?

io.github.oaslananka/infra-lens-mcp scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.oaslananka/infra-lens-mcp server expose?

io.github.oaslananka/infra-lens-mcp exposes 10 tools: analyze_server, snapshot, record_baseline, compare_to_baseline, get_history, and 5 more. Their descriptions and schemas cost roughly 524 tokens of context every time the server is loaded.

Is the io.github.oaslananka/infra-lens-mcp server still maintained?

io.github.oaslananka/infra-lens-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.oaslananka/infra-lens-mcp server under?

io.github.oaslananka/infra-lens-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.