MCP.Market

Leaseclear MCP server

by amadeuserras·io.github.amadeuserras/leaseclear-mcp·v0.1.3

MCP server for LeaseClear lease Q&A.

B78/100grade B
What users say
No reviews yet
Be the first
Safety scan
B78/100

full report

Adoption
New

0 stars23 downloads/wk

Reviews

Write one

Nobody has reviewed Leaseclear yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Leaseclear tools (1)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • lease_qa

    Ask one neutral, precise question about lease terms. Returns an answer grounded in the lease, or states that the lease does not address the question.

Public scan report

scanner v0.1.10 · 2026-11-02 · same rubric, same numbers if you re-run it

no findings
  • Code scan6 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 73 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Leaseclear compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
78/100
higher than 57% of 48,255 servers
Tools
1
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
23
more than 9% of 12,191 servers with a package

What its tools let an agent do: 1 read

Install Leaseclear in Claude Code, Cursor or VS Code

claude mcp add leaseclear-mcp -- uvx leaseclear-mcp
Add to Cursor

What the publisher says

From the Leaseclear repository's README, as published. We do not edit it. Read it on GitHub

leaseclear-mcp

A Model Context Protocol server that exposes LeaseClear lease Q&A.

<!-- mcp-name: io.github.amadeuserras/leaseclear-mcp -->

Listed in the official MCP Registry as io.github.amadeuserras/leaseclear-mcp.

Tools

  • lease_qa — ask one question about lease terms; returns an answer grounded in the lease, or states that the lease is silent

Usage

Add this to your MCP client config (e.g. claudedesktopconfig.json or Cursor mcp.json):

{
  "mcpServers": {
    "lease-qa": {
      "command": "uvx",
      "args": ["leaseclear-mcp"]
    }
  }
}

The package is on PyPI. uvx fetches and runs it as a local subprocess, communicating over stdio. uv required.

Optional environment variables

{
  "mcpServers": {
    "lease-qa": {
      "command": "uvx",
      "args": ["leaseclear-mcp"],
      "env": {
        "LEASECLEAR_API_KEY": "lc_...",
        "LEASECLEAR_API_URL": "https://..."
      }
    }
  }
}

lease_qa usage

Argument

  • question (string, required) — one question about the lease

_meta

  • document_ids (string[], optional) — UUIDs of the documents to query. Omitted means all.

Security: The meta field is used to pass metadata to the tool call that the model doesn't see. Having documentids there is intentional: it prevents cross-document prompt injection because the model is never able to choose which documents it has access to. See a real-world example in LeaseOps: prompt injection and the tenants table.

MCP Python SDK example

Tool call:

result = await session.call_tool(
    name="lease_qa",
    arguments={
        "question": "How much is the security deposit for Yuna Kim?"
    },
    meta={
        "document_ids": [
            "a1b2c3d4-e5f..."
        ]
    }
)

Output:

{
  "answer": "The security deposit is $6,400.00. This deposit is held in Owner's Broker's trust account [california-johnson-kim §4]."
}

Tech stack

  • Python 3.12
  • Model Context Protocol Python SDK (mcp[cli]) over stdio
  • httpx for LeaseClear API calls
  • Pydantic and pydantic-settings for schemas and config
  • uv and uv_build for running and packaging
  • pytest, Ruff, and Pyright for tests, linting, and type checking

Project structure

leaseclear-mcp/
├── src/leaseclear_mcp/
│   ├── server.py        # MCP server + lease_qa
│   ├── leaseclear.py    # LeaseClear HTTP client
│   ├── schemas.py
│   └── config.py
├── tests/
├── pyproject.toml
├── .env.example
└── README.md

Local Development

git clone https://github.com/you/leaseclear-mcp.git
cd leaseclear-mcp
uv sync
cp .env.example .env
uv run pytest
uv run ruff check .
uv run pyright

Debugging

Use the MCP Inspector to test the server interactively:

npx @modelcontextprotocol/inspector uvx leaseclear-mcp

From a checkout, use uv run leaseclear-mcp instead of uvx leaseclear-mcp.

License

MIT

Nothing above is checked by us. What we check is on the safety report.

Leaseclear: common questions

Is Leaseclear MCP server safe?
Mostly: it is graded B (78/100). Read the Leaseclear safety report
How do I install Leaseclear?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Leaseclear need an API key?
Yes. The registry entry asks for LEASECLEAR_API_KEY.
Is Leaseclear maintained?
The last commit was 75 days ago (2026-08-21). The latest release is v0.1.3.
How does Leaseclear compare with other MCP servers?
safety score 78/100 (higher than 57% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.