Sherlock Domains MCP
# sherlock-mcp MCP server
Shelock Domains MCP server to buy & manage domains
## Components
### Resources
The server implements a simple note storage system with:
- Custom note:// URI scheme for accessing individual notes
- Each note resource has a name, description and text/plain mimetype
### Prompts
The server provides a single prompt:
- summarize-notes: Creates summaries of all stored notes
- Optional "style" argument to control detail level (brief/detailed)
- Generates prompt combining all current notes with style preference
### Tools
The server implements one tool:
- add-note: Adds a new note to the server
- Takes "name" and "content" as required string arguments
- Updates server state and notifies clients of resource changes
## Configuration
[TODO: Add configuration details specific to your implementation]
## Quickstart
### Install
#### Claude Desktop
On MacOS: `~/Library/Application\ Support/Claude/claude_desktop_config.json`
On Windows: `%APPDATA%/Claude/claude_desktop_config.json`
<details>
<summary>Development/Unpublished Servers Configuration</summary>
```
"mcpServers": {
"sherlock-mcp": {
"command": "uv",
"args": [
"--directory",
"/Users/pengren/go/github.com/Fewsats/sherlock-mcp",
"run",
"sherlock-mcp"
]
}
}
```
</details>
<details>
<summary>Published Servers Configuration</summary>
```
"mcpServers": {
"sherlock-mcp": {
"command": "uvx",
"args": [
"sherlock-mcp"
]
}
}
```
</details>
## Development
### Building and Publishing
To prepare the package for distribution:
1. Sync dependencies and update lockfile:
```bash
uv sync
```
2. Build package distributions:
```bash
uv build
```
This will create source and wheel distributions in the `dist/` directory.
3. Publish to PyPI:
```bash
uv publish
```
Note: You'll need to set PyPI credentials via environment variables or command flags:
- Token: `--token` or `UV_PUBLISH_TOKEN`
- Or username/password: `--username`/`UV_PUBLISH_USERNAME` and `--password`/`UV_PUBLISH_PASSWORD`
### Debugging
Since MCP servers run over stdio, debugging can be challenging. For the best debugging
experience, we strongly recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector).
You can launch the MCP Inspector via [`npm`](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm) with this command:
```bash
npx @modelcontextprotocol/inspector uv --directory /Users/pengren/go/github.com/Fewsats/sherlock-mcp run sherlock-mcp
```
Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose with no ambiguity. For example, 'create_dns', 'update_dns', and 'delete_dns' handle different DNS operations, while 'domains' lists domains and 'search' checks availability. The 'claim_account' tool is separate for account management, and contact information tools are distinct from domain operations.
Most tools follow a consistent verb_noun or noun pattern (e.g., 'create_dns', 'delete_dns', 'dns_records', 'domains', 'search'). Minor deviations include 'get_contact_information' and 'get_purchase_offers' using 'get_' prefix, and 'set_contact_information' using 'set_', but these are still readable and logical.
With 10 tools, the count is well-scoped for domain management. It covers core workflows like domain search, purchase, DNS management, and account/contact setup without being overwhelming. Each tool serves a specific, necessary function in the domain lifecycle.
The tool set provides complete coverage for domain management. It includes domain search, purchase offers, DNS CRUD operations (create, read, update, delete), domain listing, and account/contact setup. There are no obvious gaps; agents can handle the full lifecycle from search to DNS configuration.