Vivesca

The source here is lean on specifics, but the "opinionated" framing and Pydantic schemas suggest this is a structured, strongly-typed MCP server spanning seven distinct domains. You'd reach for this if you want predictable output formats and appreciate batteries-included design decisions over configuration sprawl. The "built to evolve" positioning implies the domains will expand over time, though without documentation on what those seven domains actually cover (data, finance, web scraping?), you're evaluating based on architecture rather than immediate capability. If the repo docs flesh out those domains, this could be a solid starting point for multi-domain workflows where type safety matters.