INDIVIDUAL MCP TOOL
search_tools
Search Iduno's catalog of micro-tools that run in the user's browser when opened and can't send data to third parties (CSP).
LIVE ENDPOINT
https://iduno.io/mcp
Connect to this endpoint to inspect the live schema for search_tools and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Potential side effects detected · medium confidence · heuristic, not a guarantee.
- A tool name or description contains a write-action term.
- A tool name or description suggests sending messages.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.iduno]
url = "https://iduno.io/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"iduno": {
"type": "http",
"url": "https://iduno.io/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: iduno
Remote MCP URL: https://iduno.io/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"iduno": {
"url": "https://iduno.io/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"iduno": {
"type": "http",
"url": "https://iduno.io/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "iduno",
"transport": "streamable-http",
"url": "https://iduno.io/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
get_tool— Fetch one Iduno tool by its id (UUID) or slug.run_tool— Get a ready-to-run link for an Iduno tool with the given inputs prefilled.get_capabilities— Return Iduno's tool-authoring contract: the exact sandbox rules, the required useToolBridge input/output contract, and the FULL list of allowed packages with their canonical import lines.check_tool_build— Check the status of one of the user's own tools (owner-scoped).review_tool— Fetch a tool's spec + build status so you (the user's AI) can review it against the requirements and propose concrete improvements.list_my_tools— List the user's OWN tools (newest first): requestId, name, visibility (private/org/named/shared), build status, created time and links.list_shares— Show who can see one of the user's tools: visibility, whether it has a public web page, whether it is shared with the company, how many client organisations it is assigned to, and its invitations (recipient addresses are masked, e.g.rename_tool— Give one of the user's PRIVATE tools a new name.