Haptic Paper
Haptic Paper is an MCP server published by hapticpaper.com, 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 Haptic Paper support the current MCP specification (2026-07-28)?
Not yet confirmed. Haptic Paper 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 Haptic Paper a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for Haptic Paper (as of 2026-08-20).
How do I connect to Haptic Paper?
Haptic Paper is available via a hosted remote endpoint at https://mcp.hapticpaper.com/mcp, the package npm:@hapticpaper/mcp-server, the official MCP Registry under com.hapticpaper/mcp, the source repository at https://github.com/hapticpaper/hh. Authentication: unknown. Transports: streamable-http.
Does Haptic Paper support MCP revision 2025-11-25?
Yes. Haptic Paper supports MCP revision 2025-11-25 (checked 2026-08-20).
Does Haptic Paper support MCP revision 2026-07-28?
No. Haptic Paper was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were Haptic Paper's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
Connect your AI to human workers. Get paid to help AI.
Which MCP spec revisions does Haptic Paper support?
Haptic Paper 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 Haptic Paper?
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 Haptic Paper
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/hapticpaper/hh returned 404 when checked.
Package (npm) as of
- Latest version
1.0.62- Last published
- First published
- Releases
- 56
- Maintainers
- 1
- Direct dependencies
- 7
- Unpacked size
- 168 KB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record for com.hapticpaper/mcp at version 1.0.62 - lists remote endpoint https://mcp.hapticpaper.com/mcp and repository https://github.com/hapticpaper/hh - accessed
- npm registry metadata for @hapticpaper/mcp-server at published version 1.0.62, 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