io.github.apilocker/apilocker

API Locker

Is the API Locker MCP server down? No. It is up and needs env, probed 2026-10-30.

Encrypted credential vault: LLM, service & OAuth keys. 21-tool MCP server for your AI agent.

needs env probed 2026-11-14 · unchanged since 2026-10-30

MCP error -32000: Connection closed
Not configured. Run `apilocker register` first.

Run it: npx -y apilocker@1.0.3 (stdio, probed in a container with the network off)
Host: npmjs.com
Repository: https://github.com/apilocker/apilocker
Website: https://www.apilocker.app
Registry: active, updated 2026-04-10 · registry entry

More servers

Other registry entries on npmjs.com, the ones next to this name; all of them.

io.github.apeirontrade/provenance-mcp · alive
io.github.apexapi/apexapi-mcp · alive
APIFreaks MCP io.github.api-freaks/apifreaks-mcp · alive
apiauto.space: Encar, Che168, Copart, IAAI io.github.apiauto-space/apiauto-mcp · alive
DOMShell io.github.apireno/domshell · needs env
io.github.apitier/mcp-server · alive
Jev Filter io.github.apixly-ai/jev-filter · needs network
io.github.aplaceforallmystuff/mcp-arr · alive

Servers that mention locker.

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

The server exits because an environment variable is missing. The probe starts the package without secrets. A server that starts without secrets and asks for them on the first tool call is measured.