Petstore MCP Server
warningspetstore.run.mcp.com.ai
Swagger Petstore API (v1.0.27) as MCP for testing and prototyping powered by the HAPI MCP server
https://petstore.run.mcp.com.ai/mcpWebsiteOAuthMCP 2025-06-18v0.6.0last checked 24 Aug 2026spoke MCP on 2 of 2 checks (30 days)initialize in 260 msHow to authenticate
Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | OAuth |
|---|---|
| Issuer | https://petstore3.swagger.io |
| Dynamic client registration | ✓Advertised (RFC 7591) |
| Client ID Metadata Document | ✕Not advertised |
| PKCE | ✕plain MCP requires S256; a client that implements only that has no method in common with this server. |
| Grant types | authorization_code |
| Scopes | write:pets, read:pets |
| Protected-resource metadata | ✓Published (RFC 9728) |
| Anonymous access | Handshake succeeds; 19 tools listable |
| Documentation | https://petstore3.swagger.io/api/v3/swagger |
What the probe found
The server exposes a public surface before authorization: updatePet, addPet, findPetsByStatus, findPetsByTags, getPetById, updatePetWithForm, deletePet, uploadFile, getInventory, placeOrder, getOrderById, deleteOrder, createUser, createUsersWithListInput, loginUser, logoutUser, getUserByName, updateUser, deleteUser.
Tools
Contract history
Get alerted when this contract changes
Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.
Prefer a feed reader? This page's contract changes are also an Atom feed.
Status badge
Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.
[](https://mcpi.app/servers/petstore-mcp-server)Own this server?
Sign in to claim this listing by proving control of the endpoint.