Tool Router

Distributed Systems · tools.distributed.systems

We maintain a tool router here. It is a registry plus a meta-router: backend servers register their tools once, and enabled tools on healthy backends become discoverable and executable through an authenticated endpoint.

Account portal API documentation Connect an agent

Operator access is live. Customer access across products is still being restored. Opening the account portal does not yet grant access to the shared operator tools.

This service predates MCP. The protocol layer was added later as a binding; the registry and routing core were built first and remain independent of any single protocol.

Connect an agent

MCP endpoint: https://tools.distributed.systems/mcp. Use an existing operator bearer token in your client's authorization header. Unauthenticated requests return 401.

To discover the currently available operations through the REST API:

curl --fail-with-body \
  -H "Authorization: Bearer $DSCO_TOOLS_TOKEN" \
  'https://tools.distributed.systems/api/v1/tools/?available_only=true&limit=100'

Execute a read-only operation using its backend-qualified name:

curl --fail-with-body \
  -H "Authorization: Bearer $DSCO_TOOLS_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"tool":"distributed-unit:unit_list","arguments":{}}' \
  https://tools.distributed.systems/api/v1/tools/execute

Search is available at /api/v1/tools/search?available_only=true. Registration requires operator authorization; catalog membership alone does not establish that a backend is ready to execute.

Monthly plans

Plan	USD monthly	Availability
Starter	$20 / month	Request access
Pro	$100 / month	Request access
Business	$500 / month	Request access

Prices are in USD. Request access; no automatic checkout or charge. Plan inclusions, private hosting capacity and any additional usage costs are confirmed before activation. Existing subscriptions are not changed.

Plan details · Private integration hosting

Private hosting starts with an account-scoped request and operator review. A request does not provision infrastructure or publish your tools in the shared catalog.

Live status

Available operations	2,559
Qualified backends	13
Retained catalog entries	2,559
Pending operations	0

These counts describe backend readiness. Access is also checked for each account.

Endpoints

/health — liveness and registry counts
/docs — OpenAPI documentation
/api/v1/status — detailed backend status