Naver data API
4 endpoints for Naver: search, suggestions, news search, blog. One API key, one JSON schema, as MCP tools or REST.
Endpoints
Call any of them over MCP with call_endpoint and its path, or over REST.
| Endpoint | Returns | Credits | Cache |
|---|---|---|---|
| searchGET /v1/naver/search | Naver web results for a keyword, first page only. | 1 | 2 min |
| suggestionsGET /v1/naver/suggestions | Autocomplete suggestions from Naver. | 1 | 2 min |
| news/searchGET /v1/naver/news/search | News articles from the Naver news vertical, with headline, press and summary. | 1 | 2 min |
| blogGET /v1/naver/blog | Blog posts matching a query from Naver, newest first. | 1 | 2 min |
Connect your agent over MCP
Remote MCP server: https://data.openkrill.app/mcp with your key in the x-api-key header.
claude mcp add --transport http krilldata \
https://data.openkrill.app/mcp \
--header "x-api-key: YOUR_API_KEY"{
"mcpServers": {
"krilldata": {
"url": "https://data.openkrill.app/mcp",
"headers": {
"x-api-key": "YOUR_API_KEY"
}
}
}
}{
"mcpServers": {
"krilldata": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://data.openkrill.app/mcp",
"--header",
"x-api-key:${API_KEY}"
],
"env": {
"API_KEY": "YOUR_API_KEY"
}
}
}
}