MCP Tool Catalog
Every tool three.ws publishes over the Model Context Protocol, in one place:
what it does, which server hosts it, what it costs, and whether an AI client can run it without asking you first.
This page is generated from the source of every tool, so it cannot drift from what the servers actually serve.
The same data is machine-readable at /mcp-catalog.json.
Let your assistant run the safe ones by itself
Your AI client decides whether to run a tool without asking you by trusting its read-only label. Everywhere else that label is the tool author's own word for it. Here it is checked against the code on every build, so it is worth automating on. Pick how much you want automated and paste the result into your client.
Loading the policy…Always current: /api/mcp-policy returns this same document, so a client can refetch it instead of pinning a copy that goes stale as tools are added.