snapWONDERS MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SNAPWONDERS_API_KEY | Yes | Your snapWONDERS API key, from https://snapwonders.com/profile/api-keys |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyse_fileA | Run forensic analysis on a local image or video and return the per-file verdicts. Reports the A–F grade, what the metadata reveals (GPS, device fingerprint, encoder signatures), manipulation evidence, and any hidden content detected. A null verdict means no answer, not a negative one. Fields such as
Args:
file_path: Path to a file on this machine. |
| hide_fileA | Hide a file inside a cover image or video, and save the result to disk. The output looks like an ordinary photo or video. Recovering the hidden file needs this exact password — it is not stored anywhere and cannot be reset, so make sure the user knows what it is before running this. Args: secret_path: The file to conceal. cover_path: The image or video that will carry it. password: Passphrase required to reveal it later. output_dir: Where to write the result. Defaults to alongside the cover file. |
| reveal_fileA | Extract content hidden inside an image or video, and save it to disk. Args: stego_path: The file believed to contain hidden content. password: The passphrase it was hidden with. output_dir: Where to write what is recovered. Defaults to alongside the input. |
| convert_fileA | Convert a local image or video to another format, and save the output to disk. Args:
file_path: The file to convert.
output_format: Target format. Images: |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct action on a file: analyse (forensic report), hide (embed), reveal (extract), convert (transcode). analyse_file and reveal_file both touch hidden content, but analyse only reports verdicts while reveal extracts with a password, and the descriptions make that distinction explicit.
All four names follow the same verb_noun snake_case pattern (analyse_file, hide_file, reveal_file, convert_file). The verb is always the operation and the noun is consistently 'file', with no mixed conventions.
Four tools sits comfortably in the 3-15 sweet spot and each covers a distinct, non-overlapping operation in the media-forensics workflow. There are no filler or redundant tools, and the scope is tightly matched to the server's stated purpose.
The core lifecycle is covered: forensic analysis, steganographic embedding, extraction, and format conversion. Minor gaps remain—no batch/multi-file processing, no standalone metadata export, and no verification-only path that avoids writing an output file—but these are workaround-able.