Publisher portfolio
shibley
Explore the MCP servers published by shibley, with independent connection checks, performance measurements, and setup instructions for each project.
- Listed servers
- 4
Active projects in this portfolio. Deleted and deprecated registry rows are excluded.
- Sampled servers
- 4
Active servers with a recorded connection probe
- Latest probe connected
- 3
Latest stored probe connected. This is not a live guarantee.
- Repositories
- 4
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 |
|---|---|---|---|---|
AIDataParser PDFs, images and messy text to schema-guaranteed JSON. try_parse runs a real extraction, no key. | Responded | 539 ms | 15 / 22 | |
AISOTools Check whether AI assistants recommend a product, and search or compare 3,000+ AI tools. | Responded | 496 ms | 15 / 22 | |
API Status Check Live status probes plus published uptime and incident history for 280+ APIs and cloud services. | Responded | 808 ms | 14 / 22 | |
MyMCPTools Find MCP servers and check whether they actually respond, via live handshake probes. | Unreachable | Not measured | 5 / 22 |
Company & identity
About shibley
shibley publishes MCP servers under the io.github.shibley 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.