linkbreakers-mcp@1.200.2
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=c03c5b09-f543-4310-b8a0-e3716dd05db4&code_challenge=HToTf9vTTMYZn-ydysdDX8OIwnTLqSJOZX8MIItPaTc&code_challenge_method=S256&redirect_uri=http%3A%2F%2F127.0.0.1%3A47823%2Fcallback&state=e1f2a9d9d07d5050a90603c176). 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=c03c5b09-f543-4310-b8a0-e3716dd05db4&code_challenge=HToTf9vTTMYZn-ydysdDX8OIwnTLqSJOZX8MIItPaTc&code_challenge_method=S256&redirect_uri=http%3A%2F%2F127.0.0.1%3A47823%2Fcallback&state=e1f2a9d9d07d5050a90603c176). 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.
What changed since 1.195.11
vet-skills diff linkbreakers-mcp 1.195.11 1.200.2In the sandbox, this version reached for nothing 1.195.11 did not. Compared from the two recorded runs, not from source.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
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=c03c5b09-f543-4310-b8a0-e3716dd05db4&code_challenge=HToTf9vTTMYZn-ydysdDX8OIwnTLqSJOZX8MIItPaTc&code_challenge_method=S256&redirect_uri=http%3A%2F%2F127.0.0.1%3A47823%2Fcallback&state=e1f2a9d9d07d5050a90603c176). Authenticated tool behavior not tested) on 2026-11-18 and scored it 87/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.200.2 as of 36 min ago. This is the package itself, not its dependencies.