Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PersonCraft

REMOTE · PERSONCRAFT.COM

Your own Claude designs and codes Godot 4 games; each build is tested with real screenshots.

Available components

+36 this week 74 Trust /100

Last scanned (21 hours ago)

Scores higher than 61% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Entertainment and Games

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security94
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 366 tokens (~183/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 1 category

A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +36
    • Transport: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Tool coverage: 0 functional
    • First check of Schema quality: fail functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: good functional
  • 9 Nov 26 38

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://personcraft.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.personcraft.com CN=YR2,O=Let's Encrypt,C=US 26 Sept 2026 25 Dec 2026 RSA 2048 SHA256-RSA 56f99312bc5b1ca550e482ab5204ab09653
SANs: *.personcraft.com, personcraft.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of personcraft.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
personcraft.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On connection
HTTP status 401

WWW-Authenticate challenge Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://personcraft.com/.well-known/oauth-protected-resource/api/mcp"

Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://personcraft.com/.well-known/oauth-protected-resource/api/mcp"
Header Value
strict-transport-security max-age=63072000
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'wasm-unsafe-eval' https://www.gstatic.com https://connect.facebook.net; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://cvdkqhiftwmafzadnddv.supabase.co https://fal.media https://*.fal.media https://www.facebook.com; media-src 'self' blob: https://cvdkqhiftwmafzadnddv.supabase.co https://fal.media https://*.fal.media; font-src 'self' data:; connect-src 'self' blob: data: https://cvdkqhiftwmafzadnddv.supabase.co wss://cvdkqhiftwmafzadnddv.supabase.co https://o4511762758303744.ingest.us.sentry.io https://www.gstatic.com https://www.facebook.com; worker-src 'self' blob:; frame-src https://personcraft-play.vercel.app; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; report-uri https://o4511762758303744.ingest.us.sentry.io/api/4511762768789504/security/?sentry_key=b472cf7c2aa12ad530983d4dd7a95e9a
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(), usb=(), browsing-topics=()
www-authenticate Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://personcraft.com/.well-known/oauth-protected-resource/api/mcp"

Protected resource metadata

Document https://personcraft.com/.well-known/oauth-protected-resource/api/mcp
Retrieved Yes
Resource https://personcraft.com/api/mcp
Authorisation server https://personcraft.com

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://personcraft.com/api/mcp Verified 200
http (plaintext) http://personcraft.com/api/mcp HTTPS enforced 308 https://personcraft.com/api/mcp
MCP tools · 2 exposed · ~327 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
personcraft_consultar_juego ~154

Recupera revisión, diseño y metadata de assets del dueño. Para agregar modelos propios ya generados usa personcraft_listar_assets_3d_reutilizables y personcraft_importar_asset_3d_existente; si faltan assets, sube un archivo licenciado o pide aprobación de gasto separada. Por defecto omite la fuente para no saturar el contexto. includeSource true incluye proyectos de hasta 48 KiB; para los demás usa listar_archivos_juego y leer_archivo_juego por partes. Los binarios permanecen privados. La ejecución permanece not-run hasta un runner aislado de Godot.

NameTypeReqDescription
idstringyes–
includeSourceboolean––

No output schema declared.

No examples provided.

personcraft_crear_juego ~173

Guarda un proyecto propio con id UUID elegido por el cliente y brief (title, idea, locale es/en, dimension 2d/3d y targets opcionales: web, android, ios, windows, macos, linux, steam-windows, steam-macos, steam-linux), sin limitar el género. El asistente conectado escribe el diseño para esos destinos; el dueño aprueba su alcance. Si requiere assets, espera una importación privada antes de escribir código. No hay inferencia del servidor ni consumo de créditos. La verificación actual exporta Web; elegir Android, iOS o Steam no certifica su ejecutable ni publica en tiendas. El proyecto persiste entre sesiones; no garantiza juegos AAA de cualquier alcance.

NameTypeReqDescription
briefobjectyes–
idstringyes–

No output schema declared.

No examples provided.

Install

How do I install the PersonCraft MCP server?

PersonCraft is a hosted endpoint at https://personcraft.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · personcraft.com

# add to Claude Code
claude mcp add --transport http johan1727-personcraft 'https://personcraft.com/api/mcp'
Common questions

What is the PersonCraft MCP server?

PersonCraft is an MCP server listed in the public MCP registry as io.github.johan1727/personcraft. Your own Claude designs and codes Godot 4 games; each build is tested with real screenshots. This page covers its hosted endpoint (https://personcraft.com/api/mcp).

Is the PersonCraft MCP server safe to use?

PersonCraft scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the PersonCraft MCP server expose?

PersonCraft exposes 2 tools: personcraft_crear_juego, personcraft_consultar_juego. Their descriptions and schemas cost roughly 327 tokens of context every time the server is loaded.

Does the PersonCraft MCP server require authentication?

Yes. PersonCraft asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the PersonCraft MCP server still maintained?

PersonCraft is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the PersonCraft MCP server?

VerifyMCP ran 12 checks on PersonCraft, covering TLS certificate, Authorization, HTTPS, HSTS header and 8 more. One item could not be completed, a gap on our side rather than a finding about PersonCraft: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.