Developer · Remote MCP server
Petstore MCP Server
Swagger Petstore API (v1.0.27) as MCP for testing and prototyping powered by the HAPI MCP server.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.com.mcp/petstore- Version
- 0.6.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-01-07
- Updated
- 2026-01-07
- Publisher
- ai.com.mcp · 7 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via the domain mcp.com.ai or a parent domain of it · how
- Listed under
- OpenAPI MCP servers
- Website
- run.mcp.com.ai
- Repository
- github.com/la-rebelion/hapimcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://petstore.run.mcp.com.ai/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- HTTP 200 without a JSON-RPC answer
- Checked on
- 2026-10-05
How to connect Petstore MCP Server
Petstore MCP Server is a remote MCP server: there is nothing to install. Its endpoint is https://petstore.run.mcp.com.ai/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from ai.com.mcp
| Server | Runs |
|---|---|
| Agent Skills Search ServerSearch and discover Agent Skills from the skills.sh registry. Powered by HAPI MCP server. | Remote · HTTPLive check: ✗ no handshake |
| Contabo (VPS) MCP ServerContabo API (v1.0.0) as MCP tools for cloud provisioning, and management. Powered by HAPI MCP server. | Remote · HTTPLive check: ✗ no handshake |
| HAPI MCP ServerHAPI MCP server: Dynamically exposes OpenAPI REST APIs as MCP tools for AI assistants. | Remote & Local · HTTP |
| HAPI Strava MCP ServerStrava MCP tools for AI: athletes, activities, segments, clubs, routes. Powered by HAPI MCP server. | Remote · HTTPLive check: ✓ handshake |
| LinkedIn MCP ServerLinkedIn API as MCP tools to retrieve profile data and publish content. Powered by HAPI MCP. | Remote · HTTPLive check: ✓ handshake |
| OpenAI Tools MCP ServerFocused MCP server for OpenAI image/audio generation (v2.0.0). Wraps endpoints via HAPI CLI. | Remote · HTTPLive check: ✗ no handshake |
More developer servers
| Server | Runs |
|---|---|
| Petal Components MCPPhoenix LiveView component schemas from petal_components, exposed to AI coding assistants. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| petro-mcpMCP server for petroleum engineering: LAS logs, decline curves, PVT, petrophysics, volumetrics. | Local · stdio |
| petromcpLocal-first MCP server: read LAS well logs and DLIS files from your own disk. | Local · stdio |
| PetsonalityAn MBTI-powered terminal pet companion for Claude Code and OpenClaw. | Local · stdio |
| Pg AiguideComprehensive PostgreSQL documentation and best practices, including ecosystem tools. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Pg Migration Lock LintNames every statement in a Rails, Django or raw SQL migration that takes a table-blocking Postgres l. | Local · stdio |
| Pg Readonly MCPA read-only Postgres MCP server that parses SQL rather than pattern-matching it. | Local · stdio |
| PGAuditorHosted MCP server for PostgreSQL diagnostics: slow queries, missing indexes, connection pressure. | Remote · HTTPLive check: ✗ no handshake |