Skills/npm/firesidefm-mcp-server

firesidefm-mcp-server@0.3.0

CAUTION

Publisher claims: "Unofficial MCP server for the Fireside.fm podcast hosting API" Observed in sandbox: sends data to fireside.fm.

Registry npm (MCP server)Publisher jkotzker · publishing for 32 daysInstalls 870Last detonated 21 h ago

Coverage

Started with a decoy FIRESIDE_API_TOKEN; tool list observed. Tool calls with a real credential not tested.
Tested
server startup with a tagged decoy in FIRESIDE_API_TOKEN · MCP initialize and tools/list · every tool description, for hidden instructions · where the decoy credential went · every file read, file written and host contacted by what ran
Not tested
what the tools do when called with a real credential
Needs
FIRESIDE_API_TOKEN — give it to the server where it runs, through vet-skills run --secrets, so the value never enters the server's environment. Never paste a credential into a chat, a ticket or a report.

Before you give it your token

It will ask for
FIRESIDE_API_TOKENConfiguration, not credentials: FIELD_KEYS, FIRESIDE_API_BASE_URL, FIRESIDE_PODCAST, FIRESIDE_READ_ONLY, FIRESIDE_UPLOAD_DIRS
Where it talks to
no vendor host named in the codeAlso fireside.fm — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · contacted fireside.fm (undeclared)
What we could not test
what the tools do when called with a real credential

Find out what these hosts are first. In the honeypot it contacted fireside.fm, which nothing in the package names as its own. If that is the vendor's service, fine; if you cannot place it, do not connect it.

$vet-skills run --net fireside.fm -- npx -y firesidefm-mcp-server

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) on 2026-11-13 and scored it 71/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: sends data to fireside.fm.

Behavior trace

Honeypot run · 51 s · 2 scenarios
t+CategoryObserved action
0.0sprocessno install scripts in bundle
11sprocessdependency install exit 0
31sprocessrelaunched with a decoy FIRESIDE_API_TOKEN (tagged; nothing real)
51snetworkCONNECT tcp://fireside.fm:443 · not in the allow-list, refused
51sclaimed8 tools with a decoy FIRESIDE_API_TOKEN: fireside_get_account, fireside_list_podcasts, fireside_get_podcast, fireside_list_episodes, fireside_get_episode, fireside_get_episode_metrics, fireside_get_monthly_downloads, fireside_get_daily_downloads
51stools6e30dd3721403893
51stoolsc045394dbf286f9c
51stools72ef818fa0421049
51stools969a561743508ca1
51stools713693b26029f8ef
51stools6c9d4b286818d1c6
51stools84cd64988c6c2500
51stools52651cdc9daf780b
51sprocessscript backend runs setup only
51sprocessno install scripts to re-run

Static findings

No findings across 1,874 lines in 21 files.

Cost to the agent

Instructions loaded
≈56 tok
1 file · 21 in bundle
Tool list per prompt
≈1,583 tok
8 tools · 198 per tool
Handshake
883 ms
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 209

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 firesidefm-mcp-server@0.3.0 as of 20 h ago. This is the package itself, not its dependencies.

What would make this Verified

9 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Contacts a host you did not declare≈ +23 on the totalList every host you talk to in SKILL.md frontmatter (`network: [api.example.com]`), or stop contacting the ones you cannot justify.
  2. Unclaimed publisher≈ +8 on the totalClaim jkotzker: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
Publish a new version to npm, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim jkotzkerPropose a patch to the maintainer