0n3 — the 0n runtime (0nmcp 5)
io.github.0norkPublished by GitHub account 0norkv5.0.6Updated Oct 29, 2026
Your apps as AI tools: one sign-in, one vault, 125 services and 1,851 endpoints, with receipts.
Overview
0n3 (0nmcp) exposes 125 services and 1,851 endpoints from your connected apps as AI tools, behind one sign-in and one vault, with receipts.
- What you can do
- Connect your apps through a single 0n3 sign-in and hosted vault.
- Let an assistant call endpoints across 125 services (1,851 endpoints) as tools.
- Use a hosted vault listing your connected services, reachable from a local stdio install.
- Keep a receipt trail of the calls made through the runtime.
- No individual tools are listed in the manifest, so exact operations are not documented here.
- When to use it
- Worth considering when you want one assistant connection to reach many of your existing apps and services instead of installing a separate MCP server for each, and you are comfortable routing those calls through a hosted vault.
- Requirements
- Either the remote endpoint at 0n3.app with OAuth (Authorization header) or the local npm package 0nmcp over stdio. A 0n token is needed: ON3_TOKEN for stdio (optional, used to list your hosted vault) and an Authorization bearer token for the remote endpoint. A 0n3 account and network access.
Installation
In SourceWeft
- Open 0n3 — the 0n runtime (0nmcp 5) in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.0nork%2F0nMCP/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"0n3-the-0n-runtime-0nmcp-5": {
"type": "http",
"url": "https://0n3.app/mcp"
}
}
}README
This repository has no README.
Tools
0Version history
3- v5.0.6LatestOct 29, 2026
- v5.0.2Oct 25, 2026
- v4.5.1Sep 16, 2026
Score
60% 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 daysRequired25 pts
- Auth declaredRequired10 pts
- 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
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.