_ registry / mcp streamable-http · checked 17h ago

lexicon-garden

https://lexicon.garden

Registry code: 263d083127382689

api record

This is a read-only, unauthenticated server for Lexicon Garden's lexicon index. Use resolve_lexicon to fetch a schema through its NSID authority, search_lexicons to find lexicons by NSID or meaning, describe_lexicon to read a schema's definitions, validate_lexicon to check schemas and data, check_compatibility to compare schema versions, and discover_permission_sets to find OAuth permission sets. Browse namespaces with the lexicon://browse/{prefix} resource. No sign-in is required.

endpoint
https://lexicon.garden/mcp
protocol
streamable-http ·2025-11-25
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is lexicon-garden live?
Yes — it answered the hub's last check (checked 17h ago). It answered 100% of checks over the last 30 days.
Is lexicon-garden free to use?
Yes — the hub reached it with no key and no payment.
What tools does lexicon-garden have?
6 tools: describe_lexicon, validate_lexicon, discover_permission_sets, resolve_lexicon, check_compatibility, search_lexicons.
Is lexicon-garden safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
227ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 6 tools
6 never probed 0 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • describe_lexicon unknown 17h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "lexicon"
      ],
      "properties": {
        "lexicon": {
          "type": "string",
          "description": "The lexicon NSID to describe (e.g., 'app.bsky.feed.post', 'com.atproto.repo.createRecord', or 'app.bsky.actor.profile#viewBasic' for a specific fragment)"
        },
        "identity": {
          "type": "string",
          "description": "Optional: The identity (DID like 'did:plc:...' or handle like 'alice.bsky.social') of the authority publishing this lexicon. If not provided, the authority will be resolved via DNS."
        },
        "language": {
          "type": "string",
          "description": "Optional: Preferred language code (ISO 639) for localized descriptions from garden.lexicon.documentation records. If not provided, only schema descriptions are shown. Use language codes like 'en', 'pt-BR', 'ja', etc."
        }
      }
    }
    arguments 20 lines
  • validate_lexicon unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "schema"
      ],
      "properties": {
        "flags": {
          "type": "object",
          "properties": {
            "allowLegacyBlob": {
              "type": "boolean",
              "description": "Allow legacy blob format (cid field instead of ref)"
            },
            "externalSchemas": {
              "type": "array",
              "items": {
                "type": "object"
              },
              "description": "External schemas to use for validation (as JSON objects)"
            },
            "skipExternalRefs": {
              "type": "boolean",
              "description": "Skip validation of external references (treat them as valid)"
            },
            "allowLenientDatetime": {
              "type": "boolean",
              "description": "Allow lenient datetime parsing"
            }
          },
          "description": "Optional: Validation flags"
        },
        "input": {
          "type": "object",
          "description": "Optional: Procedure input body to validate (for procedure schemas only)"
        },
        "params": {
          "type": "object",
          "description": "Optional: Query parameters to validate (for query or procedure schemas)"
        },
        "record": {
          "type": "object",
          "description": "Optional: Record data to validate (for record schemas only)"
        },
        "schema": {
          "type": "object",
          "description": "The lexicon schema to validate (the full lexicon document as a JSON object)"
        }
      }
    }
    arguments 49 lines
  • discover_permission_sets unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "collections"
      ],
      "properties": {
        "methods": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Optional: List of XRPC method NSIDs your application calls (e.g., ['app.bsky.video.uploadVideo', 'com.atproto.repo.listRecords'])"
        },
        "collections": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "List of collection NSIDs your application reads or writes (e.g., ['app.bsky.feed.post', 'app.bsky.actor.profile', 'garden.lexicon.example'])"
        }
      }
    }
    arguments 22 lines
  • resolve_lexicon unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "nsid"
      ],
      "properties": {
        "nsid": {
          "type": "string",
          "description": "The NSID to resolve (e.g., 'app.bsky.feed.post')"
        },
        "refresh": {
          "type": "boolean",
          "description": "Optional: read the record from the network even when it is indexed"
        }
      }
    }
    arguments 16 lines
  • check_compatibility unknown 17h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {
        "nsid": {
          "type": "string",
          "description": "Optional: The lexicon NSID. If provided with from_cid and to_cid, fetches schemas from storage."
        },
        "to_cid": {
          "type": "string",
          "description": "Optional: CID of the newer version (used with nsid)"
        },
        "from_cid": {
          "type": "string",
          "description": "Optional: CID of the older version (used with nsid)"
        },
        "to_schema": {
          "type": "object",
          "description": "Optional: The newer schema JSON (used without nsid)"
        },
        "from_schema": {
          "type": "object",
          "description": "Optional: The older schema JSON (used without nsid)"
        }
      }
    }
    arguments 25 lines
  • search_lexicons unknown 17h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "mode": {
          "enum": [
            "keyword",
            "semantic"
          ],
          "type": "string",
          "description": "keyword (default) or semantic"
        },
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "Maximum results (default 10)"
        },
        "query": {
          "type": "string",
          "description": "What to search for: words, a phrase in quotes, -word to exclude, or (with mode semantic) a plain description. 2 to 256 characters."
        },
        "lexicon_types": {
          "type": "array",
          "items": {
            "enum": [
              "record",
              "query",
              "procedure",
              "subscription",
              "permission-set"
            ],
            "type": "string"
          },
          "description": "Only return lexicons whose main definition has one of these types"
        },
        "include_non_authoritative": {
          "type": "boolean",
          "description": "Also return lexicons whose publisher is not the NSID's DNS authority (default false). Such copies may be forks or impersonations."
        }
      }
    }
    arguments 44 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 263d083127382689.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/263d083127382689/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/263d083127382689/badge.svg)](https://brick.blue/agent/263d083127382689?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.