Ironclad Verified
REMOTE · IRONCLADVERIFIED.COM
Hire evidence-verified home-service contractors. Confirmed-job reviews only; rank is never buyable.
Available components
Last scanned (46 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 31 Aug 2026.
Category CRM and Sales
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 7 Sept 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 6 Sept 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 5 Sept 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 4 Sept 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 3 Sept 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 1 Sept 26 0
- Endpoint reachability: not serving MCP → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- 26 Aug 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
- 11 Aug 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
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 7 Sept 2026 · Probed https://ironcladverified.com/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of ironcladverified.com. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| ironcladverified.com. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ironcladverified.com/mcp | Unreachable | ||
| http (plaintext) | http://ironcladverified.com/mcp | HTTPS enforced |
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 →
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.
How do I install the Ironclad Verified MCP server?
Ironclad Verified is a hosted endpoint at https://ironcladverified.com/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 · ironcladverified.com
claude mcp add --transport http com-ironcladverified-verified 'https://ironcladverified.com/mcp'
What is the Ironclad Verified MCP server?
Ironclad Verified is an MCP server listed in the public MCP registry as com.ironcladverified/verified. Hire evidence-verified home-service contractors. Confirmed-job reviews only; rank is never buyable. This page covers its hosted endpoint (https://ironcladverified.com/mcp).
Is the Ironclad Verified MCP server safe to use?
Ironclad Verified scores 0 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 Ironclad Verified MCP server expose?
Ironclad Verified exposes 7 tools: search_contractors, get_contractor, request_contractor, reroute_request, complete_job, and 2 more. Their descriptions and schemas cost roughly 856 tokens of context every time the server is loaded.
Does the Ironclad Verified MCP server require authentication?
Its publisher declares no required credentials for Ironclad Verified. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Ironclad Verified MCP server still maintained?
Ironclad Verified has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 31 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.