Publisher portfolio
piiiico
Explore the MCP servers published by piiiico, with independent connection checks, performance measurements, and setup instructions for each project.
- Listed servers
- 3
Active projects in this portfolio. Deleted and deprecated registry rows are excluded.
- Sampled servers
- 2
Active servers with a recorded connection probe
- Latest probe connected
- 2
Latest stored probe connected. This is not a live guarantee.
- Repositories
- 3
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 |
|---|---|---|---|---|
check-claim Check that a source really says what your claim says, before you publish. Verbatim, multi-path. | Responded | 163 ms | 14 / 22 | |
Commit — Supply Chain Risk Scoring Supply chain risk scoring for npm, PyPI, Cargo, and Go. 9 tools. Behavioral signals. | Responded | 142 ms | 14 / 22 | |
AgentLair Give AI agents a real email address, vault, calendar, and task delegation via MCP. | Requires auth | Not measured | 5 / 22 | Not checked yet |
Company & identity
About piiiico
piiiico publishes MCP servers under the io.github.piiiico 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.