Conformance witness · observation, not accusation · recomputable

Tool-surface change observed — api.framesail.com

Endpoint: https://api.framesail.com/mcp

Version string served, unchanged across both observations: 1.27.2

Change first observed: 2026-10-01T07:40:03.170Z

Finding: CLASS_SUSPENDED_CRITICAL

Surface expanded without a version change, and at least one new tool takes an action (writes, sends, moves money, or deletes).

What we observed

Two anonymous tools/list enumerations of the endpoint above, at different times.

The serverInfo.version string was byte-identical in both. The tool set was not.

Tools present in the later enumeration but not the earlier (26):

• account_edit
• assets_edit
• assets_generate
• assets_read
• delete ← takes an action
• editor_edit
• editor_read
• get_generation_options
• get_status
• projects_edit
• projects_read
• render
• script_edit
• script_generate
• script_read
• segment_edit
• segment_restructure
• storyboard_edit
• storyboard_generate
• storyboard_read
• style_edit
• style_generate
• style_read
• voiceover_edit
• voiceover_generate
• voiceover_read

Tools present in the earlier enumeration but not the later (70):

• activate_script_version
• add_music_track
• add_segment_sfx
• analyze_style
• animate_segment
• await_jobs
• browse_audio_library
• build_scenes
• change_segment_type
• combine_segments
• create_asset
• create_channel
• create_project
• create_style
• delete_asset
• delete_project
• delete_style
• director_note
• generate_asset_reference
• generate_script
• generate_segments
• generate_storyboard
• generate_style_template
• generate_voiceover
• get_credit_balance
• get_pipeline_progress
• get_project
• get_script
• get_section_template
• get_segment_assets
• get_segments
• get_style
• get_video_url
• get_workflow_status
• list_assets
• list_channels
• list_models
• list_music_tracks
• list_projects
• list_provider_keys
• list_scenes
• list_style_presets
• list_styles
• list_voice_blocks
• list_voices
• project_director_note
• regenerate_segment_asset
• remove_music_track
• remove_segment_asset
• rescan_voice_blocks
• revise_script
• rollback_segment_asset
• save_script
• scan_script
• set_character_voice
• set_narrator_voice
• set_project_style
• set_provider_key
• set_segment_continuation
• split_segment
• update_asset
• update_caption_config
• update_music_track
• update_project
• update_segment_content
• update_segment_prompts
• update_style_fields
• update_style_references
• update_voice_block
• whoami

Why this may matter to your users

A client that pinned 1.27.2 and reviewed the tool list at

pin time is, today, being served a different list under the same version string. Gateways

and MCP hosts that cache an approved tool set per version will not re-request approval,

because from their side nothing announced a change.

In this case one of the new tools takes an action rather than returning data (delete),

so the difference between the approved set and the served set is not only informational.

Verify this yourself

This is a plain MCP handshake. No credentials, nothing of ours required:

curl -s -X POST 'https://api.framesail.com/mcp' \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'MCP-Protocol-Version: 2025-06-18' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"check","version":"1"}}}'
# then, with the returned Mcp-Session-Id:
curl -s -X POST 'https://api.framesail.com/mcp' \
  -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' \
  -H 'MCP-Protocol-Version: 2025-06-18' -H 'Mcp-Session-Id: <id>' \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}'

Our surface hashes over the sorted tool names plus sorted input-schema property names:

If your own enumeration disagrees with the later hash, we are wrong and we want to hear it.

What this report does NOT say

• It does not allege a breach, compromise, or wrongdoing. An intentional untracked

deploy produces exactly this signal, and that is the most likely explanation.

• It does not assert the new tools are insecure. It asserts only that they appeared

under an unchanged version string.

• We enumerate anonymously, so tools behind authentication are invisible to us.

Absence from our view is not absence from your server.

• Two observations bound when the change was visible, not when it shipped.

Method

Unannounced periodic re-enumeration of a live MCP population — we ask the endpoint

directly on a schedule rather than waiting to be notified. Relevant because only

6.4% of live MCP servers have a working channel to announce a change at all

(69.1% never declare tools.listChanged; of those that do, most expose no

server-initiated stream to send it on). A change like the one above cannot reach a

notification-based monitor, which is why it is normally invisible.

*StillOS Digital Holdings — continuous conformance witness for MCP servers.*

*Report generated 2026-10-30T17:18:50.140Z from observations dated 2026-10-01T07:40:03.170Z.*