dev.teamonly/teamonly
TeamOnly
Is the TeamOnly MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-08.
Deploy AI-built internal apps behind your company login, with a database, files and secrets.
alive probed 2026-11-14 · unchanged since 2026-11-08
- Run it
- npx -y teamonly@0.10.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- teamonly 0.10.0
- Capabilities
- tools
- Instructions
- 952 characters
- Of a 1M window
- 0.3 % of a 1M context window
- Count
- 3.0k tokens in Claude Opus 5.5, exact, measured 2026-11-08. With the Claude Code prefix mcp__…__ on each tool name: 3.1k. The o200k_base estimate is 1.8k. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/sohelsd/teamonly-mcp
- Website
- https://teamonly.dev/mcp
- Registry
- active, updated 2026-11-08 · registry entry
- Changes
- 4 recorded, reachable in 4 of them. A row is added when the result, the tool count or the cost changes.
Most expensive tools
The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.64×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| pull | 293 | 179 | 10 % |
| roles | 254 | 155 | 8 % |
| access | 233 | 142 | 8 % |
| init | 231 | 141 | 8 % |
| set_secret | 221 | 135 | 7 % |
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- snapcn dev.snapcn/mcp · alive
- SpatialPack — 3D asset readiness dev.spatialpack/mcp · needs env
- Tada: automated QA for AI-written code dev.taada/tada · alive
- Tabhand dev.tabhand/tabhand · alive
- dev.threadmine/mcp · alive
- Tinify image tools dev.tinify/mcp · alive
- dev.toolc/toolc · crashed on start
- dev.true402/mcp-server · alive
Servers that mention database or internal.
- Aevia ai.aeviamodeler/aevia · needs auth
- ai.argushq/enforcement-database · no DNS
- EOSL.ai — Hardware End-of-Life Database ai.eosl/eosl · alive
- JustDeploy ai.justdeploy/mcp · needs auth
- ai.mcpmyadmin/mcpmyadmin · needs auth
- MotiBlog ai.motiblog/mcp · needs auth
- QCDatabase.AI ai.qcdatabase/mcp · needs auth
- Schema ai.schemalabs/schema · needs auth
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-08 07:59 | alive | 111 ms | 16 | 3.0k | 1.8k |
| 2026-10-29 07:42 | alive | 170 ms | 15 | 2.8k | 1.7k |
| 2026-10-27 06:52 | alive | 134 ms | 12 | 2.2k | 1.3k |
| 2026-10-26 06:59 | alive | 193 ms | 12 | 1.3k |
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
- The server answers initialize and tools/list. Nothing to fix.