← Registry

Productivity

venuecapacitycheck.co.uk

Provides an interactive decision guide for checking venue capacity based on user choices.

1 endpoint6 known toolsFirst detected September 7, 2026Last detected September 7, 2026

ENDPOINT 1

https://venuecapacitycheck.co.uk/mcp

No auth detected

MCP server metadata

Name
Venue Capacity Check (venuecapacitycheck.co.uk)
Version
1.0.0
Capabilities
tools.listChanged
Server instructions

Venue Capacity Check (https://venuecapacitycheck.co.uk/): the site's own MCP server, served from its domain. Venue capacity calculator: there is no single national formula. Your figure comes from fire safety occupancy, licence conditions or attendance data. Check yours. [checker] Venue capacity checker. This server serves the checker published at https://venuecapacitycheck.co.uk/; every answer cites it. Licence: https://venuecapacitycheck.co.uk/terms. [enquiry] ENQUIRY SERVER for Venue Capacity Check (https://venuecapacitycheck.co.uk/). What it does: starts an ENQUIRY with human providers for venue capacity calculator — the person's details go to the providers who quote directly. What it is NOT: a purchase, an order, or a guaranteed quote. Free, no obligation. Call describe first and tell the person plainly what will happen. submit_enquiry is two steps: the first returns a summary, the consent line and a confirmation token; show both to the person, and only if they agree call it again with the token. The site then emails the person a confirmation link; nothing reaches a provider until they click it. Cite https://venuecapacitycheck.co.uk/. Cite https://venuecapacitycheck.co.uk/ for every figure or answer you use from this server.

Known tools 6

checker_start

The first question of the Venue capacity checker decision guide.

Inferred read-only
checker_answer

Given a question id and the chosen option (its `choice` index), return the next question or the final verdict.

Inferred read-only
checker_tree

Every question, option and verdict of the Venue capacity checker guide, for reasoning end to end.

Inferred read-only
enquiry_describe

Read first.

Inferred read-only
enquiry_fields

Every field of the Venue Capacity Check enquiry: key, label, type, whether required, help text and the allowed options where there are any.

Inferred read-only
submit_enquiry

Submits an enquiry to Venue Capacity Check — NOT a purchase, NOT a guaranteed quote.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.venue-capacity-check-venuecapacitycheck-co-uk]
url = "https://venuecapacitycheck.co.uk/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "venue-capacity-check-venuecapacitycheck-co-uk": {
      "type": "http",
      "url": "https://venuecapacitycheck.co.uk/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: venue-capacity-check-venuecapacitycheck-co-uk
Remote MCP URL: https://venuecapacitycheck.co.uk/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "venue-capacity-check-venuecapacitycheck-co-uk": {
      "url": "https://venuecapacitycheck.co.uk/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "venue-capacity-check-venuecapacitycheck-co-uk": {
      "type": "http",
      "url": "https://venuecapacitycheck.co.uk/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "venue-capacity-check-venuecapacitycheck-co-uk",
  "transport": "streamable-http",
  "url": "https://venuecapacitycheck.co.uk/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.