Skip to content

Secure Autonomous Register MCP server

io.github.reachsaurabh-creator/secure-autonomous-registerreachsaurabh-creatorstreamable-httpv1.0.1Scanned

Read-only, sourced cases of AI agents, vehicles and robots acting on their own, mapped to controls.

6 tools: 1 change things and 5 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • 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 Secure Autonomous Register MCP server can do

The Secure Autonomous Register MCP server is published by the GitHub account reachsaurabh-creator. It has 6 tools. It can create or change data (1 tool: recent_signals), but cannot delete data. 5 tools only read.

1 tool brings in text other people can write (get_case).

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.1.

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 1Claude Code: ask
  • recent_signalsThe Register's nightly stream of new primary records (vulnerability entries, recalls, rules) touching systems that act on their own, newest first.No 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.
    Description, as the server wrote it
    The Register's nightly stream of new primary records (vulnerability entries, recalls, rules) touching systems that act on their own, newest first. Signals never assign fault.

    Annotations the server declares

    • title: Recent signals
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 5Show 5 read-only tools
  • find_rulesRegulations and standards that bear on autonomous systems, filtered by keyword, jurisdiction (e.g.No findings

    Why it is in this group

    • The name "find_rules" says "find": a word for reading.
    Description, as the server wrote it
    Regulations and standards that bear on autonomous systems, filtered by keyword, jurisdiction (e.g. 'European Union', 'United States', 'California'), or control ID. Each lists the controls it maps to and how strongly (required, implied, recommended, proposed).

    Annotations the server declares

    • title: Find rules
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_caseThe full case: every claim with its type (fact, assertion, interpretation) and source links, the outcome, controls that failed, were absent or held, the Register's labeled interpre…Reads text others writeNo findings

    Why it is in this group

    • The name "get_case" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "reply": it reads comments, which other people can write.
    Description, as the server wrote it
    The full case: every claim with its type (fact, assertion, interpretation) and source links, the outcome, controls that failed, were absent or held, the Register's labeled interpretation, right-of-reply status for each named party, corrections, and a ready citation.

    Annotations the server declares

    • title: Get a case
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_controlOne control: its definition, the cases where it failed, was absent or held, and the regulations and standards that require, imply or recommend it.No findings

    Why it is in this group

    • The name "get_control" says "get": a word for reading.
    Description, as the server wrote it
    One control: its definition, the cases where it failed, was absent or held, and the regulations and standards that require, imply or recommend it.

    Annotations the server declares

    • title: Get a control
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_controlsThe Register's controls (the safeguards that would interrupt the failures it records), each with how many published cases record it as failed, absent or held.No findings

    Why it is in this group

    • The name "list_controls" says "list": a word for reading.
    Description, as the server wrote it
    The Register's controls (the safeguards that would interrupt the failures it records), each with how many published cases record it as failed, absent or held.

    Annotations the server declares

    • title: List controls
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_casesFind Register cases by keywords (company, system, failure, e.g.No findings

    Why it is in this group

    • The name "search_cases" says "search": a word for reading.
    Description, as the server wrote it
    Find Register cases by keywords (company, system, failure, e.g. 'coding agent deletes database', 'robotaxi', 'prompt injection email'), optionally filtered by world (physical, bridge, software, transaction, boundary) or by a control ID that was missing or failed. Returns short summaries with URLs.

    Annotations the server declares

    • title: Search cases
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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 private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
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 16, 2026, 14:20 UTC, unchanged since Nov 16, 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
1
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 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://secureautonomous.com/api/mcp: tools/list returned 6 tools to an anonymous client, including recent_signals (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.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http secure-autonomous-register https://secureautonomous.com/api/mcp
claude mcp add --transport http secure-autonomous-register https://secureautonomous.com/api/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__secure-autonomous-register__search_cases",
      "mcp__secure-autonomous-register__get_case",
      "mcp__secure-autonomous-register__list_controls",
      "mcp__secure-autonomous-register__get_control",
      "mcp__secure-autonomous-register__find_rules"
    ],
    "ask": [
      "mcp__secure-autonomous-register__recent_signals"
    ],
    "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 secure-autonomous-register. Review it before you use it.

Capability tags behind 1 rule
  • mcp__secure-autonomous-register__get_case 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/io.github.reachsaurabh-creator/secure-autonomous-register/verify?hash=e9854ec62b45d82a842bd56d278b79664c8d08d5d28c966c955ca45396d27c47" | jq -e '.changed == false'

Pinned hash e9854ec62b45, from Nov 16, 2026, 05:18 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.reachsaurabh-creator/secure-autonomous-register/changes.xml

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

Badge

Anlyon Radar badge for io.github.reachsaurabh-creator/secure-autonomous-register
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.reachsaurabh-creator/secure-autonomous-register.svg)](https://radar.anlyon.com/servers/io.github.reachsaurabh-creator/secure-autonomous-register)

Source: MCP Registry. Synced Nov 16, 2026, 06:17 UTC.

Secure Autonomous Register MCP server: questions and answers

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

Is the Secure Autonomous Register MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 1 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 Secure Autonomous Register MCP server delete data?

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

Can the Secure Autonomous Register 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 Secure Autonomous Register MCP server have?

6 tools: 1 write, 5 read. recent_signals, search_cases, get_case, list_controls, get_control and find_rules.

Does the Secure Autonomous Register MCP server need sign-in or OAuth?

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

Does the Secure Autonomous Register MCP server send data to outside services?

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

Has the Secure Autonomous Register MCP server changed its tools?

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