Skip to content

Lexicon Garden MCP server

garden.lexicon/lexicon-gardenlexicon.gardenstreamable-httpv3.0.20Scanned

Resolve, search, and validate AT Protocol lexicons.

6 tools: 2 change things and 4 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

2 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 Lexicon Garden MCP server can do

The Lexicon Garden MCP server is published by lexicon.garden, a domain the MCP Registry verified. It has 6 tools. It can create or change data (2 tools: check_compatibility and discover_permission_sets), but cannot delete data. 4 tools only read.

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

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 20, 2026, version 3.0.20.

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 2Claude Code: ask
  • check_compatibilityCheck compatibility between two versions of an ATProtocol lexicon schema.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.
    Description, as the server wrote it
    Check compatibility between two versions of an ATProtocol lexicon schema. Detects breaking vs non-breaking changes and provides migration guidance. Supply either two schema JSON objects directly (from_schema + to_schema), or an NSID with two CIDs to compare stored versions (nsid + from_cid + to_cid).
  • discover_permission_setsDiscover which ATProtocol permission-set lexicon schemas cover a given set of collections and/or XRPC methods.No findings

    Why it is in this group

    • The name "discover_permission_sets" says "set": a word for a change.
    Description, as the server wrote it
    Discover which ATProtocol permission-set lexicon schemas cover a given set of collections and/or XRPC methods. Returns matching permission sets with their OAuth scope strings (`include:<nsid>`), useful for determining what OAuth scopes an application needs.
Only reads 4Show 4 read-only tools
  • describe_lexiconGet detailed information about an ATProtocol lexicon schema: its definitions, authority, CID and any published documentation.No findings

    Why it is in this group

    • The name "describe_lexicon" says "describe": a word for reading.
    Description, as the server wrote it
    Get detailed information about an ATProtocol lexicon schema: its definitions, authority, CID and any published documentation. Use this to understand the structure and format of XRPC methods, records, and other lexicon types.
  • resolve_lexiconResolve an ATProtocol lexicon by NSID: find the DID named by the `_lexicon` TXT record of the NSID's authority and read that DID's com.atproto.lexicon.schema record, from Lexicon G…No findings

    Why it is in this group

    • The name "resolve_lexicon" says "resolve": a word for reading.
    Description, as the server wrote it
    Resolve an ATProtocol lexicon by NSID: find the DID named by the `_lexicon` TXT record of the NSID's authority and read that DID's com.atproto.lexicon.schema record, from Lexicon Garden's index or, when it is not indexed or refresh is set, from the network. Returns the schema, its AT-URI and CID, the authority DID and where it came from.
  • search_lexiconsFind ATProtocol lexicons by what their schemas say: descriptions, definition names, field names and known values.No findings

    Why it is in this group

    • The name "search_lexicons" says "search": a word for reading.
    Description, as the server wrote it
    Find ATProtocol lexicons by what their schemas say: descriptions, definition names, field names and known values. Use it when you don't know the NSID. mode "keyword" (default) matches words; mode "semantic" ranks by meaning, so a plain description of what you need works (e.g. 'store a user's reading list'), and it falls back to keyword when unavailable. By default only lexicons published by their NSID's DNS authority are returned. Returns NSIDs with summaries and AT-URIs; follow up with describe_lexicon.
  • validate_lexiconValidate a lexicon schema and optionally validate data against it.No findings

    Why it is in this group

    • The name "validate_lexicon" says "validate": a word for reading.
    Description, as the server wrote it
    Validate a lexicon schema and optionally validate data against it. Use this to verify schema correctness and validate records, query params, or procedure inputs against their schemas.

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 20, 2026, 18:19 UTC, unchanged since Nov 20, 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
2
Protocol version
2025-11-25
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 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://lexicon.garden/mcp: tools/list returned 6 tools to an anonymous client, including check_compatibility (write), discover_permission_sets (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 3.0.20. Values in angle brackets are yours to fill in.

claude mcp add --transport http lexicon-garden https://lexicon.garden/mcp
claude mcp add --transport http lexicon-garden https://lexicon.garden/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__lexicon-garden__resolve_lexicon",
      "mcp__lexicon-garden__search_lexicons",
      "mcp__lexicon-garden__describe_lexicon",
      "mcp__lexicon-garden__validate_lexicon"
    ],
    "ask": [
      "mcp__lexicon-garden__check_compatibility",
      "mcp__lexicon-garden__discover_permission_sets"
    ],
    "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 lexicon-garden. 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/garden.lexicon/lexicon-garden/verify?hash=3b13b99d0e83e1cc87594e1966f3ab009a68022ca0a9d90ad526c00005cb5055" | jq -e '.changed == false'

Pinned hash 3b13b99d0e83, from Nov 20, 2026, 14:18 UTC.

Watch

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

https://radar.anlyon.com/servers/garden.lexicon/lexicon-garden/changes.xml

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

Badge

Anlyon Radar badge for garden.lexicon/lexicon-garden
[![Anlyon Radar](https://radar.anlyon.com/badge/garden.lexicon/lexicon-garden.svg)](https://radar.anlyon.com/servers/garden.lexicon/lexicon-garden)

Source: MCP Registry. Synced Nov 20, 2026, 14:17 UTC.

Lexicon Garden MCP server: questions and answers

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

Is the Lexicon Garden MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 2 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 Lexicon Garden MCP server delete data?

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

Can the Lexicon Garden 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 Lexicon Garden MCP server have?

6 tools: 2 write, 4 read. check_compatibility, discover_permission_sets, resolve_lexicon, search_lexicons, describe_lexicon and validate_lexicon.

Does the Lexicon Garden MCP server need sign-in or OAuth?

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

Does the Lexicon Garden MCP server send data to outside services?

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

Has the Lexicon Garden MCP server changed its tools?

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