An MCP server that gives compatible AI agents secure access to Nas.com business data and management tools.
Nas.com is a remote MCP server published at mcp.nas.com. It has been probed 6 times since 9/10/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 2,249 ms, a delay an agent will notice. It exposes a broad tool surface of 423 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
list_my_business — Redundant with list_my_communities (same purpose)get_business — Ambiguous parameter definitions for community identificationlist_products — Incomplete description with cut-off text and missing inputSchemaupdate_lead_form_style_preset — Unclear parameter definitions for style presetscheck_business_tool_access — No inputSchema defined for permission checksRisk: medium
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/nascompany-nas-mcp)<a href="https://mcpmetrics.io/servers/nascompany-nas-mcp"><img src="https://mcpmetrics.io/badge/nascompany/nas-mcp/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-11 13:13:33 | Legacy | 401 | 2521 | 200 | 2549 | 2025-11-25 |
| 2026-09-11 11:20:19 | Legacy | 401 | 2643 | 200 | 2688 | 2025-11-25 |
| 2026-09-11 09:28:19 | Legacy | 401 | 2198 | 200 | 2192 | 2025-11-25 |
| 2026-09-11 07:35:54 | Legacy | 401 | 2169 | 200 | 2200 | 2025-11-25 |
| 2026-09-11 05:44:28 | Legacy | 401 | 2249 | 200 | 2312 | 2025-11-25 |
| 2026-09-10 21:16:35 | Auth-gated | 401 | 367 | 401 | 363 | — |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.