pepita
pepita is an MCP server published by mcp.pepita.dev, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.
Does pepita support the current MCP specification (2026-07-28)?
Not yet confirmed. pepita is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
Is pepita a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for pepita (as of 2026-08-20).
How do I connect to pepita?
pepita is available via a hosted remote endpoint at https://mcp.pepita.dev/mcp, the package npm:@pepitahq/mcp, the official MCP Registry under dev.pepita.mcp/mcp, the source repository at https://github.com/pepitahq/pepita-mcp. Authentication: oauth. Transports: streamable-http.
Does pepita support MCP revision 2025-11-25?
Yes. pepita supports MCP revision 2025-11-25 (checked 2026-08-20).
Does pepita support MCP revision 2026-07-28?
No. pepita was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were pepita's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
Read, edit, publish, and preview your pepita websites from Claude.
Which MCP spec revisions does pepita support?
pepita has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source | |
| MCP 2026-07-28 | Not supported | Source |
How widely adopted is pepita?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
Repository and package signals for pepita
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
The repository this server declares no longer resolves. That is a measurement, not
a failed lookup: https://github.com/pepitahq/pepita-mcp returned 404 when checked.
Package (npm) as of
- Latest version
0.22.0- Last published
- First published
- Releases
- 29
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 2
- Unpacked size
- 148 KB
- Registry signature
- Signed
- Build provenance
- No attestation
- Deprecated
- Yes
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record for dev.pepita.mcp/mcp at version 0.14.0 - lists remote endpoint https://mcp.pepita.dev/mcp and repository https://github.com/pepitahq/pepita-mcp - accessed
- Endpoint probe of https://mcp.pepita.dev/mcp - authorization required (HTTP 401, Bearer realm="OAuth", resource_metadata="https://mcp.pepita.); capability set not observable without credentials - accessed
- npm registry metadata for @pepitahq/mcp at published version 0.22.0, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed