Skip to content

LazyAnalysis — AI Solution Composer MCP server

it.lazyanalysis/lazyanalysislazyanalysis.itstreamable-httpv1.0.0Scanned

Compose downloadable graphs and dashboards with native, Formula, Python and reusable Super Nodes.

13 tools: 3 change things and 10 only read.

Tools: 0 delete, 0 irreversible, 3 write, 10 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the LazyAnalysis — AI Solution Composer MCP server can do

The LazyAnalysis — AI Solution Composer MCP server is published by lazyanalysis.it, a domain the MCP Registry verified. It has 13 tools. It can create or change data (3 tools: get_capabilities, create_graph and graph_to_spec), but cannot delete data. 10 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

13 tools

Changes things 3Claude Code: ask
  • create_graphBuilds a .lazy file from a spec (see get_guide) and checks it.No findings

    Why it is in this group

    • The name "create_graph" says "create": a word for a change.
    Description, as the server wrote it
    Builds a .lazy file from a spec (see get_guide) and checks it. When ok is true it returns a download link for the user (on a hosted server) or saves it as save_as (on a local server); include_file also returns the whole file. Otherwise it returns the errors to fix.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
  • get_capabilitiesStart here for LazyAnalysis reactive graphs, dashboard authoring and publishing, themes, nested supernodes, and the actions this MCP server supports.1 finding

    Why it is in this group

    • The name "get_capabilities" says "get": a word for reading.
    • The description's first verb is "start": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "get_capabilities" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_capabilities" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Start here for LazyAnalysis reactive graphs, dashboard authoring and publishing, themes, nested supernodes, and the actions this MCP server supports.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • graph_to_specTurns a .lazy file (its JSON text, or a download link from create_graph) into a spec, to change it and build it again with create_graph.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Turns a .lazy file (its JSON text, or a download link from create_graph) into a spec, to change it and build it again with create_graph.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
