Publisher · GitHub account
MCP servers published by shibley
4 servers in the official MCP Registry are published under the namespace io.github.shibley/ and have a page in this directory: all remote, reached by URL. First published 2026-07-30; latest update 2026-10-01.
What this publisher publishes
Names under io.github.shibley/ can only be published by someone who signs in to the MCP Registry as the GitHub user shibley, or with the rights the registry requires in the GitHub organisation of that name (its documentation now asks for an organisation owner). The name shows which GitHub account published the entry; it does not show that the account belongs to the company whose product a server works with.
- Namespace
io.github.shibley- Servers with a page
- 4
- Categories
- data (1), developer (1), media (1), other (1)
- Transports
- Streamable HTTP (4)
- Remote servers declaring a header
- 0 of 4
- Websites stated
- aidataparser.com, aisotools.com, apistatuscheck.com, mymcptools.com
- First published
- 2026-07-30
- Latest update
- 2026-10-01
Source repositories
The 4 repositories these servers state, with how many servers name each, most named first.
All 4 servers, A to Z
| Server | Runs |
|---|---|
| AIDataParserPDFs, images and messy text to schema-guaranteed JSON. try_parse runs a real extraction, no key. | Remote · HTTPLive check: ✓ handshake |
| AISOToolsSearch, compare, and find alternatives across a catalog of 3,000+ AI tools. | Remote · HTTPLive check: ✓ handshake |
| API Status CheckLive status probes plus published uptime and incident history for 280+ APIs and cloud services. | Remote · HTTPLive check: ✓ handshake |
| MyMCPToolsFind MCP servers and check whether they actually respond, via live handshake probes. | Remote · HTTPLive check: ✓ handshake |
Grouped by registry namespace, as the MCP Registry states it. A page here is not an endorsement and nobody pays to be listed: editorial policy · Before you connect a server