Home / MCP registry index / io.github.NovaPixell/lexgrid-mcp

NovaPixel LexGrid

io.github.NovaPixell/lexgrid-mcp in the official MCP registry. Endpoint https://lexgrid.novapixel.it/mcp. Source: github.com/NovaPixell/lexgrid-mcp.

The registry describes it as: Deterministic EU Compliance, Tax, Public Procurement & Labour Law Engine for AI Agents

We read its 32 tools on 2026-11-16. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again about every two weeks.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code
claude mcp add --transport http lexgrid-mcp https://lexgrid.novapixel.it/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "lexgrid-mcp": {
      "url": "https://lexgrid.novapixel.it/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"lexgrid-mcp","type":"http","url":"https://lexgrid.novapixel.it/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard
claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

vies_gleif_kyb_verify einvoice_xml_auditor iban_sepa_antifraud codice_fiscale_audit corporate_default_predictor financial_trend_anomaly csrd_esg_calculator dcf_wacc_valuation email_deliverability_audit tls_http_inspector domain_rdap_intel port_leak_detector gdpr_cmp_tracker_audit eu_ai_act_check b2b_tech_profiler cookie_dark_patterns cig_cup_anac_validator bando_thresholds_calculator subappalto_cascade_limiter anomalia_offerte_calculator dora_third_party_risk nis2_criticality_classifier incident_severity_triage tlpt_threat_led_pentest_scope cbam_embedded_emissions taric_hs_validator incoterms_cost_allocator dual_use_export_control costo_aziendale_dipendente lordo_netto_irpef_simulator ccnl_inquadramento_audit fringe_benefit_tax_optimizer

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-16): b9b0a0ea6c80067e. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-novapixell-lexgrid-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-novapixell-lexgrid-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.