Skip to content

ASL Colorado Complaint Access MCP server

com.autosecurelogin/colorado-complaint-accessautosecurelogin.comstreamable-httpv1.0.0Scanned

Colorado DORA license lookups, the SOMB provider directory and answers from the rules and standards.

6 tools: 4 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 4 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 6
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the ASL Colorado Complaint Access MCP server can do

The ASL Colorado Complaint Access MCP server is published by autosecurelogin.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (4 tools: colorado_license_directory, colorado_license_directory_options, colorado_rules_ask and colorado_somb_standards_ask), but cannot delete data. 2 tools only read.

1 tool reads private data (colorado_somb_providers); 6 tools bring in text other people can write (colorado_license_search, colorado_license_directory, colorado_license_directory_options and 3 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 16, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 4Claude Code: ask
  • colorado_license_directoryPage through Colorado licensees by profession category, license type, status, city or state.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • colorado_license_directory_optionsThe profession categories, license types and statuses accepted by colorado_license_directory.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    The profession categories, license types and statuses accepted by colorado_license_directory.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • colorado_rules_askAnswer a question from the included Colorado DORA board and program rules, with cited excerpts.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Answer a question from the included Colorado DORA board and program rules, with cited excerpts. Name the profession, board or program in the question.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • colorado_somb_standards_askAnswer a question from the Colorado SOMB adult or juvenile standards and guidelines, with cited excerpts.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Answer a question from the Colorado SOMB adult or juvenile standards and guidelines, with cited excerpts.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • colorado_somb_providersSearch the Colorado Sex Offender Management Board approved treatment, evaluation and polygraph provider directory by name, county, city, ZIP, service, practice level, language or s…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The description's first verb is "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "search" and "directory": it reads files.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write6
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:24 UTC, unchanged since Nov 4, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.autosecurelogin.com/colorado/mcp: tools/list returned 6 tools to an anonymous client, including colorado_license_directory (write), colorado_license_directory_options (write), colorado_rules_ask (write), colorado_somb_standards_ask (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http colorado-complaint-access https://mcp.autosecurelogin.com/colorado/mcp
claude mcp add --transport http colorado-complaint-access https://mcp.autosecurelogin.com/colorado/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__colorado-complaint-access__colorado_license_search",
      "mcp__colorado-complaint-access__colorado_somb_providers"
    ],
    "ask": [
      "mcp__colorado-complaint-access__colorado_license_directory",
      "mcp__colorado-complaint-access__colorado_license_directory_options",
      "mcp__colorado-complaint-access__colorado_rules_ask",
      "mcp__colorado-complaint-access__colorado_somb_standards_ask"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as colorado-complaint-access. Review it before you use it.

Capability tags behind 6 rules
  • mcp__colorado-complaint-access__colorado_license_search untrusted-input
  • mcp__colorado-complaint-access__colorado_license_directory untrusted-input
  • mcp__colorado-complaint-access__colorado_license_directory_options untrusted-input
  • mcp__colorado-complaint-access__colorado_somb_providers private-data, untrusted-input
  • mcp__colorado-complaint-access__colorado_rules_ask untrusted-input
  • mcp__colorado-complaint-access__colorado_somb_standards_ask untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.autosecurelogin/colorado-complaint-access/verify?hash=c3fff3959c7e6e6b2ae18d2a7eb0cd213a221602a25b5ea6b95eea1267a9cdf8" | jq -e '.changed == false'

Pinned hash c3fff3959c7e, from Nov 16, 2026, 19:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.autosecurelogin/colorado-complaint-access/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.autosecurelogin/colorado-complaint-access
[![Anlyon Radar](https://radar.anlyon.com/badge/com.autosecurelogin/colorado-complaint-access.svg)](https://radar.anlyon.com/servers/com.autosecurelogin/colorado-complaint-access)

Source: MCP Registry. Synced Nov 3, 2026, 08:17 UTC.

ASL Colorado Complaint Access MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the ASL Colorado Complaint Access MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the ASL Colorado Complaint Access MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the ASL Colorado Complaint Access MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the ASL Colorado Complaint Access MCP server have?

6 tools: 4 write, 2 read. colorado_license_directory, colorado_license_directory_options, colorado_rules_ask, colorado_somb_standards_ask, colorado_license_search and colorado_somb_providers.

Does the ASL Colorado Complaint Access MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the ASL Colorado Complaint Access MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the ASL Colorado Complaint Access MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.