Home / MCP registry index / io.github.vlad-public-code/valem
io.github.vlad-public-code/valem
io.github.vlad-public-code/valem in the official MCP registry.
Endpoint https://valem.run/mcp. Source: github.com/vlad-public-code/org.json-kula.valem.
The registry describes it as: Valem - Deterministic reactive state models. Create your own calculators/forms with AI
We read its 29 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
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 every week.
Tools it advertises
list_models create_model get_model_info get_spec get_library get_state get_field mutate patch_model get_effective_schema snapshot restore explain get_history get_audit verify_audit upload_blob download_blob evolve_spec delete_model get_view get_domain_guidance validate_spec eval_expression test_spec dry_run convert_spreadsheet search_document pair_browser
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-vlad-public-code-valem)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. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.