io.github.wmarceau/fitness-influencer
io.github.wmarceau/fitness-influencer
Is the io.github.wmarceau/fitness-influencer MCP server down? Yes. It has given no valid answer since 2026-10-17: not found.
AI-powered fitness content creator tools: video editing, image generation, workout plans, analytics.
not found down since 2026-10-17 · probed 2026-11-15 · unchanged since 2026-10-31
error: No solution found when resolving dependencies cause: Because there is no version of fitness-influencer-mcp==1.3.0 and you require fitness-influencer-mc
- Run it
- uvx fitness-influencer-mcp@1.3.0 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/MarceauSolutions/dev-sandbox
- Registry
- active, updated 2026-01-16 · registry entry
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- io.github.wjgoarxiv/vmd-hydrate-mcp · needs mcp<2
- io.github.wmarceau/amazon-seller · crashed on start
- io.github.wmarceau/apollo · crashed on start
- io.github.wmarceau/canva-mcp · crashed on start
- io.github.wmarceau/hvac-quotes · alive
- io.github.wmarceau/instagram-creator · crashed on start
- io.github.wmarceau/md-to-pdf · crashed on start
- io.github.wmarceau/rideshare-comparison · alive
Servers that mention influencer.
- Creator SKILL v2 — Influencer Discovery ai.deinai/creator-skill-v2 · needs auth
- Creator SKILL — Influencer Discovery ai.deinai/creator-skill · needs auth
- RYLA ai.ryla/ryla · alive
- 1stCollab com.1stcollab/influencers · needs auth
- com.getcims/mcp · needs auth
- Inflyu com.inflyu/inflyu · needs auth
- com.infumar/advertiser · needs auth
- com.koalcheck/koalcheck · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-17, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.