Composition axis
Composition MCP servers
Combines other servers' capabilities to reach an outcome. Orchestrates data and domain servers into a finished decision, not just a data point.
Example · ValuationMCP
A Composition server exists to produce a finished answer, not a data point.
Most servers hand back a fact. A Composition server takes facts from elsewhere, runs something deterministic over them, and returns a conclusion you could defend to a third party. ValuationMCP is the one in this directory. It takes a practice's filed profile, blends seven valuation methods over it, and returns a value with the inputs and the method weights visible.
The part worth being precise about is what "combines other servers" means. There is no pipe. A Composition server does not reach out and call ADVmcp on its own. You connect both in your client, and the agent carries the filed facts from one into the other inside a single conversation. The composition happens in the conversation, not in the infrastructure.
That is also why the role is not derivable from a server's category. ValuationMCP sits under Advisor and Firm Intelligence, the same category as several Domain servers. What separates it is that it consumes other servers' output by design.
Composition is the rarest role here, and the one the rest of this taxonomy exists to make legible.
Composition servers in the directory
1 server in this directory play this role