mcpbeat Sign in

Site MCP Server

by co-epossystemretail Your server? Claim it
answering

Site is answering right now. Last checked 9 min ago. It exposes 3 tools.

EPOS system for retail: the site's own MCP server — enquiry (enquiry = a human handoff, not a...

Uptime history 41 days of history · worst day 99%
41 days agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
885 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 3

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 12 November 2026. No other catalogue keeps this.

12 Nov 2 tool descriptions were rewritten3 times that day enquiry_describe, submit_enquiry
and 1 more, back to 12 November 2026

Nothing serious here today

Today is the operative word: we check Site every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add site --transport http https://epossystemretail.co.uk/mcp
Settings → Connectors → Add custom connector, then paste this address
https://epossystemretail.co.uk/mcp
~/.codex/config.toml
[mcp_servers.site]
url = "https://epossystemretail.co.uk/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "site": {
      "url": "https://epossystemretail.co.uk/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "site": {
      "type": "http",
      "url": "https://epossystemretail.co.uk/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

enquiry
enquiry_describe
Read first. States plainly what submit_enquiry does on EPOS system for retail: it starts an enquiry with EPOS system for retail, whose team reads it and replies directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the details, the consent wording, and how the person confirms.
enquiry_fields
Every field of the EPOS system for retail enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.
submit
submit_enquiry
Submits an enquiry to EPOS system for retail: NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token; show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before the EPOS system for retail team sees it. Consent means the person has read and agreed to: "Happy to be contacted about this enquiry by the company that runs this site."

Endpoints

URLTransportStateLatencyChecked
https://epossystemretail.co.uk/mcp streamable-http answering 713 ms 9 min ago

Alternatives to Site

same job, measured the same way
Site
by co-seoplumbers

SEO for plumbers: the site's own MCP server — enquiry (enquiry = a human handoff, not a...

3 tools answering
Site
by seodentists

SEO for dentists: the site's own MCP server — enquiry (enquiry = a human handoff, not a...

3 tools answering
Site
by seoaccountants

SEO for accountants: the site's own MCP server — enquiry (enquiry = a human handoff, not a...

3 tools answering
Site
by co-ppclawfirms

PPC for law firms: the site's own MCP server — enquiry (enquiry = a human handoff, not a...

3 tools answering
Site
by co-copywritingseo

Copywriting for SEO: the site's own MCP server — enquiry (enquiry = a human handoff, not a...

3 tools answering
Site
by co-seodealerships

SEO for dealerships: the site's own MCP server — enquiry (enquiry = a human handoff, not a...

3 tools answering
Site
by co-localseolawfirm

Local SEO for law firm: the site's own MCP server — enquiry (enquiry = a human handoff, not a...

3 tools answering
Site
by co-motorrewindcost

Motor Rewind Cost: the site's own MCP server — enquiry (enquiry = a human handoff, not a...

3 tools answering

Site — questions

Answers built from our own checks of this server.

What can Site do?
It exposes 3 tools, read directly from the server on our last check. Among them: enquiry_describe, enquiry_fields, submit_enquiry. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Site working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 885 ms. The bar chart above shows every period we have measured.
How do I connect Site?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Site need an API key?
No. Site completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Site?
It answers our handshake in 885 ms on average, which is faster than 10% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.