SkillFM Beacon
Register the SkillFM health-and-cost MCP listing when you want Beacon’s full audit surface—tokens, spend, BYOK, and cleanup—in one registry slug.
Overview
SkillFM Beacon (ai-health-token-usage-byok-cost-cleanup) is a MCP server for the Operate phase that bundles health checkups, token and cost views, BYOK vault checks, and cleanup audits.
What is this MCP server?
- Registry title SkillFM Beacon with AI health checkup and agent monitoring
- LLM spend and AI cost optimizer signals for MCP-connected workflows
- BYOK and local vault keywords for provider key hygiene
- Slow-agent cleanup and context cleanup audit hooks
- npm @skillfm/mcp at version 0.1.1 with stdio transport
- Registry version 0.1.1
- Package identifier @skillfm/mcp on registry.npmjs.org
- GitHub repository id 1240555653 (skillfm-mcp)
What problem does it solve?
Searching the MCP registry for token or cleanup help still leaves you without a single server that ties health, spend, and BYOK together inside the agent.
Who is it for?
Builders who add MCP servers by exact registry name and want the full SkillFM audit keyword set in one entry.
Skip if: Anyone who only needs Claude-specific usage without BYOK or cleanup—use the Claude Code–focused SkillFM listing instead.
What do I get? / Deliverables
Installing this registry id gives your client the 0.1.1 Beacon package so tools can run unified health, usage, cost, and cleanup audits on demand.
- Beacon tool surface reachable under the long-form registry id
- Version 0.1.1 package pin for reproducible agent setups
- Health, usage, cost, and cleanup audit responses for agent-driven triage
Recommended MCP Servers
Journey fit
Long-tail registry names map to the same operate problem: keeping agent spend and context under control after you are live. This slug emphasizes monitoring sub-capabilities (health, usage, cost, cleanup) that belong on the operate monitoring shelf.
How it compares
Long-name registry variant of the same Beacon MCP server, not a separate observability product.
Common Questions / FAQ
Who is this SkillFM registry entry for?
It is for MCP users who want SkillFM Beacon’s combined health, token, cost, BYOK, and cleanup tooling under the descriptive registry slug.
When should I use this entry versus skillfm?
Use it when your installer or docs reference io.github.ericm1018/skillfm-ai-health-token-usage-byok-cost-cleanup or you need registry version 0.1.1 explicitly.
How do I add this server to my agent?
Configure stdio MCP with the @skillfm/mcp npm package per SkillFM docs, using this registry id in Skillselion or your client’s server manifest, then reload the agent.