Skip to content
anlyon.devby Anlyon

Contraptify

io.github.torsviklabs/contraptifytorsviklabsstreamable-httpv0.1.0Scanned

Design redstone machines with your AI and test them tick by tick with Java Edition 26.3 rules.

5 tools: 1 change things and 4 only read.

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

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →
Compare with similar serversMarkdownJSONReport this listing

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.

5 tools

Changes things 1Claude Code: ask
  • simulateRun a redstone design with its own test (inputs and expectations) and return which expectations hold and which fail (with what the block was instead, and when), what visibly change…1 finding

    Why it is in this group

    • The description's first verb is "run": 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 "simulate" 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 description's first verb is "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Run a redstone design with its own test (inputs and expectations) and return which expectations hold and which fail (with what the block was instead, and when), what visibly changed (lamps, pistons, doors, dispensers) and when, dispenser shots, and notes on what broke. Without a test it just runs the machine and reports what changed. Use it on every candidate before showing it. Do not use it to display a design to the user: use show.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 4Show 4 read-only tools
  • explainList a design's parts with their explanations, how many blocks each covers, and any blocks without a part.No findings

    Why it is in this group

    • The name "explain" says "explain": a word for reading.
    Description, as the server wrote it
    List a design's parts with their explanations, how many blocks each covers, and any blocks without a part. Use it before show to make sure every block is explained. Do not use it to test whether the machine works: use simulate.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_exampleReturn one built-in example design with its blocks, part explanations and its own test, by id from list_examples.No findings

    Why it is in this group

    • The name "get_example" says "get": a word for reading.
    Description, as the server wrote it
    Return one built-in example design with its blocks, part explanations and its own test, by id from list_examples. Large designs (the 0-9 counter has about 2,500 blocks, the 00-59 clock about 5,100) are long. Do not use it to show an example to the user: use show with example set.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_examplesList the built-in example designs (clocks, counters, a piston door, a lock, a flying machine).No findings

    Why it is in this group

    • The name "list_examples" says "list": a word for reading.
    Description, as the server wrote it
    List the built-in example designs (clocks, counters, a piston door, a lock, a flying machine). Use it to find a known-good starting point. Do not use it to fetch a design's blocks: use get_example.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • showShow a design to the user in an interactive 3D viewer in the chat: they can press its button or flip its lever, watch it run tick by tick, move around, and click any part to read w…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "show" says "show": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "show" and "chat": it reads messages.
    • untrusted-inputThe description's first sentence says "show" and "chat": it reads messages, which other people can write.
    Description, as the server wrote it
    Show a design to the user in an interactive 3D viewer in the chat: they can press its button or flip its lever, watch it run tick by tick, move around, and click any part to read what it does. Give either design, or example (an id from list_examples). Simulate the design first. Do not use it to test a design: use simulate.

    Annotations the server declares

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

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 outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
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.

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • Warnsimulate

    The server marks "simulate" 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 description's first verb is "run": a word for a change.

    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.

All changes to this server

Install

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

claude mcp add --transport http contraptify https://mcp.contraptify.com/mcp
claude mcp add --transport http contraptify https://mcp.contraptify.com/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__contraptify__explain",
      "mcp__contraptify__list_examples",
      "mcp__contraptify__get_example",
      "mcp__contraptify__show"
    ],
    "ask": [
      "mcp__contraptify__simulate"
    ],
    "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 contraptify. Review it before you use it.

Capability tags behind 1 rule
  • mcp__contraptify__show private-data, untrusted-input

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://anlyon.dev/api/v1/servers/io.github.torsviklabs/contraptify/verify?hash=fbd605f439789da2bc55fe5b24d0d8a33a9fd4c6c2f0488b784c808d076c1be4" | jq -e '.changed == false'

Pinned hash fbd605f43978, from Nov 1, 2026, 21:18 UTC.

Watch

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

https://anlyon.dev/servers/io.github.torsviklabs/contraptify/changes.xml

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

Badge

anlyon.dev badge for io.github.torsviklabs/contraptify
[![anlyon.dev](https://anlyon.dev/badge/io.github.torsviklabs/contraptify.svg)](https://anlyon.dev/servers/io.github.torsviklabs/contraptify)

Source: MCP Registry · repository. Synced Nov 1, 2026, 21:18 UTC.