Is the Ottobot Contractor License Changes MCP server down?

mcp-registry/agency.ottobot/contractor-license-changes · v0.1.3

healthy
Last checked 2026-10-26 23:43 UTC · handshake 64ms

As of 2026-10-26 23:43 UTC, the Ottobot Contractor License Changes MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
4,924
outages (90d)
0
tools
2

Did this contractor's licence change? Observed lapses and reinstatements, not a snapshot.

Point your MCP client at this streamable-http endpoint: https://license-changes-mcp.ottobot2025.workers.dev/mcp

Agent-readiness: B (85/100)

B (85/100): 0 error(s), 1 warning(s) across 2 tool(s); ~595 tokens of tool definitions.
Scores higher than 44% of 15,777 MCP servers Glimind has audited.
Its tool list costs an agent ~595 tokens per session — lighter than 90% of servers.
84 → 85 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (2)

2 of 2 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: check_license_history, recent_license_changes

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: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fagency.ottobot%2Fcontractor-license-changes/fixes

check_license_history 1 change
{
  "name": "check_license_history",
  "description": "Has this contractor's licence changed? Returns every status transition observed in the state board's own published file since 2026-07-17 -- suspensions, expirations, reinstatements and first appearance -- with the date each was seen. This is change over time, not a current-status lookup: use it after a snapshot check, to find out whether the licence you are about to rely on lapsed and came back. Distinguishes 'no change observed' from 'this source is not observed for that change', which are not ",
  "inputSchema": {
    "type": "object",
    "required": [
      "state",
      "license_number"
    ],
    "properties": {
      "state": {
        "type": "string",
        "pattern": "^[A-Za-z]{2}$",
        "description": "Two-letter state code. Covered: AZ, CA, CO, CT, DE, FL, IA, NV, NY, OR, TX, UT, VA, WA",
        "patternMessage": "argument state must be a two-letter state code, e.g. CA"
      },
      "license_number": {
        "type": "string",
        "pattern": ".*\\S.*",
        "description": "The licence number as the board prints it",
        "patternMessage": "argument license_number must not be blank"
      }
    }
  },
  "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/agency.ottobot/contractor-license-changes"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/agency.ottobot/contractor-license-changes"}) 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%2Fagency.ottobot%2Fcontractor-license-changes.svg)](https://glimind.com/server/mcp-registry%2Fagency.ottobot%2Fcontractor-license-changes?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fagency.ottobot%2Fcontractor-license-changes?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fagency.ottobot%2Fcontractor-license-changes.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fagency.ottobot%2Fcontractor-license-changes.svg
   :target: https://glimind.com/server/mcp-registry%2Fagency.ottobot%2Fcontractor-license-changes?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:484704ca926401ab…, first seen 2026-10-17, included at leaf 1423 of 76,148. Version history · verify what your client received.

Tools (2)

Compare: 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 Ottobot Contractor License Changes MCP server down right now?

As of 2026-10-26 23:43 UTC, the Ottobot Contractor License Changes MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Ottobot Contractor License Changes MCP server provide?

Ottobot Contractor License Changes MCP server advertises 2 tools, including check_license_history, recent_license_changes.

How do I install Ottobot Contractor License Changes MCP server?

Point your MCP client at this streamable-http endpoint: https://license-changes-mcp.ottobot2025.workers.dev/mcp

Is the Ottobot Contractor License Changes MCP server safe to connect to an AI agent?

Glimind scanned all 2 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 Ottobot Contractor License Changes 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