Publisher portfolio
apolocine
Explore the MCP servers published by apolocine, with independent connection checks, performance measurements, and setup instructions for each project.
- Listed servers
- 2
Active projects in this portfolio. Deleted and deprecated registry rows are excluded.
- Sampled servers
- 0
Active servers with a recorded connection probe
- Latest probe connected
- 0
Latest stored probe connected. This is not a live guarantee.
- Repositories
- 2
Distinct source repositories linked by the active listings
Portfolio overview
MCP servers
Compare connection status and measurements. Open a server for its tools, check results, and client configuration.
| Server / capability | Last probe | Median latency | Checks passed | Last checked |
|---|---|---|---|---|
io.github.apolocine/orm-mcp MCP server for @mostajs/orm: generate, lint (24 rules) & migrate EntitySchemas. | Not measured | Not measured | 4 / 6 | Not checked yet |
io.github.apolocine/mosta-net 1 MCP server, 13 databases, zero config. Multi-protocol transport with Auth + RBAC. | Not measured | Not measured | 3 / 6 | Not checked yet |
Company & identity
About apolocine
apolocine publishes MCP servers under the io.github.apolocine namespace. This namespace is associated with a GitHub login in the MCP Registry.
Namespace verification connects the publisher to its registry identity. It does not certify the security of individual servers.