list_tools_catalogLABSCO SUMMARY
A hundred utilities that cost three tool definitions.
This is the right shape for a large collection: the catalogue is data the model reads on demand rather than schema it carries every turn, so adding utilities does not enlarge the context every conversation pays for. The trade is one extra round trip before the first call.
What it is
A hosted catalogue of small developer utilities behind a discover-then-execute pipeline. Rather than putting every utility in the tool list, it exposes three: browse the catalogue, read one utility's contract, run it. The definitions riding along on every turn stay at three no matter how many utilities sit behind them.
What you get
- The whole catalogue listed, filterable by category, by tier or by exact slug, with each entry carrying its description, input type, keywords, rate limits and endpoint —
list_tools_catalog - One utility's full contract read before you call it: required fields, request schema and the from/to/value fields conversion tools use —
get_tool_details - Any utility executed three ways — direct text input, a from/to/value conversion, or a structured options object —
execute_tool - Categories spanning encode-decode, colour, crypto, formatter, converter, text, image, math, network and date
- Auto-discovery through
.well-known/mcp.json, so an MCP-aware client can find the server without being configured
Requirements
A client that speaks Streamable HTTP, pointed at https://d3v.tools/mcp/tools. No authentication. Rate limits run 10 requests a minute anonymous, 30 registered, 1000+ on premium, and each catalogue entry carries the tier it belongs to. Some utilities run client-side: for those, execute_tool returns your input with result set to null and a note to do the processing yourself, so check the type field before relying on a server-side answer.
Setup effort
Paste a URL — add the endpoint to your client
USE CASES
01
Decoding something you were handed
A Base64 blob, a JWT, a URL-escaped string. Find the matching utility in the encode-decode category, check what it wants, and run it — without leaving the conversation for a web page that wants your data pasted into it.
02
Converting units or colours mid-task
Conversion utilities take a value with a source and a destination rather than a single input. Celsius to Fahrenheit, hex to RGB, one base to another — the contract tells you which fields the utility expects before you call it.
03
Getting the call right the first time
Read the contract before executing: required fields, input type, and whether the utility is a direct-input, conversion or options-shaped call. One lookup saves a validation error and a retry.
04
Finding out what is even available
Filter the catalogue by category or by tier and read what exists. This is also how you tell in advance whether a utility is free or premium, and what its per-minute limit is.
3 tools
Listed in project docs. Your client may show a different list.
get_tool_detailsexecute_toolBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
A client that can reach a remote MCP server over HTTP
Where it runs
All 3 documented clients connect to a hosted endpoint.
INSTALLATION
Connect your client
Add the endpoint to your client.
Server setup
ENDPOINT URL
https://d3v.tools/mcp/toolsMCP Clients
OpenCode
OPENCODE · JSON
{
"mcp": {
"d3vtools": {
"type": "remote",
"url": "https://d3v.tools/mcp/tools",
"enabled": true
}
}
}Cursor
CURSOR · JSON
{
"mcpServers": {
"d3vtools": {
"url": "https://d3v.tools/mcp/tools"
}
}
}VS Code
VS CODE · JSON
{
"servers": {
"d3vtools": {
"type": "http",
"url": "https://d3v.tools/mcp/tools"
}
}
}
