ASL Colorado Complaint Access
REMOTE · MCP.AUTOSECURELOGIN.COM
Colorado DORA license lookups, the SOMB provider directory and answers from the rules and standards.
Available components
Last scanned (37 minutes ago)
Scores higher than 57% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 757 tokens (~126/item across 6 items; 6 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 Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 56% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 5 Nov 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.
- 4 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 70
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 5 Nov 2026 · Probed https://mcp.autosecurelogin.com/colorado/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.autosecurelogin.com | CN=YE1,O=Let's Encrypt,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 55fbecac6de1201486d2f7d1f79b0d2f5ea |
| SANs: mcp.autosecurelogin.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.autosecurelogin.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| autosecurelogin.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=31536000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.autosecurelogin.com/colorado/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.autosecurelogin.com/colorado/mcp | HTTPS enforced | 301 | https://mcp.autosecurelogin.com/colorado/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. 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 →
colorado_license_directory Browse Colorado licensees ~174
Page through Colorado licensees by profession category, license type, status, city or state. Call colorado_license_directory_options first for the valid categories, types and statuses.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| licenseCategory | string | – | A profession category from the options, for example "Electrical". |
| licenseNumber | string | – | – |
| licenseType | string | – | A license type code from the options. |
| limit | integer | – | Records per page, 10 to 50 (default 30). |
| name | string | – | – |
| page | integer | – | Page number (default 1). |
| sort | string | – | – |
| state | string | – | Licensee address state (two letters or full name). |
| status | string | – | License status (default Active); "all" for every status. |
No output schema declared.
No examples provided.
colorado_license_directory_options License directory filters ~24
The profession categories, license types and statuses accepted by colorado_license_directory.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
colorado_license_search Look up a Colorado license ~87
Search Colorado professional and business licenses (DORA) by licensee name or exact license number, optionally by city. Returns status, type, expiry and the official verification link.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| licenseNumber | string | – | Exact license number. |
| limit | integer | – | Results to return (default 20). |
| name | string | – | Professional or business name. |
No output schema declared.
No examples provided.
colorado_rules_ask Ask about DORA rules ~77
Answer a question from the included Colorado DORA board and program rules, with cited excerpts. Name the profession, board or program in the question.
| Name | Type | Req | Description |
|---|---|---|---|
| evidenceScope | string | – | Current rules only (default), related documents, or all. |
| language | string | – | Answer language (default en). |
| question | string | yes | – |
No output schema declared.
No examples provided.
colorado_somb_providers Find SOMB treatment providers ~205
Search the Colorado Sex Offender Management Board approved treatment, evaluation and polygraph provider directory by name, county, city, ZIP, service, practice level, language or specialty.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| clientChoiceApproved | boolean | – | Only providers on the client-choice list. |
| county | string | – | – |
| ddidApproved | boolean | – | Only providers approved for developmental or intellectual disabilities. |
| excludeCorrectional | boolean | – | – |
| excludePolygraphOnly | boolean | – | – |
| language | string | – | Language offered, for example Spanish. |
| limit | integer | – | Results per page (default 30). |
| page | integer | – | – |
| practiceLevel | string | – | – |
| query | string | – | Provider or practice name. |
| service | string | – | Service type, for example evaluation, treatment, polygraph; "care" means evaluation or treatment. |
| specialty | string | – | – |
| zip | string | – | – |
No output schema declared.
No examples provided.
colorado_somb_standards_ask Ask about SOMB standards ~64
Answer a question from the Colorado SOMB adult or juvenile standards and guidelines, with cited excerpts.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Answer language (default en). |
| population | string | – | Which standards (default all). |
| question | string | yes | – |
No output schema declared.
No examples provided.
How do I install the ASL Colorado Complaint Access MCP server?
ASL Colorado Complaint Access is a hosted endpoint at https://mcp.autosecurelogin.com/colorado/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 · mcp.autosecurelogin.com
claude mcp add --transport http com-autosecurelogin-colorado-complaint-access 'https://mcp.autosecurelogin.com/colorado/mcp'
What is the ASL Colorado Complaint Access MCP server?
ASL Colorado Complaint Access is an MCP server listed in the public MCP registry as com.autosecurelogin/colorado-complaint-access. Colorado DORA license lookups, the SOMB provider directory and answers from the rules and standards. This page covers its hosted endpoint (https://mcp.autosecurelogin.com/colorado/mcp).
Is the ASL Colorado Complaint Access MCP server safe to use?
ASL Colorado Complaint Access scores 71 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 ASL Colorado Complaint Access MCP server expose?
ASL Colorado Complaint Access exposes 6 tools: colorado_license_search, colorado_license_directory, colorado_license_directory_options, colorado_somb_providers, colorado_rules_ask, colorado_somb_standards_ask. Their descriptions and schemas cost roughly 631 tokens of context every time the server is loaded.
Does the ASL Colorado Complaint Access MCP server require authentication?
No. We connected to ASL Colorado Complaint Access without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ASL Colorado Complaint Access MCP server still maintained?
ASL Colorado Complaint Access is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.