linkbreakers-mcp@1.195.5
VERIFIED· startup onlyPublisher claims: "Local stdio bridge to the Linkbreakers MCP server (https://mcp.linkbreakers.com) for MCP clients that only run local servers." Observed in sandbox: calls mcp.linkbreakers.com only, touches nothing outside the project, writes no memory.
Coverage
Started and answered initialize; the tool list did not come back (tools/list error: MCP error -32001: Linkbreakers sign-in required. Finish the OAuth sign-in opened in your browser (https://mcp.linkbreakers.com/oauth/authorize?response_type=code&client_id=fc690fc5-3123-4b75-80da-76a0e810565d&code_challenge=jtTJ-tK3HoQlVSpwmjkaMT5bPsOaWiE2lVjIEuDk2J4&code_challenge_method=S256&redirect_uri=http%3A%2F%2F127.0.0.1%3A47823%2Fcallback&state=fba442e93d76b3c6719b89d933). Authenticated tool behavior not tested.- Tested
- server startup over stdio · MCP initialize · every file read, file written and host contacted by what ran
- Not tested
- the tool list · what the tools do when called with a real credential
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- linkbreakers.com (its own)
- What the honeypot saw
- no credential files read · reached only mcp.linkbreakers.com (its own)
- What we could not test
- the tool list · what the tools do when called with a real credential
Connect it under the guard. Started and answered initialize; the tool list did not come back (tools/list error: MCP error -32001: Linkbreakers sign-in required. Finish the OAuth sign-in opened in your browser (https://mcp.linkbreakers.com/oauth/authorize?response_type=code&client_id=fc690fc5-3123-4b75-80da-76a0e810565d&code_challenge=jtTJ-tK3HoQlVSpwmjkaMT5bPsOaWiE2lVjIEuDk2J4&code_challenge_method=S256&redirect_uri=http%3A%2F%2F127.0.0.1%3A47823%2Fcallback&state=fba442e93d76b3c6719b89d933). Authenticated tool behavior not tested. The code names no credential variable and talks to linkbreakers.com, its own; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; started and answered initialize; the tool list did not come back (tools/list error: MCP error -32001: Linkbreakers sign-in required. Finish the OAuth sign-in opened in your browser (https://mcp.linkbreakers.com/oauth/authorize?response_type=code&client_id=fc690fc5-3123-4b75-80da-76a0e810565d&code_challenge=jtTJ-tK3HoQlVSpwmjkaMT5bPsOaWiE2lVjIEuDk2J4&code_challenge_method=S256&redirect_uri=http%3A%2F%2F127.0.0.1%3A47823%2Fcallback&state=fba442e93d76b3c6719b89d933). Authenticated tool behavior not tested) on 2026-11-09 and scored it 86/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: calls mcp.linkbreakers.com only, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 25 s · 2 scenariosStatic findings
No findings across 470 lines in 8 files.
Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for linkbreakers-mcp@1.195.5 as of 5d ago. This is the package itself, not its dependencies.