Site MCP Server

by co-pilingcosts Your server? Claim it

answering

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

Piling Costs: the site's own MCP server — enquiry (enquiry = a human handoff, not a purchase);...

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 4 days of history

4 days agonow

100.0%

Uptime 24h

93 of 93 checks

Tools

read from the server

523 ms

Response time

average over 24h

open, no key

Access

streamable-http

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add site --transport http https://pilingcosts.co.uk/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "site": {
      "url": "https://pilingcosts.co.uk/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.site]
url = "https://pilingcosts.co.uk/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "site": {
      "url": "https://pilingcosts.co.uk/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "site": {
      "url": "https://pilingcosts.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 Piling Costs: it starts an enquiry with human providers who quote 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 Piling Costs 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 Piling Costs — 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 any provider sees it. Consent means the person has read and agreed to: "Happy for my details to go to relevant local piling contractors, who'll quote me directly."

Endpoints

URL	Transport	State	Latency	Checked
https://pilingcosts.co.uk/mcp	streamable-http	answering	825 ms	1 min ago

Alternatives to Site

same job, measured the same way

Site

by co-probatecosts

Probate Costs: the site's own MCP server — enquiry (enquiry = a human handoff, not a purchase);...

3 tools answering

Site

by co-shopsigncost

Shop Sign Cost: the site's own MCP server — enquiry (enquiry = a human handoff, not a purchase);...

3 tools answering

Site

by co-adrcourses

ADR Courses: the site's own MCP server — enquiry (enquiry = a human handoff, not a purchase);...

3 tools answering

Site

by co-threephasecost

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

3 tools answering

Site

by co-bngquotes

BNG Quotes: the site's own MCP server — enquiry (enquiry = a human handoff, not a purchase);...

3 tools answering

Site

by co-tm44quote

TM44 Quote: the site's own MCP server — enquiry (enquiry = a human handoff, not a purchase);...

3 tools answering

Site

by co-liveryprices

Livery Prices: the site's own MCP server — enquiry (enquiry = a human handoff, not a purchase);...

3 tools answering

Site

by co-drainprices

Drain Prices: the site's own MCP server — enquiry (enquiry = a human handoff, not a purchase);...

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 93 of 93 checks got a reply (100.0%), average response time 523 ms. The bar chart above shows every period we have measured.

Is Site still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

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 with the file path 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 523 ms on average, which is faster than 30% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.