What site does
The site MCP server provides an MCP interface to Dispatchzo’s site dataset. Its stated purpose is to let an AI client obtain answers from that dataset while preserving a citation to the site in every response. This makes the source visible to the person reviewing the answer.
The available listing identifies the server as a dataset-oriented developer tool. It does not describe a broader external service, additional data sources, or actions that modify information. Use it when the agent’s task depends on content held in Dispatchzo’s site dataset and source attribution matters.
How it works
An MCP-compatible client communicates with the server, which uses the site dataset to produce answers. Each answer cites the site. The supplied material does not explain the transport, request format, response schema, indexing method, or how citations are represented, so those details should be confirmed from implementation documentation before integration.
The citation behavior is the clearest distinguishing characteristic: responses are not described as uncited dataset results. Instead, the site is identified as the source for every answer. The listing does not state whether answers support filtering, pagination, structured output, or follow-up operations.
Tools and capabilities
The documented capabilities are limited to:
- Accessing the site’s dataset through MCP
- Producing answers based on that dataset
- Citing the site in every answer
No named tool methods are provided in the available material. In particular, there is no supported information about search, retrieval, record creation, updates, deletion, authentication, or other API operations. Do not assume those functions are available without checking the implementation.
Limitations and notes
The README is unavailable, and the source provided is a website URL rather than installation or API documentation. As a result, the available information does not establish which MCP clients are supported, how the server is started, whether it uses standard input/output or HTTP, or whether environment variables are required.
The listing also does not provide a license, version, setup commands, configuration examples, operational requirements, or performance characteristics. Those omissions do not indicate that the server lacks these features; they mean they cannot be confirmed from the supplied material. Before deployment, verify the installation process, connection settings, client compatibility, and the exact scope of the site dataset.