Petstore MCP Server
REMOTE · PETSTORE.RUN.MCP.COM.AI
Swagger Petstore API (v1.0.27) as MCP for testing and prototyping powered by the HAPI MCP server
Available components
Last scanned (2 months ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 6 Aug 2026.
Category E-commerce
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety–
Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 4 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (5)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool Safety in Tool SafetyNot scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 15 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 13 Aug 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 12 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 7 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.37 → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 5 Aug 26 +1
The score moved with no change recorded against any check. We would rather say so than guess.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Aug 2026 · Probed https://petstore.run.mcp.com.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.com.ai | CN=WE1,O=Google Trust Services,C=US | 27 Jul 2026 | 25 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | c873799496d39a890e1fc7ed4f93f4ea |
| SANs: mcp.com.ai, petstore.run.mcp.com.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of petstore.run.mcp.com.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 3799 | 8 | Verified |
| com.ai. | No DS | Delegated | ||
| mcp.com.ai. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://petstore.run.mcp.com.ai/mcp | Verified | 200 | |
| http (plaintext) | http://petstore.run.mcp.com.ai/mcp | HTTPS enforced | 301 | https://petstore.run.mcp.com.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
addPet ~45
Add a new pet to the store. - Add a new pet to the store.
| Name | Type | Req | Description |
|---|---|---|---|
| addPetBody | object | yes | – |
| x-hapi-auth-state | string | – | – |
No output schema declared.
No examples provided.
createUser ~43
Create user. - This can only be done by the logged in user.
| Name | Type | Req | Description |
|---|---|---|---|
| createUserBody | object | – | – |
| x-hapi-auth-state | string | – | – |
No output schema declared.
No examples provided.
createUsersWithListInput ~53
Creates list of users with given input array. - Creates list of users with given input array.
| Name | Type | Req | Description |
|---|---|---|---|
| createUsersWithListInputBody | array | – | – |
| x-hapi-auth-state | string | – | – |
No output schema declared.
No examples provided.
deleteOrder ~62
Delete purchase order by identifier. - For valid response try integer IDs with value < 1000. Anything above 1000 or non-integers will generate API errors.
| Name | Type | Req | Description |
|---|---|---|---|
| orderId | integer | yes | – |
| x-hapi-auth-state | string | – | – |
No output schema declared.
No examples provided.
deletePet ~44
Deletes a pet. - Delete a pet.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | – |
| petId | integer | yes | – |
| x-hapi-auth-state | string | – | – |
No output schema declared.
No examples provided.
deleteUser ~42
Delete user resource. - This can only be done by the logged in user.
| Name | Type | Req | Description |
|---|---|---|---|
| username | string | yes | – |
| x-hapi-auth-state | string | – | – |
No output schema declared.
No examples provided.
findPetsByStatus ~45
Finds Pets by status. - Multiple status values can be provided with comma separated strings.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | yes | – |
| x-hapi-auth-state | string | – | – |
No output schema declared.
No examples provided.
findPetsByTags ~56
Finds Pets by tags. - Multiple tags can be provided with comma separated strings. Use tag1, tag2, tag3 for testing.
| Name | Type | Req | Description |
|---|---|---|---|
| tags | array | yes | – |
| x-hapi-auth-state | string | – | – |
No output schema declared.
No examples provided.
getInventory ~35
Returns pet inventories by status. - Returns a map of status codes to quantities.
| Name | Type | Req | Description |
|---|---|---|---|
| x-hapi-auth-state | string | – | – |
No output schema declared.
No examples provided.
getOrderById ~58
Find purchase order by ID. - For valid response try integer IDs with value <= 5 or > 10. Other values will generate exceptions.
| Name | Type | Req | Description |
|---|---|---|---|
| orderId | integer | yes | – |
| x-hapi-auth-state | string | – | – |
No output schema declared.
No examples provided.
getPetById ~40
Find pet by ID. - Returns a single pet.
| Name | Type | Req | Description |
|---|---|---|---|
| petId | integer | yes | – |
| x-hapi-auth-state | string | – | – |
No output schema declared.
No examples provided.
getUserByName ~42
Get user by user name. - Get user detail based on username.
| Name | Type | Req | Description |
|---|---|---|---|
| username | string | yes | – |
| x-hapi-auth-state | string | – | – |
No output schema declared.
No examples provided.
loginUser ~45
Logs user into the system. - Log into the system.
| Name | Type | Req | Description |
|---|---|---|---|
| password | string | – | – |
| username | string | – | – |
| x-hapi-auth-state | string | – | – |
No output schema declared.
No examples provided.
logoutUser ~35
Logs out current logged in user session. - Log user out of the system.
| Name | Type | Req | Description |
|---|---|---|---|
| x-hapi-auth-state | string | – | – |
No output schema declared.
No examples provided.
placeOrder ~44
Place an order for a pet. - Place a new order in the store.
| Name | Type | Req | Description |
|---|---|---|---|
| placeOrderBody | object | – | – |
| x-hapi-auth-state | string | – | – |
No output schema declared.
No examples provided.
updatePet ~41
Update an existing pet. - Update an existing pet by Id.
| Name | Type | Req | Description |
|---|---|---|---|
| updatePetBody | object | yes | – |
| x-hapi-auth-state | string | – | – |
No output schema declared.
No examples provided.
updatePetWithForm ~64
Updates a pet in the store with form data. - Updates a pet resource based on the form data.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | – |
| petId | integer | yes | – |
| status | string | – | – |
| x-hapi-auth-state | string | – | – |
No output schema declared.
No examples provided.
updateUser ~51
Update user resource. - This can only be done by the logged in user.
| Name | Type | Req | Description |
|---|---|---|---|
| updateUserBody | object | – | – |
| username | string | yes | – |
| x-hapi-auth-state | string | – | – |
No output schema declared.
No examples provided.
uploadFile ~56
Uploads an image. - Upload image of the pet.
| Name | Type | Req | Description |
|---|---|---|---|
| additionalMetadata | string | – | – |
| petId | integer | yes | – |
| uploadFileBody | string | – | – |
| x-hapi-auth-state | string | – | – |
No output schema declared.
No examples provided.
How do I install the Petstore MCP Server server?
Petstore MCP Server is a hosted endpoint at https://petstore.run.mcp.com.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · petstore.run.mcp.com.ai
claude mcp add --transport http ai-com-mcp-petstore 'https://petstore.run.mcp.com.ai/mcp'
What is the Petstore MCP Server server?
Petstore MCP Server is listed in the public MCP registry as ai.com.mcp/petstore. Swagger Petstore API (v1.0.27) as MCP for testing and prototyping powered by the HAPI MCP server. This page covers its hosted endpoint (https://petstore.run.mcp.com.ai/mcp).
Is the Petstore MCP Server server safe to use?
Petstore MCP Server scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Petstore MCP Server server expose?
Petstore MCP Server exposes 19 tools: updatePet, addPet, findPetsByStatus, findPetsByTags, getPetById, and 14 more. Their descriptions and schemas cost roughly 901 tokens of context every time the server is loaded.
Does the Petstore MCP Server server require authentication?
No. We connected to Petstore MCP Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Petstore MCP Server server still maintained?
Petstore MCP Server has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 6 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Petstore MCP Server server?
VerifyMCP ran 5 checks on Petstore MCP Server, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Petstore MCP Server: Authorization, Schema quality, Stability, Tool coverage and 2 more. 4 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.