Is com.spriteship/spriteship up? Live MCP status

Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.

Endpointhttps://spriteship.com/mcp
Page built

One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.

Live status every few hours: Wellknown

Email me when this server changes

That was one look. To hear when it stops answering or its tools change, leave an address.

Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.

Monthly census, 6 October 2026

The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).

Agent discovery documents at this origin

A2A agent cardNot published (HTTP 404).
/.well-known/agent-card.json
MCP server card (SEP-2127)Not published (HTTP 404).
https://spriteship.com/mcp/server-card
MCP server card (SEP-1649 location)Not published (HTTP 404).
/.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026
Web Bot Auth key directoryNot published (HTTP 404).
/.well-known/http-message-signatures-directory

Read at https://spriteship.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.

Tool changes between snapshots

In the 2026-10 snapshot it listed 90 tools: animate_asset, approve_automatic_pose_fallback, approve_directional_poses, cancel_job, commit_map_draft, convert_texture_to_material, create_animation_from_pose, create_asset, create_character, create_project, create_ui_composition, create_ui_pack, duplicate_animation, export_map, fix_asset_seams, frame_animation, generate_character_animation, generate_character_turn, generate_pose, generate_project_intake, generate_project_vision, generate_ui_pack, get_asset, get_character, get_character_manifest, get_credits, get_custom_fields, get_export_command, get_frames, get_integration_status, get_job, get_map, get_map_draft, get_project, get_project_export_command, get_project_export_review, get_project_export_status, get_project_style_guide, get_subscription_allowances, get_ui_pack, get_ui_pack_batch, get_ui_pack_batch_recovery, get_ui_pack_export_command, import_asset_image, list_assets, list_character_poses, list_characters, list_map_revisions, list_maps, list_projects, list_ui_fonts, list_ui_packs, map_authoring_context, map_authoring_schema, map_project_library, map_workbench_context, mirror_animation, phase_split, plan_sync, prepare_map_draft, prepare_map_edits, preview_map_draft, rebuild_character, recover_ui_pack_components, regen_asset_pair, rematte_animation, rename_ui_component, replace_ui_component_png, reprocess_asset, restore_map_revision, resume_pose, resume_ui_pack_batch, retry_job, retry_unusable_result, revise_asset, revise_ui_pack_png, run_map_playtest, save_project_style_guide, save_ui_component_defaults, save_ui_pack_style, select_frames, set_asset_collision_body, set_asset_collision_roles, set_asset_runtime_intent, set_character_collision_roles, start_project_export, suggest_motion_hint, suggest_project_style, validate_ui_component_layout, whoami.

Its tools changed between 2026-09 and 2026-10:

Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.

The listing

Registry namecom.spriteship/spriteship
Endpointhttps://spriteship.com/mcp
Publisher repositorynot known: the registry did not return this listing within 4 seconds

Also

The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt

Free, no key, no signup. Terms · Privacy