← Back to directory
N

NAS-Server-1

Community
Not a standard server
Started NAS server instance

This is not a typical connect-and-use MCP server; read the source repository before using it.

Category
Other
Stars
★ 81.0k Very popular
Runtime
Go
Credentials
No credential needed
License
GPL-3.0
Last commit
27FMRS · D

This is a started NAS-Server-1 manifest instance. The available evidence is insufficient to confirm MCP tools, installation, transport protocol, or client support.

Strongest · Maintenance 13/20 Weakest · Setup experience 1/20

Reliability
3/20
Security and permissions
8/20
Maintenance
13/20
Documentation
2/20
Setup experience
1/20
Why each score
Reliability 3/20
The only server-specific evidence is that NAS-Server-1 is marked Started with node ID N1. There is no MCP initialization, tool-list, execution, test, or error-handling evidence, so handshake and behavioral consistency cannot be verified.
Security and permissions 8/20
No server-specific credentials, network flows, permission scope, or dangerous operations are shown, and no red-line risk is evidenced. However, the absence of implementation evidence prevents confirmation of least privilege, data boundaries, or confirmation controls, so the score remains low.
Maintenance 13/20
The repository is not archived, declares GPL-3.0, and provides repository-level security, community, and documentation channels. These signals do not establish server-specific releases, commits, dependency updates, ownership, or response history, so points are deducted.
Documentation 2/20
The README documents the broader Netdata product rather than this MCP server. It provides no server-specific tools, parameters, authentication, limits, cost, or troubleshooting evidence, and sibling-server capabilities cannot be attributed here.
Setup experience 1/20
There are no server-specific installation steps, runtime prerequisites, MCP client configuration, or connection examples. The repository-wide installation guidance does not verify a working connection for this server.

Static review · not runListed 2026-07-29

Read the FMRS scoring method →

Fit and risk

What it can accessUses the network

Best for

  • Users who need to verify this server instance's manifest state

Not for

  • Users who need confirmed MCP tool capabilities
  • Users who need installation, authentication, or transport instructions

Required permissions

  • The source material does not specify required permissions.

Risks and side effects

  • Because no tools or operation permissions are documented, data-access, write, and execution risks cannot be assessed.
  • Repository-wide Netdata capabilities must not be attributed to this specific server.

Setup

Before you start

Runtime:Go

The source material provides no installation steps or client configuration example.

Check that it works

Not verifiable via an MCP client: this entry is not an MCP server but a test-data file (nas_server.) for the Go powerstore collector in the netdata/netdata repository, with no tools or client config recorded.

Troubleshooting

  1. Verify that the server identifier is NAS1 and the name is NAS-Server-1.
  2. Verify that operational_status is Started and current_node_id is N1.
  3. If tools, transport, or client support are required, obtain the complete server definition for this path.

Use cases

Verify the basic manifest status and node assignment of NAS-Server-1

Overview

This MCP server is located at the specified path in the netdata/netdata repository. It is named NAS-Server-1, has operational status Started, and is assigned to node N1. The supplied material does not list tools, transport, installation configuration, or client compatibility.

Similar servers

Telegram MCP server powered by Telethon to let MCP clients read chats, manage groups, and send/modify messages, media, contacts, and settings.

★ 1.8k · Tools 76 Compare with this →

More servers from this repository

Source revision dff79a146923 Data synced 2026-10-19 Read the FMRS scoring method