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.

ai.agentlookups/overassessed

REMOTE · OVERASSESSED.AGENTLOOKUPS.AI

Maryland property-assessment fairness checks vs similar homes, with appeal windows and links.

0 this week 79 Trust /100

Last scanned (20 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

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 Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability52
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1852 tokens (~1852/item across 1 items; 1 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 7 Nov 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: excellent → good functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “check_assessment” rewrote its description, which is the text the model reads security
    • Schema quality: 1394 → 1852 ▼ functional
    • “check_assessment” reworded the description of “acct” cosmetic
    • “check_assessment” reworded the description of “address” cosmetic
  • 27 Oct 26 0
    • Tool “check_assessment” rewrote its description, which is the text the model reads security
    • Schema quality: 903 → 1394 ▼ functional
    • “check_assessment” reworded the description of “acct” cosmetic
    • “check_assessment” reworded the description of “address” cosmetic
    • “check_assessment” reworded the description of “zip” cosmetic
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 21 Nov 2026 · Probed https://overassessed.agentlookups.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=overassessed.agentlookups.ai CN=YR1,O=Let's Encrypt,C=US 7 Oct 2026 5 Jan 2027 RSA 2048 SHA256-RSA 6b28d79837942b709da72129bbf7cca3604
SANs: overassessed.agentlookups.ai
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of overassessed.agentlookups.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
agentlookups.ai. No DS 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
referrer-policy no-referrer

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://overassessed.agentlookups.ai/mcp Verified 200
http (plaintext) http://overassessed.agentlookups.ai/mcp HTTPS enforced 301 https://overassessed.agentlookups.ai/mcp
MCP tools · 1 exposed · ~1,707 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_assessment ~1,707

Fairness check for one Maryland property assessment against genuinely similar homes (same triennial reassessment group, similar size, lot and age, same zip), from a copy of the state's own assessment roll (SDAT) refreshed monthly. Input is a Maryland street address with its zip, its Maryland city or county, or MD, or an SDAT account id (acct); the city, county, state and zip can be written in the address itself (1 STATE CIR, ANNAPOLIS, MD 21401), a city or county narrows the match to that place the way a zip does, and MD alone matches the street across the whole state. A single match returns the parcel record, a uniformity object, a plain-language verdict, Maryland's appeal windows with official filing links, and honesty notes. In the parcel record, market_value is the full value an appeal argues about; taxable_now is the phased-in assessment for the Maryland tax year holding today (tax years run July 1 to June 30; taxable_now_tax_year gives its from and to dates, YYYY-MM-DD), and taxable_next with taxable_next_tax_year is the one for the tax year after; either pair is left out when the roll does not hold that year. The uniformity object gives BandSize (how many similar homes), where the assessment sits among them as percentiles (PctFMV for market value, PctImprPSF for improvement value per square foot, PctLand for land value), their medians (MedianFMV, MedianImprPSF, MedianLand), the median sales ratio of assessment to sale price (MedianSalesRatio) and its coefficient of dispersion (COD) over RatioSales sales dated RatioFromYear through RatioToYear (three calendar years ending with the year of the roll's newest sale dated on or before today), and Branch. RatioSales counts sales of $100,000 or more that the roll codes as arm's-length sales of one improved parcel; foreclosures, gifts, auctions, sales of several parcels for one price and sales of a vacant lot are left out. When the roll records no lot size or no year built for the home, the band skips that test: NotC…

NameTypeReqDescription
acctstring–SDAT account id as returned in parcel.account_id or in a multiple_matches result: letters and digits (e.g. 020600002182004), with one space before the lot in Baltimore City (e.g. 0304121302 001); spa…
addressstring–Maryland street address in the form the roll uses (e.g. 1 STATE CIR), with any unit after the street (100 HARBORVIEW DR UNIT 204), followed by its Maryland city or county, the state, or the zip (e.g.…
zipstring–5-digit zip; a ZIP+4 is read as its first five digits, and a whole JSON number up to 99999 is read as a zip with its leading zeros restored (1234 is 01234). Optional when the address carries a Maryla…

No output schema declared.

No examples provided.

Install

How do I install the ai.agentlookups/overassessed MCP server?

ai.agentlookups/overassessed is a hosted endpoint at https://overassessed.agentlookups.ai/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 · overassessed.agentlookups.ai

# add to Claude Code
claude mcp add --transport http ai-agentlookups-overassessed 'https://overassessed.agentlookups.ai/mcp'
Common questions

What is the ai.agentlookups/overassessed MCP server?

ai.agentlookups/overassessed is an MCP server listed in the public MCP registry as ai.agentlookups/overassessed. Maryland property-assessment fairness checks vs similar homes, with appeal windows and links. This page covers its hosted endpoint (https://overassessed.agentlookups.ai/mcp).

Is the ai.agentlookups/overassessed MCP server safe to use?

ai.agentlookups/overassessed scores 79 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 ai.agentlookups/overassessed MCP server expose?

ai.agentlookups/overassessed exposes 1 tool: check_assessment. Their descriptions and schemas cost roughly 1,707 tokens of context every time the server is loaded.

Does the ai.agentlookups/overassessed MCP server require authentication?

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

Is the ai.agentlookups/overassessed MCP server still maintained?

ai.agentlookups/overassessed is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the ai.agentlookups/overassessed MCP server?

VerifyMCP ran 13 checks on ai.agentlookups/overassessed, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.