uk-farm-safety
Server Details
UK farm health and safety — HSE guidance, machinery, COSHH, children on farms
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- Ansvar-Systems/uk-farm-safety-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.6/5 across 10 of 10 tools scored.
Each tool targets a distinct farm safety domain or utility function with no overlapping scope. The get_* tools cover discrete regulatory areas (COSHH, CHAW, RIDDOR) and hazard categories (machinery, livestock), while utility tools handle search, metadata, and data provenance without ambiguity.
Tools follow a consistent verb_noun snake_case pattern (get_coshh_requirements, search_safety_guidance) with clear action descriptors. The only deviation is 'about', which breaks the pattern but follows common convention for server metadata endpoints.
Ten tools strike an appropriate balance for a specialized UK farm safety domain, covering major hazard categories (machinery, livestock, chemicals), specific regulations (CHAW, COSHH, RIDDOR), and necessary utility functions (search, sources, freshness). The scope is focused without being fragmented or overwhelming.
The toolset covers high-risk farm activities and key regulatory frameworks but omits specific guidance for other major UK farm hazards like working at height, slurry gas safety, or electrical safety. However, the search_safety_guidance tool likely provides access to this content, and the risk assessment template offers a generic framework applicable to all activities.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!