ycon.cc speaks the Model Context Protocol. Point your AI assistant at one URL and it can search 300,000+ open-source icons and hand you ready-to-paste code for your framework.
https://ycon.cc/mcp
Streamable HTTP, JSON-RPC over POST. No authentication, no API key, no registration.
Pick your client and paste. Nothing else is needed.
claude mcp add --transport http ycon https://ycon.cc/mcp
{
"mcpServers": {
"ycon": {
"type": "http",
"url": "https://ycon.cc/mcp"
}
}
}
Older Claude Desktop builds cannot speak HTTP directly. Use the mcp-remote bridge instead:
{
"mcpServers": {
"ycon": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://ycon.cc/mcp"]
}
}
}
{
"mcpServers": {
"ycon": {
"url": "https://ycon.cc/mcp"
}
}
}
{
"servers": {
"ycon": {
"type": "http",
"url": "https://ycon.cc/mcp"
}
}
}
curl -sS -X POST https://ycon.cc/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Seven tools. Your assistant picks between them on its own — you just describe the icon you want.
search_iconsget_icon_codeget_icon_svgpreview_iconspreview_iconlist_icon_setslist_icon_stylesAsk your assistant something like: Find me a shopping-cart icon for my React app, outline style, MIT licence. It will:
The endpoint is public, so it is metered. The limits are set for an assistant working through a task, not for a crawler:
Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. A well-behaved client paces itself by reading them.
Over the limit you get a JSON-RPC error and a Retry-After header saying how many seconds to wait.
The icons are third-party open-source work and keep their own licences. Every answer carries the SPDX identifier and the attribution of the set the icon came from. Honouring them is up to you, not to us.
The endpoint sends no CORS headers and rejects cross-site requests, which is what makes it safe without an API key. Claude Code, Claude Desktop, Cursor and VS Code all connect from outside the browser, so this affects nobody using the configurations above.
We record anonymous usage statistics for each call — which tool was used, the search query, and the response time — to keep the service running. No API keys, no accounts, and IP addresses are anonymised.