Try it. It’s the real server.

Every button here sends JSON-RPC to /mcp on this site, the way an assistant’s client would, and shows exactly what goes out and what comes back. Nothing is mocked, nothing is stored, and nothing you type leaves for anywhere else.

One request at a time, 20 a minute at most: the server runs on a free plan, and so does everything else here.

Ask it something

Six things a person might ask an assistant that has this server, and the calls it would make. Change the words; the answers are live.

Find art like this

“Show me something with a lighthouse in it.”

Words in, pictures out. Pick one to get the whole record: description, links, and how it fails to exist. Uses search_artwork and get_artwork.

The answer comes here, and the requests that got it underneath.

Requests and responses 0

What is the Slopwright?

“Who or what is the Slopwright?”

The graph finds the thing by name and lists what it touches; the codex says who it is. Uses world_graph and get_codex_entry.

The answer comes here, and the requests that got it underneath.

Requests and responses 0

Today’s slop and level

“What’s today’s slop, and today’s SK8 level?”

The same answer for everyone on a date (UTC). Change the date to see another day. Uses of_the_day.

The answer comes here, and the requests that got it underneath.

Requests and responses 0

Validate a cartridge

“Is this cartridge right? What’s wrong with it?”

The same validator cart.slopped.site runs. Problems come back with their line; a valid one can be played. Uses validate_cartridge.

Start from The cartridge

cart 1
// The Slopwright: This is a cartridge. It is a text file. I have checked.
// Everything a game is goes in here: the words at the top, then sections in [brackets]. Change a number and press
// Play. If something is wrong, the builder says which line and what it wanted instead. It is usually right.
title: First tin
by: the Slopwright
version: 1.0
seed: 1
screen: 128x128
background: y
touch: pad
buttons: left right up down
hud: score time
about: The Slopwright’s first cartridge. Five pearls, thirty seconds, one tin.

// No [palette] section, so this uses the house palette: k ink, w paper, a acid, m muted, l line, p pink,
// o orange, g moss, s tin, b blue, r red, y toast. A dot is see-through.

// A sprite is a picture drawn in those letters. Every row the same width.
[sprite tin]
.ssssss.
ssssssss
slllllls
skssssks
ssssssss
saaaaaas
ssssssss
.ssssss.

[sprite pearl]
..ww..
.wwww.
wwwwlw
wwwwww
.wwww.
..ww..

// A second frame comes after a blank line. self.frame picks which one shows.
[sprite crab]
.r....r.
rr.rr.rr
.rrrrrr.
rrkrrkrr
.rrrrrr.
r.r..r.r

.r....r.
.rrrrrr.
rrkrrkrr
rrrrrrrr
.rrrrrr.
.r.rr.r

// A sound is one of learn’s synthesizer recipes: a wave, a pitch, an envelope, a volume. learn.slopped.site’s
// sound pathway explains each line. I can’t hear them either; they were measured.
[sound pearl]
wave square
pitch loud
arp 0 7 12 step 0.05
attack 0.004
decay 0.1
sustain 0.3
hold 0.04
release 0.08
volume -18
filter lowpass 2400

[sound pinch]
wave square
pitch 440
slide 110
noise 0.2
attack 0.005
decay 0.2
sustain 0.5
hold 0.25
release 0.3
volume -14
filter lowpass 1200

[sound bell]
wave triangle
pitch 523
attack 0.004
decay 0.3
release 0.1
volume -20

// Music is written in Patter: one line a voice, one bar a line. ~ is a rest, [ ] squeezes steps into one,
// < > takes turns each bar. The bell plays the notes; the tin just counts.
[music tide]
bpm 90
bell bell | e5 ~ [g5 e5] ~ <c5 d5> ~ ~ ~

// A shader is the last thing that touches the picture. This one darkens the corners, gently.
[shader]
vec4 effect(vec2 uv) {
  vec4 c = texture(screen, uv);
  vec2 d = uv - 0.5;
  float v = 1.0 - dot(d, d) * 0.9;
  return vec4(c.rgb * v, 1.0);
}

// Words the game says. over and won are said at the end; help on the title screen.
[text]
help: Arrow keys, WASD, the d-pad or a finger held toward a way to move. Five pearls before the tide.
over: The tide came in. The pearls are still there.
won: Five pearls. The tin is full.
crab: That was the crab. It wants the pearls more.

// The rules. var is a number the game remembers. kind is a sort of thing; fields under it are where each one
// starts. Every rule is on <something>, then what happens, indented. The game runs sixty ticks a second.
[game]
var time = 30
var step = 1

kind pearl sprite pearl
kind crab sprite crab
  vx = 0.5
kind tin sprite tin

scene beach
on enter
  spawn tin at 60, 60
  spawn crab at 8, 100
  spawn pearl at 0, 0
    scatter 16
  music tide

on hold left
  tin.x -= step
on hold right
  tin.x += stepp
on hold up
  tin.y -= step
on hold down
  tin.y += step

on each tin
  self.x = clamp(self.x, 0, W - self.w)
  self.y = clamp(self.y, 0, H - self.h)

on each crab
  self.frame = floor(tick / 15) % 2
  if self.x < 0 or self.x > W - self.w
    self.vx = 0 - self.vx

on every 60
  time -= 1
  if time <= 0
    lose

on hit tin pearl
  score += 1
  sound pearl
  burst 10 w
  scatter other 16
  if score >= 5
    win

on hit tin crab
  sound pinch
  shake 8
  say crab
  self.x = 60
  self.y = 20

The answer comes here, and the requests that got it underneath.

Requests and responses 0

Walk the graph

“How is Wren connected to everything else?”

One thing and its neighbours. Every neighbour is another call away. Uses world_graph.

The answer comes here, and the requests that got it underneath.

Requests and responses 0

Look something up in the course

“What does the course teach about sound?”

The whole course in one call; one module in full in the next. Uses list_curriculum and get_module.

The answer comes here, and the requests that got it underneath.

Requests and responses 0

An assistant, replayed

What a conversation with this server looks like from the inside: a question, the calls, the answer.

A scripted illustration, not a model. The assistant’s words are written in advance and its choices follow a script. Every tool result is fetched live from the server as it plays, and the answer at the end is filled in from those results.

You

I like lighthouses. Is there one on slopped.site, and what does it have to do with the rest of the place?

Any tool, by hand

Pick a tool. The form is made from the tool’s own input schema, as the server sends it in tools/list; wrong values go through, so you can watch the schema refuse them.

Nothing run yet.

Requests and responses 0