MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

Polyfork low-poly 3D assets

Claim this listing

dev.polyfork/polyfork

polyfork.devVerified

Low-poly 3D models and kits for three.js and game engines: search, match, remix, preview.

OtherIs Polyfork low-poly 3D assets down?Alternatives

13 of 22 checks passed

  • Handshake
  • Tools listed
  • Updated recently

Responded

The server completed its last measured handshake. This is an observation, not a guarantee.

Connect to server
Median latency
253 ms
Uptime, 30 days
Not measured
Last checked

Measurement details

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 253 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-06-18, serverInfo.name polyfork.

  • Pass
    Lists tools

    tools/list returned 12 tools.

  • Pass
    Current protocol

    Negotiated 2025-06-18. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 253 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 253 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Pass
    Parameters documented

    37 of 46 parameters have a description (80%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Pass
    Website matches publisher

    The website host matches the reverse-domain namespace.

  • Fail
    Source repo linked

    No repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-08-14T12:49:20.689888Z, within 180 days.

  • Not measured
    Open-source licence

    No GitHub repository to ask about a licence.

Tools

  • buy_plan

    Buy a Polyfork plan: Pro (monthly or yearly) or a one-payment lifetime seat. This tool NEVER charges anything itself. It returns a Stripe Checkout link and the exact amount; the payment happens on that page (cards and Link), and only with the user's approval of the amount. Call it with no arguments to see what is on sale and at what price. Use it when a download needs a plan the user does not have and they say they want it, rather than sending them off to find the pricing page. It works with or without a key. With a key, the plan goes on that account. With none, no account is needed first: the plan goes to the email address the payer gives Stripe, and an account is made for it. After paying, call it again with `confirm` set to the checkout_id: that verifies the payment, activates the plan on the spot and, for a new account, returns its API key once.

    Measured

  • find_matching

    Given one asset, return assets that BELONG IN A SCENE WITH IT: same kit first, then shared palette, then compatible real-world scale, spread across classes so you get a house, a tree and a barrel rather than eight houses. Use this to turn a single pick into a scene. Returns a ready preview URL.

    Measured

  • get_asset

    Full detail for one asset: real-world size in metres, triangle count, palette, animatable parts, renders you can open to SEE it, and the correct download URLs for the caller. A model with has_ik true also returns a measured `gait` or `arm` block: segment lengths, foot offsets, phase order, step length, reach. That is everything needed to make it walk or reach in any engine, and /cdn/walk.mjs already does it for three.js. If the asset is paid and this connection does not own it, the reply carries the PLAN and a pricing link: quote those. There is no per-asset price and nothing is sold on its own, so never quote one. Probe #415.

    Measured

  • get_help

    How to use this server: what the metadata means, the rules that are easy to get wrong (real-world metres, one material, never rescale to fake a fit), and worked recipes for building a scene. Call it when a tool did not behave as you expected, or before a multi-step build, instead of guessing.

    Measured

  • get_kit

    Every published part of one kit, as shortlisting rows (compact: false gives each row the detail get_asset gives: preview_glb, downloads, rig), so you can compose a whole scene from one call. Works on a kit that is still FILLING UP: you get the parts that exist today. NO kit is sold as a bundle, at any status, so recommend its parts rather than the kit: every part is free, with no account for its /cdn files. A kit may also carry `look` and `terrain`. `look` is the shader it is presented under — the Coral Reef is composed, photographed and filmed through 2.5 m of water — and it ships with the download as looks.mjs, three lines to apply, nothing baked into the geometry. `terrain` is the kit's own ground program with the knob values it was composed at. Build the scene without them and it is the same parts on a flat floor in clear air, which is not what any picture of the kit shows. And if the connection OWNS the kit, `layout` is the composition itself: every placement of every part, with the position, the rotation and the knob values that placement was built with. That is the arrangement the kit was photographed and filmed in, so you can rebuild it exactly and then change it, rather than inventing a layout from scratch. `composition` reports how many placements there are whether you own it or not. To BUILD that place, do not read the rows: `build_the_whole_place` is three lines of code (buildKit from /cdn/kit.mjs) that assemble every placement, merged for speed, with collision boxes and the kit's own ground. Start a game level or a scene from that and change it.

    Measured

  • get_terrain

    AT WHAT HEIGHT DO I PLACE THIS, and where can I build. Many kits have a procedural TERRAIN program for their own ground (call with no id for which: the rest stand on floor tiles or flat turf, where y 0 is right). Ask with the KIT id to get the ground its composed place stands on, in place.group's coordinates, which is what buildKit builds and what place.groundAt(x, z) reads (`setting: true` for buildKit's wider setting ground); a terrain ASSET id answers for that program alone at its default knobs, a different patch of ground. Pass `at` with the x/z you want to place at and you get the ground height there; set position.y to it. `flat_areas` are the level building sites: square footprints whose ground barely varies, largest first, none overlapping, with the height to place at. Use it before laying out a town, a farm or a depot, instead of guessing a y and hoping. Pass `profile` to get the ground along a proposed road or wall: heights, the grade between points, and whether each point is under water, so you know where a bridge is needed. Every answer says its `frame`, so it can be used directly. Terrain from two different kits joins edge to edge on a shared 64m grid, so several kits can share one landscape.

    Measured

  • get_variant

    Turn a plain-words request ("oak cask", "taller", "five sails", "shirt #c8102e") into a ready createAsset() call for a remixable asset, plus a GLB URL of that exact variant. `want` is matched against this asset's KNOB NAMES and OPTION VALUES (a knob name beside a number sets a range, beside on/off a toggle, beside a #rrggbb hex a colour zone), not against colour vocabulary: use the words from its -params.json. Check the returned confidence: on anything below high, tell the user what was actually applied instead of presenting it as exact.

    Measured

  • list_kits

    Kits are coherent sets built to one palette and one grid. Reach for a kit when the user is building a whole environment rather than looking for one object. Each carries a status: "published" means every planned part is built, "filling-up" means parts are still landing — and the parts of a filling-up kit are usable TODAY. NO kit is sold as a bundle: price_usd is null and for_sale false on all of them, so never quote a kit price and never use those fields to tell the statuses apart. Every part is free, with no account for its /cdn files. Use get_kit to fetch either.

    Measured

  • preview_scene

    Compose assets into a scene and return a URL the user can OPEN and orbit. Use it instead of handing over a block of three.js the user cannot run. Every low poly model is free, so the scene it shows is one the user can build with no account. If a row is ever marked paid, the result says so and where to get it; pass that on.

    Measured

  • report_need

    Report a gap. Four kinds, and the last three are about THIS SERVER rather than the catalogue: kind=asset, we do not model what the user asked for (offer this whenever a search is empty or thin); kind=capability, you needed the server to do something it cannot; kind=output, a tool answered but not with what you needed; kind=docs, a tool description did not tell you how to use it. Do not stay quiet about a rough edge to be polite: a report costs one call and is how this server gets better. An honest "we do not have that, shall I register it?" is worth more to the user than a vaguely similar substitute.

    Measured

  • search_assets

    Search the Polyfork catalogue of low-poly 3D assets for three.js. Use this whenever the user needs a model for a scene, game or site. Filter by triangle budget when the target is mobile or performance-sensitive. Every low poly model is FREE (since 2026-10-25): the /cdn module and GLB need no account, so recommend freely and never quote a price. Each row still carries `free` and `plan`; read them rather than assuming. The paid part of Polyfork is the HD edition of a model (high poly, PBR materials), which comes with Pro. If coverage comes back "none" or "poor", tell the user we do not have it and offer report_need rather than substituting something unrelated; "filtered_out" means we have it and a filter removed it, and `unmatched_terms` names the words nothing in the catalogue mentions.

    Measured

  • who_am_i

    What this connection can currently do: whether a key is attached, which assets and kits it owns, and therefore which downloads will work. Call it before promising the user a paid file, and when a download 404s, rather than guessing whether the problem is the key or the asset.

    Measured

