Is the Contractorroster MCP server down?

mcp-registry/com.contractorroster/contractorroster · v1.0.0

healthy
Last checked 2026-10-26 17:29 UTC · handshake 217ms

As of 2026-10-26 17:29 UTC, the Contractorroster MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 2 minutes.

uptime (30d checks)
99.9%
checks observed
4,894
outages (90d)
3
tools
5

Verified US licensed-contractor data: 879k+ state-board records, metered per record, free discovery.

Point your MCP client at this streamable-http endpoint: https://contractorroster.com/api/mcp

Agent-readiness: C (77/100)

C (77/100): 0 error(s), 2 warning(s) across 5 tool(s); ~772 tokens of tool definitions.
Scores higher than 13% of 15,771 MCP servers Glimind has audited.
Its tool list costs an agent ~772 tokens per session — lighter than 80% of servers.
76 → 77 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions62
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (3)

5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: count_contractors, get_usage, list_states, list_trades, search_contractors

12 parameter(s) across 2 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: count_contractors, search_contractors

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 5 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.contractorroster%2Fcontractorroster/fixes

count_contractors 1 change
{
  "name": "count_contractors",
  "description": "Count contractors matching a state × trade × geo query, without charging. Use to qualify a query before calling search_contractors. Returns total count and estimated cost in cents at the caller's price tier.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "state",
      "trade",
      "geo_type",
      "geo_value"
    ],
    "properties": {
      "state": {
        "enum": [
          "CO",
          "TX",
          "WA",
          "OR",
          "CA",
          "FL",
          "VA",
          "MN",
          "OH",
          "AZ",
          "IL",
          "NY",
          "PA",
          "NV",
          "UT",
          "MA",
          "CT",
          "LA",
          "OK",
          "AL",
          "AR",
          "WV",
          "NE",
          "ID",
          "AK",
          "IA",
          "ME",
          "TN",
          "MS",
          "MT",
          "HI",
          "DE",
          "VT",
          "DC"
        ],
        "type": "string"
      },
      "trade": {
        "enum": [
          "EC",
          "PC",
          "HVAC",
          "GC",
          "ROOFING",
          "SOLAR",
          "LANDSCAPE",
          "POOL",
          "FIRE_PROTECTION",
          "CARPENTRY",
          "CONCRETE",
          "MASONRY",
          "DRYWALL",
          "TILE",
          "EXCAVATING",
          "PAINTING",
          "FLOORING"
        ],
        "type": "string"
      },
      "geo_type": {
        "enum": [
          "zip",
          "city"
        ],
        "type": "string"
      },
      "geo_value": {
        "type": "string",
        "maxLength": 60,
        "minLength": 1
      },
      "active_only": {
        "type": "boolean"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_usage 1 change
{
  "name": "get_usage",
  "description": "Return the partner's current balance, pricing, and the 20 most recent transactions (top-ups + api calls). No charge.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}
list_states 1 change
{
  "name": "list_states",
  "description": "List supported US states with their available geo types and per-trade availability. Free; no auth required.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.contractorroster/contractorroster"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.contractorroster/contractorroster"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.contractorroster%2Fcontractorroster.svg)](https://glimind.com/server/mcp-registry%2Fcom.contractorroster%2Fcontractorroster?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.contractorroster%2Fcontractorroster?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.contractorroster%2Fcontractorroster.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.contractorroster%2Fcontractorroster.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.contractorroster%2Fcontractorroster?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:fa5c4f1bd7905be3…, first seen 2026-10-17, included at leaf 30 of 74,435. Version history · verify what your client received.

Tools (5)

Compare: most reliable search servers · most reliable finance servers · most reliable data servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Contractorroster MCP server down right now?

As of 2026-10-26 17:29 UTC, the Contractorroster MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 2 minutes.

How many tools does Contractorroster MCP server provide?

Contractorroster MCP server advertises 5 tools, including count_contractors, get_usage, list_states, list_trades, search_contractors.

How do I install Contractorroster MCP server?

Point your MCP client at this streamable-http endpoint: https://contractorroster.com/api/mcp

Is the Contractorroster MCP server safe to connect to an AI agent?

Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Contractorroster MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve