mcpbeat

Ironclad Verified MCP Server

com.ironcladverified/verified
answering

Ironclad Verified is answering right now. Last checked 10 min ago. It exposes 7 tools.

Hire evidence-verified home-service contractors. Confirmed-job reviews only; rank is never buyable.

Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
7
Tools
read from the server
447 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

run in your terminal
claude mcp add verified --transport http https://ironcladverified.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "verified": {
      "url": "https://ironcladverified.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.verified]
url = "https://ironcladverified.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "verified": {
      "url": "https://ironcladverified.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "verified": {
      "url": "https://ironcladverified.com/mcp"
    }
  }
}

Available tools 7

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

request
check_request
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.
request_contractor
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.
complete
complete_job
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.
contractor
get_contractor
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.
contractors
search_contractors
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.
reroute
reroute_request
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.
withdraw
withdraw_request
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.

Endpoints

URLTransportStateLatencyChecked
https://ironcladverified.com/mcp streamable-http answering 436 ms 10 min ago

Ironclad Verified — questions

Answers built from our own checks of this server.

What can Ironclad Verified do?
It exposes 7 tools, read directly from the server on our last check. Among them: check_request, complete_job, get_contractor, request_contractor, reroute_request, search_contractors and 1 more. 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 Ironclad Verified 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 447 ms. The bar chart above shows every period we have measured.
How do I connect Ironclad Verified?
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 Ironclad Verified need an API key?
No. Ironclad Verified completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Ironclad Verified?
It answers our handshake in 447 ms on average, which is faster than 28% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.