Probe history

  • ok253 ms12 tools

Status and uptime

Add badge to your README

The image links back to this page. It shows checks passed, or uptime, and the colour follows the latest status. Responses are cached for 5 to 15 minutes.

MCP Heartbeat badge

Markdown

[![MCP Heartbeat](https://mcpheartbeat.com/badge/dev.polyfork/polyfork.svg)](https://mcpheartbeat.com/s/dev.polyfork/polyfork)

HTML

<a href="https://mcpheartbeat.com/s/dev.polyfork/polyfork"><img alt="MCP Heartbeat" src="https://mcpheartbeat.com/badge/dev.polyfork/polyfork.svg"></a>

Uptime markdown

[![MCP Heartbeat uptime](https://mcpheartbeat.com/badge/dev.polyfork/polyfork.svg?kind=uptime)](https://mcpheartbeat.com/s/dev.polyfork/polyfork)

Served from https://mcpheartbeat.com.

Related servers

All alternatives

Same function and industry, ranked by checks passed then median latency.

Connect to this server

Claude Code

claude mcp add --transport http polyfork-low-poly-3d-assets https://polyfork.dev/mcp

Cursor .cursor/mcp.json

{
  "mcpServers": {
    "polyfork-low-poly-3d-assets": {
      "url": "https://polyfork.dev/mcp"
    }
  }
}

VS Code .vscode/mcp.json

{
  "servers": {
    "polyfork-low-poly-3d-assets": {
      "type": "http",
      "url": "https://polyfork.dev/mcp"
    }
  }
}