Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

RedFlagLease

REMOTE · REDFLAGLEASE.COM

Check US leases for red flags and look up verified state tenant law with statute citations.

Available components

75 Trust /100

Last scanned (33 minutes ago)

Scores higher than 68% of remote servers

Reachable. Last reached 24 Oct 2026.

Category Documents and Files

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 328 tokens (~164/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “check_lease” rewrote its description, which is the text the model reads security
  • 21 Oct 26 0
    • Tool “check_lease” rewrote its description, which is the text the model reads security
  • 20 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 19 Oct 26 72

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 24 Oct 2026 · Probed https://redflaglease.com/api/leasecheck/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=redflaglease.com CN=YE2,O=Let's Encrypt,C=US 18 Oct 2026 16 Jan 2027 ECDSA 256 ECDSA-SHA384 6eb8f11f50fcbbfa9cc77bfe0a419d91ef2
SANs: *.redflaglease.com, redflaglease.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of redflaglease.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
redflaglease.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff
x-frame-options DENY
referrer-policy same-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://redflaglease.com/api/leasecheck/mcp Verified 200
http (plaintext) http://redflaglease.com/api/leasecheck/mcp HTTPS enforced 301 https://redflaglease.com/api/leasecheck/mcp
MCP tools · 2 exposed · ~244 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_lease ~145

Scan a US residential lease for risky, unusual or likely unenforceable clauses under that state's tenant law. Pass the full lease text. Returns every flagged clause with its severity, the risk and the state rule/citation, plus a link to the full report on redflaglease.com (quoted clauses, how to fix each one, missing protections, questions to ask, ready-to-send negotiation email, printable and emailed). Takes up to ~45 seconds. Information, not legal advice.

NameTypeReqDescription
lease_textstringyesFull text of the lease (at least a few paragraphs)
statestringyesTwo-letter US state code, e.g. CA, NY, TX

No output schema declared.

No examples provided.

tenant_law ~99

Verified landlord-tenant rules for one US state, checked against the official statutes: security deposit limit and return deadline, late-fee rules, landlord entry notice, notice to end a month-to-month tenancy, rent-increase notice, repairs, retaliation, and lease clauses that are commonly unenforceable. Each rule has a citation and source link.

NameTypeReqDescription
statestringyesTwo-letter US state code, e.g. CA, NY, TX

No output schema declared.

No examples provided.

Install

How do I install the RedFlagLease MCP server?

RedFlagLease is a hosted endpoint at https://redflaglease.com/api/leasecheck/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · redflaglease.com

# add to Claude Code
claude mcp add --transport http com-redflaglease-lease-checker 'https://redflaglease.com/api/leasecheck/mcp'
Common questions

What is the RedFlagLease MCP server?

RedFlagLease is an MCP server listed in the public MCP registry as com.redflaglease/lease-checker. Check US leases for red flags and look up verified state tenant law with statute citations. This page covers its hosted endpoint (https://redflaglease.com/api/leasecheck/mcp).

Is the RedFlagLease MCP server safe to use?

RedFlagLease scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the RedFlagLease MCP server expose?

RedFlagLease exposes 2 tools: tenant_law, check_lease. Their descriptions and schemas cost roughly 244 tokens of context every time the server is loaded.

Does the RedFlagLease MCP server require authentication?

No. We connected to RedFlagLease without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the RedFlagLease MCP server still maintained?

RedFlagLease is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.