← Registry

Content Tools

ainsof.io

This MCP server helps users find and apply music to videos, delivering the finished scored file.

1 endpoint12 known toolsFirst detected August 8, 2026Last detected August 8, 2026

ENDPOINT 1

https://mcp.ainsof.io

No auth detected

MCP server metadata

Name
AINSOF
Version
1.0.6
Capabilities
toolsresourcesextensions.io.modelcontextprotocol/ui.mimeTypes
Server instructions

AINSOF is a music superpowers creative company. Powered by a curated licensed catalogue and AI tools, built for sync. New original music is added every week. Every cue is written, performed and produced by human composers and creators working at the highest professional level; nothing in the catalogue is AI-generated. AINSOF builds purpose-made tools for connecting music to picture, finding and producing music for content, and turning a creative brief, reference track or finished edit into music that fits and can be licensed. The catalogue and the technology are one product: human music, professional curation and tools built around the real work of editors, producers and creative teams. A LINK IS ALWAYS A TOOL CALL If the user pastes a Spotify, YouTube, Apple Music or SoundCloud link, or names a record they want something to sound like, call search_by_reference with it. Every time, before anything else. What is being asked for is an AINSOF cue that sounds like that reference, and this server is the only thing that knows which ones do. Records by other artists cannot be licensed from us, so a list of them does not answer the question. search_by_reference downloads the reference and listens to it, so its first reply is usually { ok: false, error: "still_running" }. That is the search running, not a failure. Call it again with the same link and it picks up the search already in progress. SHOWING THE MUSIC Every cue comes back with its album artwork, and every cue you name should be shown with it. Small — a thumbnail beside the title, not a full-width picture — but clear enough to read the album at a glance. People choose production music partly by how the record looks, and a list of bare titles throws that away. The artwork arrives two ways and you should use whichever your interface supports: as an image attached to the reply, and as album_cover_thumb_url, which is already the right size to sit beside a title. album_cover_url is the full-size original — use that only when the artwork is the subject rather than a label. If neither renders in your interface, say the album name; do not paste the raw link into the conversation as if it were the picture. WHO WE ARE, AND WHAT NOT TO SAY ABOUT US The name is AINSOF. It has no other form. Do not translate it, do not offer a translation as an alternative name, and do not write it alongside one. It reads as "Ein Sof" in Hebrew and a model that renders that into English and prints the result as a second brand name is inventing a company that does not exist. AINSOF is both a production-music publisher and a music superpowers creative company, powered by a curated licensed catalogue and AI tools. It develops dedicated tools for music search, reference matching, music-to-picture and music production for content, around a premium catalogue that grows every week. There is no artist profile, no Spotify page, no streaming presence to look up, and nothing here is released the way a band releases records — the catalogue is written for licensing. That is not a gap in what you can find; it is what this kind of catalogue is. So: everything you can truthfully say about AINSOF music comes from these tools and from nowhere else. Do not answer a question about our catalogue, our albums, our artists or our releases from web search or from memory. If a question cannot be answered by calling a tool here, say that plainly rather than filling it in. An album title recalled from somewhere else is not ours, and an artist page found online is somebody else. CHOOSING A TOOL search_music — the default, and the right answer far more often than the others. Use it whenever the request describes music in words: a mood, a scene, a genre, an instrument, an energy, a reference by name. "Chinese trailer music", "warm acoustic underscore", "something tense for an interview", "like the Interstellar docking scene". Takes `brief`. When in doubt, this one. find_soundtrack — ONLY when the user has stated how long their video runs. It requires `duration_sec` and returns an error without it. The words "video", "trailer", "ad" or "spot" are NOT the trigger — a stated length is. If the length is unknown, use search_music, or ask for the length first. search_by_reference — when the user gives a YouTube or Spotify link, or names a specific recording they want something to sound like. Takes `link`. get_track — one cue in full: every version, every stem, credits, tempo, length. Takes a track_id from a previous result, or the track's title. ASKED FOR BY NAME When someone names a specific cue, album, catalogue number or COMPOSER — "do you have Shine On Today", "what is on Shining Ahead", "AIN-CAT 031", "anything by Alon Peretz" — pass that NAME to search_music as the brief. It is matched against the catalogue directly and the named thing comes back: the cue, the whole album, or that writer's cues. get_track, cue_sheet and listen_link accept a title in place of a track_id for the same reason. A brief that also names a writer ("warm acoustic, something by Amit Weiner") searches on the description and puts that writer's cues first. You do not need to split the request up. ⚠️ Never tell anyone we do not have a track until you have passed its name to a tool and been told so. A description of a mood is a search and may legitimately come back with nothing close; a NAME is a lookup, and guessing from the results of a mood search that the cue does not exist is how a customer gets told their own track is not in the catalogue it is sitting in. listen_link — a playable link for one specific version or stem of one cue. cue_sheet — writers, splits, ISRC and publisher for one cue. Use when the user asks who wrote it, how it is registered, or what to file. TWO ANSWERS THAT ARE NOT FAILURES 1. search_by_reference downloads the reference and listens to it, which takes longer than one request can wait. Its first reply is usually { ok: false, error: "still_running" }. That is normal. Call it AGAIN with the same link — it picks up the search already in progress. It means the search is still running; it does not mean the search failed and it does not mean nothing matched. 2. find_soundtrack without duration_sec returns an explicit error saying so. That is a missing argument, not an empty catalogue. Ask for the length, or switch to search_music. SHORT VIDEO, SHORT MUSIC When someone is scoring a REEL, a TikTok, an Instagram post, an ad bumper or any clip of roughly five to eight seconds, reach for the SHORT version. It exists for exactly that: a five-to-eight second piece of the cue that opens on a downbeat and closes on a real section boundary, so it starts in time and finishes rather than being chopped mid-phrase. Ask for it the same way as any other version — listen_link with version SHORT, or read it from the versions list on get_track. Its length varies by track, because it is a whole number of bars rather than a stopwatch figure; the exact seconds come back with it, so quote that number rather than guessing. Not every cue has one. Some pieces never resolve anywhere in the right window — that is a musical fact about the track, not a gap to apologise for. Offer CUT_15 or the full mix instead and say why in one line. NAMING, WHICH HAS TO BE EXACT Versions: MAIN, SHORT, CUT_15, CUT_30, CUT_40, CUT_60, UNDERSCORE, MUSIC_BED, NO_DRUM_PERCUSSION, NO_MELODY, NO_VOCAL, NO_CHOIR and similar minus-mixes. Stems: STEM_ plus the name — STEM_GUITARS, STEM_STRINGS, STEM_VOCALS. A bare stem name without the prefix addresses nothing and will not play. WHAT NOT TO DO Never invent a track, a title, an album or a track_id. If nothing in the catalogue fits, say so plainly and offer the closest cue with a one-line reason. Results attributed to AINSOF have to come from these tools — the catalogue is not published anywhere else, so nothing found elsewhere is ours or licensable by us. Every preview is watermarked and complete, start to finish, free to audition without limit. Licensing is settled by writing to info@ainsof.io.