Only reads 10Show 10 read-only tools
  • describe_node_typeEverything about one node type: its help page (purpose, typical uses, inputs and outputs, settings, tips and pitfalls, nodes it works well with), its pins, its settings with their …No findings

    Why it is in this group

    • The name "describe_node_type" says "describe": a word for reading.
    Description, as the server wrote it
    Everything about one node type: its help page (purpose, typical uses, inputs and outputs, settings, tips and pitfalls, nodes it works well with), its pins, its settings with their defaults, and its ui settings. "settings_reference" says what every saved setting means (e.g. which number is which direction or operation). Read the help before using a node.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • describe_theme_valuesWhat a graph's look can set (see "Theme Studio" in get_guide): the themes, card materials and control families, and every value with its type and range.No findings

    Why it is in this group

    • The name "describe_theme_values" says "describe": a word for reading.
    Description, as the server wrote it
    What a graph's look can set (see "Theme Studio" in get_guide): the themes, card materials and control families, and every value with its type and range. Filter by surface (Application, Node editor canvas, Nodes, Connections, Dashboard, Cards, Widgets) or group (Colors, Background, Edges, Glow, Shadows).

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • describe_widget_styleLook up one exact stable style ID including its node UI key, read-only/control semantics, material family and GPU support.No findings

    Why it is in this group

    • The name "describe_widget_style" says "describe": a word for reading.
    Description, as the server wrote it
    Look up one exact stable style ID including its node UI key, read-only/control semantics, material family and GPU support.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • get_geospatial_capabilitiesRead G1–G8 geospatial data contracts, native node availability, WGS84/CRS requirements, raster modes, G7 indexing and G8 Nx7 OGR vector topology.No findings

    Why it is in this group

    • The name "get_geospatial_capabilities" says "get": a word for reading.
    Description, as the server wrote it
    Read G1–G8 geospatial data contracts, native node availability, WGS84/CRS requirements, raster modes, G7 indexing and G8 Nx7 OGR vector topology. Specify workflow='coastal_raster', 'tiled_raster', 'indexed_features', or 'vector_gis' for known input/output pin links and configuration. Results are gated by this server's loaded native catalog; unsupported workflows are not represented as runnable. Does not execute the graph.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • get_guideHow LazyAnalysis graphs work and how to describe one for create_graph.No findings

    Why it is in this group

    • The name "get_guide" says "get": a word for reading.
    Description, as the server wrote it
    How LazyAnalysis graphs work and how to describe one for create_graph. Read it first.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • get_solution_patternDiscover proven composition patterns.No findings

    Why it is in this group

    • The name "get_solution_pattern" says "get": a word for reading.
    Description, as the server wrote it
    Discover proven composition patterns. With pattern='nested_dashboard', return a complete spec showing a Graph supernode with its own dashboard, a Graph portal card on the parent dashboard, named input/output ports, and a parameter exposed through two graph levels. The native desktop application provides child-dashboard navigation and Back to parent/root controls in View mode. Customize after inspecting the current catalog, then create_graph.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • list_node_typesSearch the available computational nodes by task, name, or category.No findings

    Why it is in this group

    • The name "list_node_types" says "list": a word for reading.
    Description, as the server wrote it
    Search the available computational nodes by task, name, or category. Results are paginated (limit 1 to 100, offset starting at 0); follow next_offset when has_more is true. Search for "fft", "smooth a noisy signal", or a protocol name to check actual availability.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • list_widget_stylesDiscover native indicator/control style IDs, read-only vs interactive semantics, saved UI setting keys and display modes.No findings

    Why it is in this group

    • The name "list_widget_styles" says "list": a word for reading.
    Description, as the server wrote it
    Discover native indicator/control style IDs, read-only vs interactive semantics, saved UI setting keys and display modes. Use before create_graph when selecting premium radar, analog/VU meters, LED, rotary knob or slider materials. Pages max 100 results.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • read_helpThe help of LazyAnalysis (what people see with F1): what the platform is for and how it works, the node editor, dashboards and how cards react to the graph, supernodes and their pa…No findings

    Why it is in this group

    • The name "read_help" says "read": a word for reading.
    Description, as the server wrote it
    The help of LazyAnalysis (what people see with F1): what the platform is for and how it works, the node editor, dashboards and how cards react to the graph, supernodes and their parameters, Theme Studio, the Python node, sharing, AI assistants and the example graphs. Without a page: the list of pages. With a page id (e.g. "how_it_works", "dashboards"): that page.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • validate_graphChecks a .lazy file (its JSON text, or a download link from create_graph) the way LazyAnalysis reads it.No findings

    Why it is in this group

    • The name "validate_graph" says "validate": a word for reading.
    Description, as the server wrote it
    Checks a .lazy file (its JSON text, or a download link from create_graph) the way LazyAnalysis reads it.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:20 UTC, unchanged since Nov 18, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.lazyanalysis.it/mcp: tools/list returned 13 tools to an anonymous client, including get_capabilities (write), create_graph (write), graph_to_spec (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "get_capabilities" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_capabilities" says "get": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http lazyanalysis https://mcp.lazyanalysis.it/mcp
claude mcp add --transport http lazyanalysis https://mcp.lazyanalysis.it/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__lazyanalysis__get_solution_pattern",
      "mcp__lazyanalysis__get_geospatial_capabilities",
      "mcp__lazyanalysis__get_guide",
      "mcp__lazyanalysis__read_help",
      "mcp__lazyanalysis__list_node_types",
      "mcp__lazyanalysis__describe_node_type",
      "mcp__lazyanalysis__describe_theme_values",
      "mcp__lazyanalysis__list_widget_styles",
      "mcp__lazyanalysis__describe_widget_style",
      "mcp__lazyanalysis__validate_graph"
    ],
    "ask": [
      "mcp__lazyanalysis__get_capabilities",
      "mcp__lazyanalysis__create_graph",
      "mcp__lazyanalysis__graph_to_spec"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as lazyanalysis. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/it.lazyanalysis/lazyanalysis/verify?hash=4fd37c5827fb128d4090b60e430ef6c816db53713ef646193eebc12647dacd16" | jq -e '.changed == false'

Pinned hash 4fd37c5827fb, from Nov 18, 2026, 00:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/it.lazyanalysis/lazyanalysis/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for it.lazyanalysis/lazyanalysis
[![Anlyon Radar](https://radar.anlyon.com/badge/it.lazyanalysis/lazyanalysis.svg)](https://radar.anlyon.com/servers/it.lazyanalysis/lazyanalysis)

Source: MCP Registry. Synced Nov 18, 2026, 00:18 UTC.

LazyAnalysis — AI Solution Composer MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the LazyAnalysis — AI Solution Composer MCP server safe?

No scan can promise that. What its definitions show: 13 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the LazyAnalysis — AI Solution Composer MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the LazyAnalysis — AI Solution Composer MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the LazyAnalysis — AI Solution Composer MCP server have?

13 tools: 3 write, 10 read. get_capabilities, create_graph, graph_to_spec, get_solution_pattern, get_geospatial_capabilities, get_guide, read_help, list_node_types and 5 more.

Does the LazyAnalysis — AI Solution Composer MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the LazyAnalysis — AI Solution Composer MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the LazyAnalysis — AI Solution Composer MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.