Ironclad Verified
REMOTE · IRONCLADVERIFIED.COM · SCANNED AUG 3
Hire evidence-verified home-service contractors. Confirmed-job reviews only; rank is never buyable.
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 →
Endpoint Security63
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1097 tokens (~156/item across 7 items; 7 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 Management27
- Stability observed for 8 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · ironcladverified.com
claude mcp add --transport http com-ironcladverified-verified https://ironcladverified.com/mcp
[mcp_servers.com-ironcladverified-verified] url = "https://ironcladverified.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-ironcladverified-verified": {
"type": "remote",
"url": "https://ironcladverified.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-ironcladverified-verified --url https://ironcladverified.com/mcp --transport streamable-http
mcp_servers:
com-ironcladverified-verified:
url: "https://ironcladverified.com/mcp" {
"mcpServers": {
"com-ironcladverified-verified": {
"type": "http",
"url": "https://ironcladverified.com/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.
- 2 Aug 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.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 65
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 3 Aug 2026 · Probed https://ironcladverified.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ironcladverified.com | CN=YE2,O=Let's Encrypt,C=US | 21 Jun 2026 | 19 Sept 2026 | ECDSA 256 | ECDSA-SHA384 | 5bef919111698b9e37c136fe155bd1f4464 |
| SANs: *.ironcladverified.com, ironcladverified.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC insecure
Validation of ironcladverified.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ironcladverified.com. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| content-security-policy | default-src 'none'; style-src 'unsafe-inline'; font-src 'self'; img-src 'self' data:; form-action 'self'; base-uri 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ironcladverified.com/mcp | Verified | 200 | |
| http (plaintext) | http://ironcladverified.com/mcp | HTTPS enforced | 301 | https://ironcladverified.com/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.
check_request Check what happened to a request ~88
Reads a request's status by its withdrawRef: sent / seen / contacted / booked / completed / withdrawn / unanswered, with the contractor's name, their ack (accepted/declined), whether a reroute is currently possible, and — after a move — the successor request's ref. No personal data is returned.
| Name | Type | Req | Description |
|---|---|---|---|
| withdrawRef | string | yes | The withdrawRef returned by request_contractor. |
No output schema declared.
No examples provided.
complete_job The homeowner confirms the job is done ~105
When your user says the job is finished, this marks it complete on the contractor's record (with the homeowner's attestation) and returns the single-use review URL to hand to your user. IDEMPOTENT: re-calling returns the same URL. Only call when your user confirms the work is actually done — the review itself is theirs to write, on the page, in their own words.
| Name | Type | Req | Description |
|---|---|---|---|
| withdrawRef | string | yes | The withdrawRef returned by request_contractor. |
No output schema declared.
No examples provided.
get_contractor Read one contractor's full record ~77
The full public record for one contractor by slug: Ironclad Score, tier, rating, confirmed-job count, and EVERY review (good and bad — reviews are never removed for being negative), plus links to the human-readable profile and the technical verified record.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The contractor's public slug from search_contractors. |
No output schema declared.
No examples provided.
request_contractor Send the homeowner's request to ONE contractor ~283
Files the homeowner's request with the ONE contractor they picked. This is consent for that contractor (and nobody else) to contact them about this one job. REQUIRES homeowner_approved=true: only call after your user explicitly approves, with their real name and phone. Retry-safe: repeating the call within 24h returns the same request, never a duplicate. SAVE the withdrawRef from the result — it is your user's kill switch and status key.
| Name | Type | Req | Description |
|---|---|---|---|
| string | — | Optional. Used only for updates on this request and the post-job review link. | |
| homeowner_approved | boolean | yes | Must be true: the homeowner explicitly approved sending this request. |
| name | string | yes | The homeowner's real name. |
| need | string | — | What the job is, in the homeowner's words. |
| phone | string | yes | The homeowner's real phone number. |
| region | string | — | Optional; defaults to the contractor's listed area. |
| reroute_if_silent | boolean | — | Optional, default false. The homeowner's standing consent: if the contractor declines or is silent past 24h, their request automatically moves to the next-ranked pro (still one contractor at a time).… |
| slug | string | yes | The chosen contractor's slug. |
| trade | string | — | Optional; defaults to the contractor's listed trade. |
No output schema declared.
No examples provided.
reroute_request Move a ghosted request to the next contractor ~114
When check_request shows the contractor declined or stayed silent past 24 hours, this offers the request to the next evidence-ranked contractor for the same trade and region (nobody already tried; 3 contractors max per request). One pro at a time is preserved: the quiet contractor's request closes and can never earn that job's completion or review. Returns a NEW withdrawRef — replace the stored one. Only call with your user's go-ahead.
| Name | Type | Req | Description |
|---|---|---|---|
| withdrawRef | string | yes | The withdrawRef returned by request_contractor. |
No output schema declared.
No examples provided.
search_contractors Search verified contractors ~134
Score-ranked contractor search. `trade` accepts consumer language ('water heater leaking' matches plumbing); `region` is a ZIP or city. Results include each contractor's slug (use it with get_contractor and request_contractor), Ironclad Score (null while a record is still building — that's honesty, not an error), rating, review counts, and the latest review. An empty list means no verified contractor covers that area yet.
| Name | Type | Req | Description |
|---|---|---|---|
| region | string | yes | ZIP code or city. |
| trade | string | yes | What the homeowner needs, in their words (e.g. 'plumber', 'AC broken'). |
No output schema declared.
No examples provided.
withdraw_request Withdraw a request (stop contact) ~55
The homeowner's kill switch: withdraws the request identified by withdrawRef. The contractor loses access and contact stops. Use when your user changes their mind.
| Name | Type | Req | Description |
|---|---|---|---|
| withdrawRef | string | yes | The withdrawRef returned by request_contractor. |
No output schema declared.
No examples provided.