uk.co.dilapidationscost/site
REMOTE · DILAPIDATIONSCOST.CO.UK · SCANNED SEP 20
Dilapidations Cost: the site's own MCP server — enquiry (enquiry = a human handoff, not a...
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 592 tokens (~197/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the uk.co.dilapidationscost/site MCP server?
uk.co.dilapidationscost/site is a hosted endpoint at https://dilapidationscost.co.uk/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · dilapidationscost.co.uk
claude mcp add --transport http uk-co-dilapidationscost-site 'https://dilapidationscost.co.uk/mcp'
{
"mcpServers": {
"uk-co-dilapidationscost-site": {
"url": "https://dilapidationscost.co.uk/mcp"
}
}
} {
"servers": {
"uk-co-dilapidationscost-site": {
"type": "http",
"url": "https://dilapidationscost.co.uk/mcp"
}
}
} [mcp_servers.uk-co-dilapidationscost-site] url = "https://dilapidationscost.co.uk/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"uk-co-dilapidationscost-site": {
"type": "remote",
"url": "https://dilapidationscost.co.uk/mcp",
"enabled": true
}
}
} openclaw mcp add uk-co-dilapidationscost-site --url 'https://dilapidationscost.co.uk/mcp' --transport streamable-http
mcp_servers:
uk-co-dilapidationscost-site:
url: "https://dilapidationscost.co.uk/mcp" {
"McpServers": {
"uk-co-dilapidationscost-site": {
"Transport": "http",
"Url": "https://dilapidationscost.co.uk/mcp"
}
}
} assistant mcp add uk-co-dilapidationscost-site -t streamable-http -u 'https://dilapidationscost.co.uk/mcp'
{
"mcpServers": {
"uk-co-dilapidationscost-site": {
"type": "http",
"url": "https://dilapidationscost.co.uk/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +46
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.40 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 14 Sept 26 −44
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.23 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +43
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.20 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 10 Sept 26 +5
- HTTPS: fail → pass ▲ security
- 7 Sept 26 −41
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 6 Sept 26 59
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://dilapidationscost.co.uk/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dilapidationscost.co.uk | CN=WE1,O=Google Trust Services,C=US | 14 Aug 2026 | 12 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 555c3fbbf10fb213133f6dc551967258 |
| SANs: dilapidationscost.co.uk, *.dilapidationscost.co.uk | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of dilapidationscost.co.uk. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| uk. | present | 43876 | 8 | Verified |
| co.uk. | present | 11810 | 8 | Verified |
| dilapidationscost.co.uk. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dilapidationscost.co.uk/mcp | Verified | 200 | |
| http (plaintext) | http://dilapidationscost.co.uk/mcp | HTTPS enforced | 301 | https://dilapidationscost.co.uk/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
enquiry_describe What you get: an ENQUIRY with a human (not a purchase, not a guaranteed quote) ~70
Read first. States plainly what submit_enquiry does on Dilapidations Cost: 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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
enquiry_fields The questions the enquiry asks ~49
Every field of the Dilapidations Cost 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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
submit_enquiry Submit an ENQUIRY to human providers (two steps; not a purchase) ~228
Submits an enquiry to Dilapidations Cost — 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 dilapidations surveyors, who'll send me fee proposals directly."
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | yes | the person's answers, keyed by field key |
| confirmation | string | – | the confirmation token from step 1, after the person has approved the summary |
| consent | boolean | yes | true only when the person has agreed to: Happy for my details to go to dilapidations surveyors, who'll send me fee proposals directly. |
No output schema declared.
No examples provided.
What is the uk.co.dilapidationscost/site MCP server?
uk.co.dilapidationscost/site is an MCP server listed in the public MCP registry as uk.co.dilapidationscost/site. Dilapidations Cost: the site's own MCP server, enquiry (enquiry = a human handoff, not a... This page covers its hosted endpoint (https://dilapidationscost.co.uk/mcp).
Is the uk.co.dilapidationscost/site MCP server safe to use?
uk.co.dilapidationscost/site scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the uk.co.dilapidationscost/site MCP server expose?
uk.co.dilapidationscost/site exposes 3 tools: enquiry_describe, enquiry_fields, submit_enquiry. Their descriptions and schemas cost roughly 347 tokens of context every time the server is loaded.
Does the uk.co.dilapidationscost/site MCP server require authentication?
No. We connected to uk.co.dilapidationscost/site without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the uk.co.dilapidationscost/site MCP server still maintained?
uk.co.dilapidationscost/site is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.