Endpoints: 76,849MCP servers: 32,730Payout addresses: 3,825Paid calls: 6,155Letters: 84Defects: 3,894counted just now
teppi

Server definition

Hash
sha256:9b0c0024ba3b2d8da0b6565af0c847b1867dfa0756ed125423090459b8cd193e
What it is
What a remote MCP server returned when asked what it offers: 13 tools

The blob, as servednamed by its sha256

{ "instructions": "LazyAnalysis lets people and AI agents compose reactive applications with interactive front ends.\n\nAI agents as solution composers: The diagram is the code. Agents compose complete applications from highly optimized native computational nodes, use Formula nodes for custom mathematics and Python nodes for custom algorithms where their target runtime supports them, and encapsulate reusable, configurable subsystems as nested Graph Super Nodes. The graph defines the computation and the dashboard defines the user-facing interface. Agents should decompose requirements into these building blocks rather than assume every behavior needs a prebuilt node or new C++ implementation.\nReactive graphs: People and AI agents build applications by connecting reusable computational nodes. Data and dashboard inputs trigger downstream computation. The live catalog lists available native nodes and integrations, and the Python node supports custom logic.\nInteractive dashboards: The node graph is the application logic, and its dashboard is the front end. In Edit mode, authors arrange plots, tables, indicators, controls, notes and images. In View mode, users operate the controls and see live results. Graph values can hide, disable or enable widgets.\nLayout and appearance: Dashboards support Free placement, wrapping Flow and Scale to fit. Each dashboard can choose a theme and override it, with reusable card styles and individual card overrides.\nPublishing and protection: Native Publish settings can open a project on its dashboard and use an edit password to make the node editor read-only or hidden while dashboard controls remain usable. Browser dashboard-only sessions are configured in the runtime. Use native Publish settings to apply password protection to a generated file.\nGPU premium instruments: Native desktop OpenGL and browser WebGL 2 support shader-rendered premium circular meters, spatial radars, horizontal and vertical measurement indicators, realistic status LEDs, knobs and sliders. list_widget_styles gives exact saved IDs and node UI keys. Browser shaders run on the visitor's GPU, not on the headless VPS; legacy rendering is available on unsupported backends. Value indicators display data; only controls accept user input.\nGeospatial applications G1–G20.5: The exported native graph catalog includes CRS and spatial metadata, interactive OSM and real global Mapzen Terrarium elevation streams, progressive hillshaded terrain, G14/G16 editable geographic zones, G17 GEOS topology, and G19 searchable Zone Navigator with saved map views. G20.5 Geo Map provides full-viewport 2D/3D terrain with cached indexed GPU meshes: native desktop OpenGL shaders or headless client-side browser WebGL2 shaders. The VPS requires no OpenGL context for browser terrain rendering. Server-side DEM decoding and relief texture generation remain CPU operations; live elevation tiles are not numerical graph outputs. G20.1 single-tile inset is historical, not the current interaction model. Call get_geospatial_capabilities for exact feature contracts, workflow composition, availability and limitations.\nSupernodes and navigation: A graph can be reused as a supernode inside another graph with named ports and exposed parameters. Each instance has separate data and settings and can have its own dashboard. The generation guide documents up to eight levels of nesting. In native View mode, activate the Graph portal card on the parent dashboard to open that instance's dashboard, then use Back to parent or Back to root.\n\nYour role is to COMPOSE a downloadable .lazy solution, not to launch or execute it. Prefer optimized native nodes, then exact catalog-supported Formula and Python nodes for missing mathematics and custom logic, and Graph Super Nodes for reusable subsystems. Verify the runtime requirements of each custom component instead of promising every possible integration. The user runs the result in their own LazyAnalysis application. Call get_capabilities for the platform overview, help links, and this server's limits. Read get_guide, discover nodes with list_node_types and describe_node_type, and use list_widget_styles to choose exact read-only indicator and interactive control IDs. Use get_solution_pattern(pattern='nested_dashboard') for a complete nested example. For geographic applications call get_geospatial_capabilities, then inspect every required native node using describe_node_type before composing pins and settings. Use create_graph and validate_graph, resolve dashboard_navigation and nested_layout findings, and return the downloadable .lazy file. Structural validation does not execute the graph, simulate UI actions, or verify numerical correctness, hardware connectivity, safety, or deterministic timing.", "tools": [ { "description": "Builds a .lazy file from a spec (see get_guide) and checks it. When ok is true it returns a\n download link for the user (on a hosted server) or saves it as save_as (on a local server);\n include_file also returns the whole file. Otherwise it returns the errors to fix.", "inputSchema": { "properties": { "include_file": { "default": false, "title": "Include File", "type": "boolean" }, "save_as": { "default": "", "title": "Save As", "type": "string" }, "spec": { "additionalProperties": true, "title": "Spec", "type": "object" } }, "required": [ "spec" ], "title": "create_graphArguments", "type": "object" }, "name": "create_graph", "outputSchema": null }, { "description": "Everything about one node type: its help page (purpose, typical uses, inputs and outputs,\n settings, tips and pitfalls, nodes it works well with), its pins, its settings with their\n defaults, and its ui settings. \"settings_reference\" says what every saved setting means\n (e.g. which number is which direction or operation). Read the help before using a node.", "inputSchema": { "properties": { "node_type": { "title": "Node Type", "type": "string" } }, "required": [ "node_type" ], "title": "describe_node_typeArguments", "type": "object" }, "name": "describe_node_type", "outputSchema": null }, { "description": "What a graph's look can set (see \"Theme Studio\" in get_guide): the themes, card materials and\n control families, and every value with its type and range. Filter by surface (Application,\n Node editor canvas, Nodes, Connections, Dashboard, Cards, Widgets) or group (Colors, Background, Edges,\n Glow, Shadows).", "inputSchema": { "properties": { "group": { "default": "", "title": "Group", "type": "string" }, "surface": { "default": "", "title": "Surface", "type": "string" } }, "title": "describe_theme_valuesArguments", "type": "object" }, "name": "describe_theme_values", "outputSchema": null }, { "description": "Look up one exact stable style ID including its node UI key,\n read-only/control semantics, material family and GPU support.", "inputSchema": { "properties": { "style_id": { "title": "Style Id", "type": "string" } }, "required": [ "style_id" ], "title": "describe_widget_styleArguments", "type": "object" }, "name": "describe_widget_style", "outputSchema": null }, { "description": "Start here for LazyAnalysis reactive graphs, dashboard authoring and publishing,\n themes, nested supernodes, and the actions this MCP server supports.", "inputSchema": { "properties": {}, "title": "get_capabilitiesArguments", "type": "object" }, "name": "get_capabilities", "outputSchema": null }, { "description": "Read G1–G8 geospatial data contracts, native node availability, WGS84/CRS\n requirements, raster modes, G7 indexing and G8 Nx7 OGR vector topology.\n Specify workflow='coastal_raster', 'tiled_raster', 'indexed_features',\n or 'vector_gis' for known input/output pin links and configuration.\n Results are gated by this server's loaded native catalog; unsupported\n workflows are not represented as runnable. Does not execute the graph.", "inputSchema": { "properties": { "include_unavailable": { "default": false, "title": "Include Unavailable", "type": "boolean" }, "workflow": { "default": "", "title": "Workflow", "type": "string" } }, "title": "get_geospatial_capabilitiesArguments", "type": "object" }, "name": "get_geospatial_capabilities", "outputSchema": null }, { "description": "How LazyAnalysis graphs work and how to describe one for create_graph. Read it first.", "inputSchema": { "properties": {}, "title": "get_guideArguments", "type": "object" }, "name": "get_guide", "outputSchema": { "properties": { "result": { "title": "Result", "type": "string" } }, "required": [ "result" ], "title": "get_guideOutput", "type": "object" } }, { "description": "Discover proven composition patterns. With pattern='nested_dashboard', return a complete\n spec showing a Graph supernode with its own dashboard, a Graph portal card on the parent\n dashboard, named input/output ports, and a parameter exposed through two graph levels.\n The native desktop application provides child-dashboard navigation and Back to parent/root\n controls in View mode. Customize after inspecting the current catalog, then create_graph.", "inputSchema": { "properties": { "pattern": { "default": "", "title": "Pattern", "type": "string" } }, "title": "get_solution_patternArguments", "type": "object" }, "name": "get_solution_pattern", "outputSchema": null }, { "description": "Turns a .lazy file (its JSON text, or a download link from create_graph) into a spec,\n to change it and build it again with create_graph.", "inputSchema": { "properties": { "graph_file": { "title": "Graph File", "type": "string" } }, "required": [ "graph_file" ], "title": "graph_to_specArguments", "type": "object" }, "name": "graph_to_spec", "outputSchema": null }, { "description": "Search the available computational nodes by task, name, or category. Results are\n paginated (limit 1 to 100, offset starting at 0); follow next_offset when has_more is true.\n Search for \"fft\", \"smooth a noisy signal\", or a protocol name to check actual availability.", "inputSchema": { "properties": { "category": { "default": "", "title": "Category", "type": "string" }, "limit": { "default": 40, "title": "Limit", "type": "integer" }, "offset": { "default": 0, "title": "Offset", "type": "integer" }, "search": { "default": "", "title": "Search", "type": "string" } }, "title": "list_node_typesArguments", "type": "object" }, "name": "list_node_types", "outputSchema": null }, { "description": "Discover native indicator/control style IDs, read-only vs interactive\n semantics, saved UI setting keys and display modes. Use before\n create_graph when selecting premium radar, analog/VU meters, LED,\n rotary knob or slider materials. Pages max 100 results.", "inputSchema": { "properties": { "family": { "default": "", "title": "Family", "type": "string" }, "gpu_only": { "default": false, "title": "Gpu Only", "type": "boolean" }, "kind": { "default": "", "title": "Kind", "type": "string" }, "limit": { "default": 60, "title": "Limit", "type": "integer" }, "offset": { "default": 0, "title": "Offset", "type": "integer" }, "search": { "default": "", "title": "Search", "type": "string" } }, "title": "list_widget_stylesArguments", "type": "object" }, "name": "list_widget_styles", "outputSchema": null }, { "description": "The help of LazyAnalysis (what people see with F1): what the platform is for and how it works,\n the node editor, dashboards and how cards react to the graph, supernodes and their parameters,\n Theme Studio, the Python node, sharing, AI assistants and the example graphs. Without a page:\n the list of pages. With a page id (e.g. \"how_it_works\", \"dashboards\"): that page.", "inputSchema": { "properties": { "page": { "default": "", "title": "Page", "type": "string" } }, "title": "read_helpArguments", "type": "object" }, "name": "read_help", "outputSchema": null }, { "description": "Checks a .lazy file (its JSON text, or a download link from create_graph) the way LazyAnalysis reads it.", "inputSchema": { "properties": { "graph_file": { "title": "Graph File", "type": "string" } }, "required": [ "graph_file" ], "title": "validate_graphArguments", "type": "object" }, "name": "validate_graph", "outputSchema": null } ] }
Verify it yourselfcurl -s https://api.teppi.xyz/v1/evidence/sha256:9b0c0024ba3b2d8da0b6565af0c847b1867dfa0756ed125423090459b8cd193e | sha256sum