# site [Health: Active]

**Category:** 🔬 Research  
**Repository:** https://caspchecklist.com  
**npm Downloads (last month):** 9171  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/site-37

## Description
CASP Checklist: the site's own MCP server — checker, enquiry (enquiry = a human handoff, not a...

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What the site MCP server does

The site MCP server connects an MCP-compatible agent to CASP Checklist at caspchecklist.com. The available description identifies two capabilities: checker and enquiry. Checker is the site’s checking function. Enquiry represents a handoff to a human, so it should be treated as a route for assistance or follow-up rather than as another automated tool result.

This server is listed in the 🔬 Research category. It may fit workflows where an agent needs to use CASP Checklist as part of a research process and distinguish between an automated check and a request that requires human attention. The supplied material does not define the checklist content, the inputs accepted by checker, or the information required for an enquiry.

## Tools and capabilities

The documented capabilities are:

- **Checker:** Performs the checking function associated with CASP Checklist. The available material does not specify its parameters, return format, or validation rules.
- **Enquiry:** Starts or supports an enquiry that is handed to a human. It is explicitly not described as an automated answer mechanism.

The site MCP server’s listing does not provide a fuller tool schema. Developers should therefore inspect the server’s MCP declarations or the source documentation before building prompts, validation, retries, or application logic around either capability.

## Limitations and notes

The README is unavailable for this listing. As a result, the following details cannot be confirmed from the supplied material: installation commands, transport type, authentication requirements, environment variables, client-specific setup, tool argument schemas, response formats, error behavior, rate limits, and license.

The name “enquiry” should not be interpreted as a general-purpose question-answering tool. The supplied description defines it as a human handoff. Applications using the site MCP server should make that distinction clear to users and should not assume that an enquiry returns an immediate automated result.

No compatible client is named in the available material. Client compatibility should be verified from the server’s implementation or its later documentation before deployment. The same applies to whether the server is intended for local use, a hosted connection, or a particular MCP transport.

_Full upstream README: https://allmcps.com/mcp/site-37/readme_