Skip to content

LrrK Agent Desk MCP server

ai.lrrk/agent-desklrrk.aistreamable-httpv1.1.0Scanned

Read-only tools for cited LrrK evidence, weekly publication changes, and reviewed service referrals.

5 tools: 2 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 2 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Its sign-in does not let Anlyon set up an OAuth client on its own, so there is no link to it here.

What the LrrK Agent Desk MCP server can do

The LrrK Agent Desk MCP server is published by lrrk.ai, a domain the MCP Registry verified. It has 5 tools. It can create or change data (2 tools: lrrk_check_updates and lrrk_map_coverage), but cannot delete data. 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 19, 2026, version 1.1.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.

5 tools

Changes things 2Claude Code: ask
  • lrrk_check_updatesGet exact record additions, corrections, and withdrawals between saved published version keys and the current public versions.1 finding

    Why it is in this group

    • The name "lrrk_check_updates" says "update": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "lrrk_check_updates" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true}; The name "lrrk_check_updates" says "update": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Get exact record additions, corrections, and withdrawals between saved published version keys and the current public versions. Follow nextPage with the same knownVersions before saving the new keys. An unknown checkpoint or unavailable source means the exact comparison is incomplete.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
  • lrrk_map_coverageMap a topic and optional device class to reviewed public references and explicit gaps.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
    Map a topic and optional device class to reviewed public references and explicit gaps. Search matches are not device-specific applicability, testing, or risk verdicts.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
Only reads 3Show 3 read-only tools
  • lrrk_find_evidenceSearch published LrrK Letters, reviewed Hardware Attack Library records, and admitted Intelligence Product metadata.No findings

    Why it is in this group

    • The name "lrrk_find_evidence" says "find": a word for reading.
    Description, as the server wrote it
    Search published LrrK Letters, reviewed Hardware Attack Library records, and admitted Intelligence Product metadata. Returns bounded excerpts and canonical source links. Historical paid publication bodies are never returned.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
  • lrrk_find_serviceFind LrrK's human-reviewed Assess, Engage, Monitor, or one-question Evidence Brief path for a stated need.No findings

    Why it is in this group

    • The name "lrrk_find_service" says "find": a word for reading.
    Description, as the server wrote it
    Find LrrK's human-reviewed Assess, Engage, Monitor, or one-question Evidence Brief path for a stated need. Returns criteria and a first-party link; no inquiry is submitted and no work is initiated.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
  • lrrk_get_evidenceRetrieve the metadata, edition, citations, evidence status and limits for one public LrrK record.No findings

    Why it is in this group

    • The name "lrrk_get_evidence" says "get": a word for reading.
    Description, as the server wrote it
    Retrieve the metadata, edition, citations, evidence status and limits for one public LrrK record. A historical Intelligence Product returns metadata and its exact-edition owner handoff only.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: 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 private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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 19, 2026, 17:18 UTC, unchanged since Nov 19, 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
https://lrrk.ai/.well-known/oauth-protected-resource
Authorization servers
https://lrrk.ai/agent
Legacy HTTP+SSE transport
no
Dynamic client registration
no
Client ID metadata documents
no
  • 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://lrrk.ai/mcp/public: tools/list returned 5 tools to an anonymous client, including lrrk_check_updates (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "lrrk_check_updates" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true}; The name "lrrk_check_updates" says "update": a word for a change.

    What this check looks for

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.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http agent-desk https://lrrk.ai/mcp/public
claude mcp add --transport http agent-desk https://lrrk.ai/mcp/public

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__agent-desk__lrrk_find_evidence",
      "mcp__agent-desk__lrrk_get_evidence",
      "mcp__agent-desk__lrrk_find_service"
    ],
    "ask": [
      "mcp__agent-desk__lrrk_check_updates",
      "mcp__agent-desk__lrrk_map_coverage"
    ],
    "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 agent-desk. Review it before you use it.

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/ai.lrrk/agent-desk/verify?hash=a4eab784d27bdede916fd53fe2f190be665aa4fbce90591ce293e8e3d339a51f" | jq -e '.changed == false'

Pinned hash a4eab784d27b, from Nov 19, 2026, 03:17 UTC.

Watch

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

https://radar.anlyon.com/servers/ai.lrrk/agent-desk/changes.xml

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

Badge

Anlyon Radar badge for ai.lrrk/agent-desk
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.lrrk/agent-desk.svg)](https://radar.anlyon.com/servers/ai.lrrk/agent-desk)

Source: MCP Registry. Synced Nov 19, 2026, 04:17 UTC.

LrrK Agent Desk MCP server: questions and answers

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

Is the LrrK Agent Desk MCP server safe?

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

Can the LrrK Agent Desk MCP server delete data?

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

Can the LrrK Agent Desk 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 LrrK Agent Desk MCP server have?

5 tools: 2 write, 3 read. lrrk_check_updates, lrrk_map_coverage, lrrk_find_evidence, lrrk_get_evidence and lrrk_find_service.

Does the LrrK Agent Desk MCP server need sign-in or OAuth?

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

Does the LrrK Agent Desk MCP server send data to outside services?

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

Has the LrrK Agent Desk MCP server changed its tools?

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