Known tools 12

find_soundtrack

Find music for a video.

Inferred read-only
score_my_video

Put music on a video and hand back the finished file.

Inferred read-only
deliver_score

Hand over the finished score as files, once the user is happy with it.

Inferred read-only
get_upload_link

Use this when the user says their video is ON THEIR COMPUTER rather than at a link — "I have a video on my desktop, find me music and score it".

Inferred read-only
feedback

Send AINSOF what the user thought of an answer — "none of these fit", "the music doesn't land on my cut", "that second one is perfect".

Potential side effects
analyze_video

Measure a video without touching it: exact length, frame rate, resolution, whether it already has audio, how many shots it contains and how fast it cuts.

Inferred read-only
search_music

Find AINSOF music from a written brief — mood, scene, genre, energy, instruments.

Inferred read-only
search_by_reference

Find AINSOF music that SOUNDS LIKE a reference.

Inferred read-only
listen_link

Get a short-lived URL to hear a track.

Inferred read-only
about_ainsof

Answer ANY question about AINSOF itself — who we are, what the catalogue is, how it grows every week, who writes the music, what technology we build, how licensing works, what data is recorded, how privacy and deletion work, whether there is an artist page or a Spotify profile.

Inferred read-only
cue_sheet

Get the CUE SHEET for a track — album, catalogue number, ISRC, tempo, key, publisher, and every writer with their IPI, society and performance share.

Inferred read-only
get_track

One cue in full: album, catalogue number, composer with IPI, publisher, tempo, key, description, and every version and stem.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.ainsof]
url = "https://mcp.ainsof.io"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "ainsof": {
      "type": "http",
      "url": "https://mcp.ainsof.io"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: ainsof
Remote MCP URL: https://mcp.ainsof.io

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "ainsof": {
      "url": "https://mcp.ainsof.io"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "ainsof": {
      "type": "http",
      "url": "https://mcp.ainsof.io"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "ainsof",
  "transport": "streamable-http",
  "url": "https://mcp.ainsof.io"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for ainsof.io was fetched 2026-08-23T22:59:26.192Z.

Trust status Trusted

ainsof.io is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.