nut-server

nut-server is a server component for Network UPS Tools (NUT). It typically provides network services (e.g., for UPS monitoring/control) so other clients can query UPS status and issue commands over the network.

Evaluated Apr 04, 2026 (25d ago)
Homepage ↗ Repo ↗ Infrastructure infrastructure monitoring security self-hosted ups nut
⚙ Agent Friendliness
25
/ 100
Can an agent use this?
🔒 Security
44
/ 100
Is it safe for agents?
⚡ Reliability
31
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
0
Documentation
35
Error Messages
0
Auth Simplicity
45
Rate Limits
0

🔒 Security

TLS Enforcement
35
Auth Strength
55
Scope Granularity
35
Dep. Hygiene
50
Secret Handling
45

As a self-hosted UPS management server, security depends on correct NUT configuration, network exposure (firewalls), and credential handling. TLS/transport security and fine-grained authorization are not clearly documented in the provided context; improper network exposure can be a major risk.

⚡ Reliability

Uptime/SLA
0
Version Stability
45
Breaking Changes
40
Error Recovery
40
AF Security Reliability

Best When

You need self-hosted, network-accessible UPS monitoring/control using NUT and can manage the server’s security and operations.

Avoid When

You cannot secure the network endpoints, secrets, and service configuration of a self-hosted UPS management server.

Use Cases

  • Centralized UPS monitoring for multiple clients
  • UPS status aggregation for home lab or small datacenter
  • Remote execution of basic UPS actions (depending on NUT configuration)

Not For

  • Environments requiring a managed cloud SaaS with hosted uptime guarantees
  • Use as a general-purpose device-management platform beyond NUT/UPS needs
  • Cases where strict audit/compliance requirements cannot be met by self-managed infrastructure

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
No
SDK
No
Webhooks
No

Authentication

Methods: NUT network access control (typically user/ACL based on NUT configuration; exact mechanisms depend on deployment)
OAuth: No Scopes: No

No OAuth or documented API-key scheme is evident from the provided package context. NUT deployments commonly rely on NUT-specific users/credentials and network ACLs configured in NUT config files.

Pricing

Free tier: No
Requires CC: No

Self-hosted open-source component; costs are infrastructure/ops rather than subscription-based.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • NUT server interfaces are typically service/config-file driven rather than a modern API contract; AI agents may struggle without explicit API specs or tool endpoints.
  • Correct operation often depends heavily on network/ACL/firewall settings and accurate NUT configuration (ups/driver mappings, users, permissions).

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for nut-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered