mcpbeat Sign in

Songlinks MCP Server

by songlinks Your server? Claim it
answering

Songlinks is answering right now. Last checked 6 min ago. It exposes 4 tools.

Find the songwriter behind a name or IPI name number, under every spelling and number.

Uptime history 10 days of history
10 days agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
619 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 24 October 2026. No other catalogue keeps this.

25 Oct a tool description was rewritten find_songwriter
24 Oct a tool description was rewritten find_songwriter

Nothing serious here today

Today is the operative word: we check Songlinks every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

run in your terminal
claude mcp add songlinks --transport http https://songlinks.io/mcp
Settings → Connectors → Add custom connector, then paste this address
https://songlinks.io/mcp
~/.codex/config.toml
[mcp_servers.songlinks]
url = "https://songlinks.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "songlinks": {
      "url": "https://songlinks.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "songlinks": {
      "type": "http",
      "url": "https://songlinks.io/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

songwriter
find_songwriter
Use when the user names a songwriter or composer and wants to know who they are, which person a name belongs to, or every registration of that writer. Returns the persons the name could be: each with a person ID, the names and IPI name numbers they are registered under, how many works, and a person_url to cite. Pairs listed under possibly_the_same_person were held apart and are not merged; `why` says why. Candidates are this lookup's own grouping, made afresh for the name, and can differ from the stored person that get_songwriter and the person page describe: a candidate can include records with no IPI name number that the stored person lists apart, and two candidates can carry the same person_id when this lookup keeps apart records the stored person joined. Each record's person_id is the stored person it belongs to, or null; person_records is how many records that person holds, and records_not_in_this_answer how many of them this candidate does not, because they sit in another candidate or outside this lookup. A candidate whose records belong to more than one stored person has no person_id and lists them in stored_persons, with a note: the stored records hold those registrations as different people. For a person's registrations as they stand, call get_songwriter. A candidate's works counts every record in it, records held apart from the person included; the person's own count is get_songwriter's works.total. Registrations are under legal names. When the user gives a professional or stage name and you know the writer's legal name, search the legal name first: a stage name usually returns other people whose names contain those words, not the writer. If the writer you expect is not among the candidates, or song_match.match is none, try their legal name. truncated means more registrations matched than one answer groups: a fuller name narrows it. Give a song title they wrote, when known, to say which of several namesakes wrote it. A one-word name is not searched: ask for the full name.
get_songwriter
Use when you have a Songlinks person ID (SLP-XXXX-XXXX-X), from find_songwriter or a person page, and the user wants that writer's details: the registrations grouped into the person, records listed apart as possibly the same person, and their first works. Each record says how it was joined: `main` marks the record the ID was issued on, and `rule` is the evidence: same_ipi (another of the person's records carries the same IPI name number), ipi (it carries the person's own number), model (judged the same writer from works, co-writers and publishers in common; `score` is how sure), corroborated (confirmed by an independent source) or verdict (decided by a person). At most 25 works are listed; works.total is the full count and the person page lists the rest. works.ordered_by is `recordings` when the list starts with the most-recorded works, and `coded` when it is in catalogue-code order: then it is a sample, not the writer's best-known songs.
songwriter_by_ipi
Use when the user has an IPI name number (up to 11 digits, often written without its leading zeros) and wants to know which songwriter holds it. Returns the person or persons holding the number, each with a person ID and person_url; use get_songwriter for one person's details. `none` means no person here holds it: it may be a publisher's number, or one whose registrations have not been grouped.
writers
check_writers
Use when the user has several IPI name numbers, such as the writers on a song, a catalogue or a registration file, and wants to know who each one is, or whether some of a writer's works sit under another spelling or number. Up to 50 numbers per call. For each: the person holding it, their registered names, works in total and on their main number, works_elsewhere (registered only under another spelling or number), and a person_url.

Endpoints

URLTransportStateLatencyChecked
https://songlinks.io/mcp streamable-http answering 476 ms 6 min ago

Alternatives to Songlinks

same job, measured the same way
Dubai Log
by rowb-dubai-log

UAE travel and living cost calculators with the published source behind every number.

4 tools answering
Telnyx
by stucchi

MCP server for the Telnyx API — billing, phone numbers, and messaging

138 installs/wk local only
Eaa Form Lint Wcag22
by jmshinhwa

Names every WCAG 2.2 AA form failure on its line, with the criterion and the fix

30 installs/wk local only
Vitrus analytics
by vitrus

Read-only analytics for all your apps: users, AI traffic, revenue, with the SQL behind every number.

answering
Calmido Phone Number Lookup
by calmido

Who is calling? Spam reports, a verdict and the business behind NL, BE and LU phone numbers.

1 tools answering
LNX link in bio
by lnx

Build a free link-in-bio page (lnx.net/name) for the user from their links, socials and bio.

2 tools answering
cliphou.se release videos
by cliphou

Turns every release into a social video. Finds the selling points, picks the angle, writes the copy.

6 tools answering
K
Korpi API
by reksely

MCP server for the Korpi API: every top AI video, image and text model behind one key and one bill.

374 installs/wk local only

Songlinks — questions

Answers built from our own checks of this server.

What can Songlinks do?
It exposes 4 tools, read directly from the server on our last check. Among them: check_writers, find_songwriter, get_songwriter, songwriter_by_ipi. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Songlinks working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 619 ms. The bar chart above shows every period we have measured.
How do I connect Songlinks?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Songlinks need an API key?
No. Songlinks completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Songlinks?
It answers our handshake in 619 ms on average, which is faster than 19% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.