Your agent can call ax1om · scoring is live over MCP, free tier included.Start freeAlready have an account?

Every MCP tool has a title, and the workspace passthrough is four verb-typed tools

ImprovementMCP

Two changes from the Claude Connectors Directory review criteria, both about how a connected client presents the surface.

Every tool now publishes a title beside its readOnlyHint and destructiveHint, derived from the tool name in sentence case with the acronyms kept: validate_csv is “Validate CSV”, get_model_results is “Get model results”. A new tool inherits a title by existing.

The workspace passthrough used to be one tool that took an HTTP method as an argument, so a single call could be a safe read or a destructive delete depending on a parameter. It is now four tools: read_workspace_api (GET, and no method argument at all), create_workspace_api (POST), update_workspace_api (PUT and PATCH, marked destructive) and delete_workspace_api (DELETE, marked destructive). The same manifest decides what each may call, and a verb outside a tool’s set is refused the way any other bad method is. Scopes did not narrow: the read door still needs the same consent the others do.