nic-cl
by kattatzu
README.md
# NIC.cl MCP Server
A Model Context Protocol (MCP) server to query .cl domain information from [NIC Chile](https://www.nic.cl).
## Features
- **get_latest_domains**: Fetch recently registered domains (hour, day, week, month).
- **search_domains**: Search for .cl domains using patterns (exact, starts with, contains).
- **whois_domain**: Get detailed WHOIS information for a specific .cl domain.
- **get_deleted_domains**: Fetch recently deleted domains.
## Installation
### Using npx (recommended)
No installation needed. Use directly in your MCP client configuration:
1. Install global dependency
```bash
npm install -g @kattatzu/mcp-nic-cl
```
2. Configure MCP
```json
{
"mcpServers": {
"nic-cl": {
"command": "npx",
"args": ["-y", "@kattatzu/mcp-nic-cl"]
}
}
}
```
### From Source
1. Clone this repository.
2. Install dependencies:
```bash
npm install
```
3. Build the project:
```bash
npm run build
```
4. Add to your MCP client configuration:
```json
{
"mcpServers": {
"nic-cl": {
"command": "node",
"args": ["/absolute/path/to/nic-cl-mcp/dist/index.js"]
}
}
}
```
## Usage
### With MCP Inspector
You can test the server locally using the MCP Inspector:
```bash
npx @modelcontextprotocol/inspector npx @kattatzu/mcp-nic-cl
```
### In Claude Desktop or other MCP Clients
Add the following to your MCP settings configuration file:
```json
{
"mcpServers": {
"nic-cl": {
"command": "npx",
"args": ["-y", "@kattatzu/mcp-nic-cl"]
}
}
}
```
## Tools
### `get_latest_domains`
- **Arguments**:
- `time` (optional): `"hour"`, `"day"`, `"week"`, `"month"`. Default: `"hour"`.
### `search_domains`
- **Arguments**:
- `q` (required): Search pattern.
- `filter` (optional): `"exacta"`, `"comienza"`, `"contiene"`. Default: `"exacta"`.
### `whois_domain`
- **Arguments**:
- `domain` (required): The .cl domain to query.
### `get_deleted_domains`
- **Arguments**:
- `time` (optional): `"day"`, `"week"`. Default: `"day"`.
## License
ISC
TDQS
A3.8/5.0
Scored across 4 tools
Disambiguation5/5
Each tool targets a distinct operation: recent registrations, pattern search, WHOIS lookup, and recent deletions. No two tools have overlapping purposes.
Naming Consistency5/5
All tools follow a clear verb_noun pattern rooted in the .cl domain domain: get_latest_domains, search_domains, whois_domain, get_deleted_domains. The naming is predictable and easy to guess.
Tool Count5/5
Four tools is well-scoped for a .cl registry information service. Each tool covers a distinct and needed query type without redundancy.
Completeness5/5
The set offers search, WHOIS lookup, and both registration and deletion feed queries, covering the core operations expected of a NIC information service. There are no significant gaps for the stated purpose.
Maintenance
ActivityInactive
ResponsivenessNo issues