flin-linkedin-posts-mcp@0.3.2
VERIFIED· not startedPublisher claims: "Local MCP server for LinkedIn member posts and personal analytics with separate app logins" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
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
- no vendor host named in the codeAlso linkedin.com — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; 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 0.2.9
vet-skills diff flin-linkedin-posts-mcp 0.2.9 0.3.2This version reaches for something 0.2.9 did not: 1 new host (linkedin.com). Compared from the two recorded runs, not from source.
- New hosts
- linkedin.com
0.2.9 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only.
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; not started: dependency install failed; the server itself was not observed) on 2026-11-21 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: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
npx --yes @anthropic-ai/[email protected] validate manifest.jsonFix: Pin versions and sources; vendor anything fetched at install time."https://user:[email protected]/rest/posts", "https://api.linkedin.com:444/rest/posts",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.@pytest.mark.parametrize("uri", ["http://user:[email protected]:1234/callback", "http://127.0.0.1:0/callback", "https://example.com/callback"])Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.assert all(not any(part in {".env", ".git", ".venv", "__pycache__", "tokens.json"} for part in Path(name).parts) for name in names)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.os.execve(uv, command(uv), environment(os.environ)) # nosec B606Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.return subprocess.run(args, env=env, capture_output=True, text=True, check=True, timeout=60).stdout.strip()Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.npx --yes @anthropic-ai/[email protected] validate manifest.jsonFix: Pin versions and sources; vendor anything fetched at install time.module = importlib.util.module_from_spec(spec)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.spec.loader.exec_module(module)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.module = importlib.util.module_from_spec(spec)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.spec.loader.exec_module(module)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.module = importlib.util.module_from_spec(spec)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.spec.loader.exec_module(module)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.spec.loader.exec_module(module)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.module = importlib.util.module_from_spec(spec)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.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
Not checked against OSV yet; the weekly check has not reached this version.