WatchBase
WatchBase MCP Server provides structured access to the WatchBase Data Feed API, enabling AI assistants to query comprehensive watch metadata including brands, collections, reference numbers, and technical details. Developed by watchdealer-pavel, this TypeScript implementation exposes six specialized tools that map directly to WatchBase API endpoints, handling authentication and error management behind the scenes. The server requires a WatchBase API key passed as an environment variable and returns standardized JSON responses, making it particularly valuable for watch enthusiasts, collectors, or retailers who need to access detailed horological information through AI assistants.
Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-30.
Scan details: Circle-IR · 2026-09-30 · Appeal
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- security
- Source
- PulseMCP
- Author type
- human
- Last scanned
- 2026-09-30
- Updated
- 2026-09-30
Use via MCP
Resolve WatchBase from your agent
Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.
One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp --scope user for --scope project to commit it to .mcp.json.