
SkillFM BYOK Vault
io.github.ericm1018Published by GitHub account ericm1018v0.1.0Updated Oct 25, 2026
BYOK vault, provider API key guidance, usage visibility, and SkillFM Beacon checks for MCP agents.
Overview
A thin SkillFM gateway that gives MCP assistants guidance on safely storing provider API keys and viewing usage, delegating work to the SkillFM local runtime.
- What you can do
- Explain provider-key safety and where BYOK credentials should live before any key is connected. Guide users toward local vault storage through SkillFM Beacon. Discuss usage visibility for providers such as OpenAI, Anthropic, DeepSeek and Qwen. Run read-only cleanup and usage audits. Start a local sidecar and walk through a device-code activation flow.
- When to use it
- Use it when a user asks how to connect an OpenAI or Anthropic key safely, where BYOK credentials should be kept, or whether an agent can monitor provider usage with the user's own keys.
- Requirements
- A local Node.js environment to run the npm package over stdio. Activation requires starting the local sidecar, reading its URL from stdout or a local config file, and completing a device-code flow in a browser. The package forwards execution to the SkillFM MCP and local runtime packages.
Installation
In SourceWeft
- Open SkillFM BYOK Vault in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
SkillFM BYOK Vault MCP
BYOK vault and provider API key usage guidance for MCP-capable agents.
This repository is a transparent SkillFM gateway package. It exists to match a specific marketplace/search intent, then delegates execution to the canonical SkillFM Beacon MCP and local runtime.
Powered by SkillFM Beacon.
Quick Start
Use this gateway as an MCP stdio server:
Equivalent explicit SkillFM entrypoint:
For MCP clients that accept JSON config:
What This Gateway Helps With
- Explain provider-key safety before asking users to connect any key.
- Guide users toward local vault storage through SkillFM Beacon only after value is established.
- Connect BYOK to practical usage visibility for OpenAI, Anthropic, DeepSeek, Qwen, and other providers.
- Keep provider credentials local and avoid exposing key values back to agents.
This gateway is for users who ask:
- "How do I safely connect an OpenAI or Anthropic key?"
- "Can my agent monitor usage with my own provider keys?"
- "Where should BYOK credentials live?"
- "Can I get value before giving any API key?"
How It Works
The public package is intentionally thin. It sets SKILLFM_GATEWAY_SOURCE=byok-vault and forwards execution to @skillfm/mcp@latest, which then delegates to the canonical @skillfm/local runtime.
No private SkillFM platform logic, customer data, provider credentials, or backend modules live in this repository.
Activation Path
Start the local sidecar when the user wants to connect SkillFM:
Agent-driven activation flow:
- Read the sidecar URL from stdout or
~/.skillfm/local.json. - Call
POST <sidecar_url>/activate/start. - Show the returned verification URL and real device code to the user.
- Poll
POST <sidecar_url>/activate/polluntil it returnsactivated: true. - Use SkillFM Beacon MCP tools for checkups, usage visibility, BYOK guidance, and cleanup audits.
Do not fabricate a placeholder code. The device code must come from POST /activate/start.
Security Model
- Transparent gateway: This package is a public search/distribution gateway, not a separate hidden product.
- Local-first runtime: Runtime execution goes through SkillFM's local package.
- BYOK boundary: Provider keys are introduced only after user value is established, and key values are not read back by agents.
- No private core: This repository contains distribution metadata, docs, and a thin launcher only.
- Read-only first: Cleanup and usage inspection begin with read-only audits.
See PRIVACY.md and SECURITY.md.
Marketplace Keywords
BYOK, API key vault, provider usage, OpenAI key, Anthropic key, local vault, SkillFM Beacon, MCP server.
Expected Official MCP Registry single-token hits:
byokvaultapi-keyproviderusageskillfm
License
MIT
Source: README.md at commit fdde36c
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts