Site

What site does

The site MCP server connects an AI client with STR Rules Check at strrulescheck.com. The available description identifies two functions: checking STR rules and submitting an enquiry. These functions cover a distinction between automated checking and requests that need a person to handle them.

The checker is intended for questions or inputs related to STR rules. The supplied material does not describe the ruleset, accepted input format, returned fields, validation behavior, or error responses, so those details should be confirmed from the service itself.

The enquiry capability is a human handoff. It should be treated as a route for sending a request to people associated with STR Rules Check, not as another automated rules-checking operation.

Tools and capabilities

The site MCP server is listed with the following capabilities:

• Checker: Checks STR rules through the STR Rules Check service.
• Enquiry: Passes an enquiry to a human rather than completing the request automatically.

No additional tools, parameters, response schemas, integrations, or supported workflows are described in the supplied listing.

Limitations and notes

The repository README is unavailable, so installation commands, transport details, environment variables, authentication requirements, client compatibility, and configuration options cannot be verified here. The listing also does not specify whether the checker operates on text, structured data, URLs, or another input type.

The phrase “enquiry” has a specific meaning in this listing: it is a human handoff. Agents and client applications should not present an enquiry as though it were an immediate automated answer or a completed rules decision. The expected response time, delivery mechanism, and confirmation behavior are not documented.

Use the site MCP server when the required operation is within the two named capabilities. For implementation planning, inspect the service documentation or test the server to determine how the checker and enquiry operations are exposed over MCP. The available material confirms the service endpoint and high-level purpose, but not the protocol setup required by a particular client.