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.

flatin.pt — Portuguese property taxes

REMOTE · FLATIN.PT · SCANNED SEP 25

Portuguese property taxes: IMT on purchase and IMI rates for all 308 municipalities

Available components

+5 this week 75 Trust /100
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 Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 689 tokens (~172/item across 4 items; 4 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 Management30
  • Stability observed for 9 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
Install

How do I install the flatin.pt — Portuguese property taxes MCP server?

flatin.pt — Portuguese property taxes is a hosted endpoint at https://flatin.pt/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 · flatin.pt

# add to Claude Code
claude mcp add --transport http pt-flatin-property-taxes 'https://flatin.pt/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "pt-flatin-property-taxes": {
      "url": "https://flatin.pt/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "pt-flatin-property-taxes": {
      "type": "http",
      "url": "https://flatin.pt/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.pt-flatin-property-taxes]
url = "https://flatin.pt/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pt-flatin-property-taxes": {
      "type": "remote",
      "url": "https://flatin.pt/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add pt-flatin-property-taxes --url 'https://flatin.pt/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  pt-flatin-property-taxes:
    url: "https://flatin.pt/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "pt-flatin-property-taxes": {
      "Transport": "http",
      "Url": "https://flatin.pt/mcp"
    }
  }
}
# add to Vellum
assistant mcp add pt-flatin-property-taxes -t streamable-http -u 'https://flatin.pt/mcp'
// mcp.json
{
  "mcpServers": {
    "pt-flatin-property-taxes": {
      "type": "http",
      "url": "https://flatin.pt/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 25 Sept 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
  • 24 Sept 26 +1

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

  • 22 Sept 26 +1

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

  • 20 Sept 26 +1

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

  • 19 Sept 26 +2
    • HSTS header: fail → pass ▲ security
  • 18 Sept 26 +1

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

  • 17 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 16 Sept 26 69

    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 25 Sept 2026 · Probed https://flatin.pt/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=flatin.pt CN=WE1,O=Google Trust Services,C=US 7 Sept 2026 6 Dec 2026 ECDSA 256 ECDSA-SHA256 b4eb9e83c52917113219b93b5bfb0c9
SANs: flatin.pt, *.flatin.pt
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of flatin.pt. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
pt. present 40155 13 Verified
flatin.pt. 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; includeSubDomains
content-security-policy default-src 'self'; script-src 'none'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://flatin.b-cdn.net; font-src 'self'; form-action 'self'; frame-ancestors 'none'; base-uri 'none'; object-src 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), camera=(), microphone=(), payment=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://flatin.pt/mcp Verified 200
http (plaintext) http://flatin.pt/mcp HTTPS enforced 301 https://flatin.pt/mcp
MCP tools · 4 exposed · ~583 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
imi_annual_cost ~125

Yearly IMI for an urban property (prédio urbano) with a given taxable value (VPT) in one municipality, at the municipality's urban rate. VPT is the tax authority's valuation, not the purchase price: ask the user for it instead of using the price.

NameTypeReqDescription
municipalitystringyesMunicipality name in Portuguese (Porto, Lisboa, Vila Nova de Gaia) or its four-digit code (1312)
vptstringyesValor Patrimonial Tributário — the taxable value of the property in euros. Not the purchase price

No output schema declared.

No examples provided.

imi_rate ~102

The yearly property tax (IMI) rate in one Portuguese municipality, by name or four-digit code. Collected from the Autoridade Tributária portal and checked line by line for all 308 municipalities. Where a municipality sets no single rate (it is set per parish), the answer says so instead of returning zero.

NameTypeReqDescription
municipalitystringyesMunicipality name in Portuguese (Porto, Lisboa, Vila Nova de Gaia) or its four-digit code (1312)

No output schema declared.

No examples provided.

imt_calculate ~266

What buying a home in Portugal costs on top of the price: IMT (property transfer tax), Imposto do Selo (stamp duty) and an estimate for the deed and registration. Official 2026 tables, including the reduced IMT table and the stamp duty deduction for buyers aged 35 or under. Returns amounts in cents and formatted in euros, with the source of the tables.

NameTypeReqDescription
buyer_is_youngboolean–The buyer is 35 or under on the date of the deed, is buying their first own permanent home, is not an IRS dependant and has owned no residential property in the previous three years. Applies the redu…
primary_homeboolean–The buyer's own permanent home (habitação própria e permanente). Default: true
territorystring–Mainland Portugal (continente) or the Azores and Madeira (regioes_autonomas). Default: continente
valuestringyesProperty price in euros, e.g. 250000 or 250000.50

No output schema declared.

No examples provided.

request_consultation ~90

How to put the user in touch with a licensed real estate agency in Portugal: returns the form link and the GDPR (RGPD) consent text in the user's language. The request is submitted by the person, not on their behalf.

NameTypeReqDescription
languagestring–The user's language: pt, en, ru, ua, de, fr, nl (uk is accepted too). Default: en

No output schema declared.

No examples provided.

Common questions

What is the flatin.pt — Portuguese property taxes MCP server?

flatin.pt — Portuguese property taxes is an MCP server listed in the public MCP registry as pt.flatin/property-taxes. Portuguese property taxes: IMT on purchase and IMI rates for all 308 municipalities. This page covers its hosted endpoint (https://flatin.pt/mcp).

Is the flatin.pt — Portuguese property taxes MCP server safe to use?

flatin.pt — Portuguese property taxes 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 flatin.pt — Portuguese property taxes MCP server expose?

flatin.pt — Portuguese property taxes exposes 4 tools: imt_calculate, imi_rate, imi_annual_cost, request_consultation. Their descriptions and schemas cost roughly 583 tokens of context every time the server is loaded.

Does the flatin.pt — Portuguese property taxes MCP server require authentication?

No. We connected to flatin.pt — Portuguese property taxes without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the flatin.pt — Portuguese property taxes MCP server still maintained?

flatin.pt — Portuguese property taxes is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.