Is pro.aicut/aicut 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://mcp.aicut.pro/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://mcp.aicut.pro/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://mcp.aicut.pro 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 54 tools: analyze_video, browse_series, change_story_scene, confirm_upload, delete_video, describe_cast_member, edit_video, extend_video, fire_story_video, generate_audio, generate_cast, generate_cast_portraits, generate_fake_text_video, generate_from_niche, generate_image, generate_image_story, generate_lipsync, generate_story_video, generate_video, get_analysis, get_audio, get_balance, get_image, get_post_status, get_recipe, get_recreate_brief, get_video, list_analyses, list_audio, list_characters, list_image_story_styles, list_images, list_models, list_niches, list_series, list_series_ideas, list_social_accounts, list_trends, list_videos, list_voices, motion_control, prepare_post, publish_post, regenerate_cast_portrait, regenerate_story_frame, remove_story_scene, render_story_video, review_post, show_generation, upload_media, upload_media_widget, upscale_image, upscale_video, wait_for_generation.

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 namepro.aicut/aicut
Endpointhttps://mcp.aicut.pro/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