Netwrix Access Analyzer

Created By
Netwrixa year ago
An MCP server for Netwrix Access Analyzer
Overview

What is Netwrix Access Analyzer?

Netwrix Access Analyzer is an MCP server designed for data analysis, specifically for integrating with Claude Desktop to enhance data analysis capabilities related to access permissions and sensitive data.

How to use Netwrix Access Analyzer?

To use the Netwrix Access Analyzer, set up the required dependencies, configure your SQL Server connection in a .env file, and integrate it with Claude Desktop by modifying its configuration file.

Key features of Netwrix Access Analyzer?

  • SQL Server integration with automatic connection on startup
  • Dynamic database schema exploration
  • SQL query execution
  • Tools for analyzing file system access and sensitive data

Use cases of Netwrix Access Analyzer?

  1. Analyzing user access permissions across file systems.
  2. Identifying sensitive data locations within an organization.
  3. Monitoring and troubleshooting access issues in real-time.

FAQ from Netwrix Access Analyzer?

  • What dependencies are required to run the Netwrix Access Analyzer?

You need Python 3.12 or higher, MCP SDK, pyodbc, and the ODBC Driver for SQL Server.

  • How do I troubleshoot connection issues?

Verify your SQL Server is running, check your credentials, ensure the ODBC driver is installed, and review the logs for errors.

  • Can I use this tool for any SQL Server?

Yes, as long as you have the correct connection details and the ODBC driver installed.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Netwrix
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago