Home / MCP registry index / io.github.Payotte-com/payotte-mcp

io.github.Payotte-com/payotte-mcp

io.github.Payotte-com/payotte-mcp in the official MCP registry. Endpoint https://payotte-mcp.payotte.workers.dev/mcp. Source: github.com/Payotte-com/payotte-mcp.

The registry describes it as: Verified Canadian real-estate pros + housing data: rates, transfer tax, rent-vs-buy, QC assessments.

We read its 88 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http payotte-mcp https://payotte-mcp.payotte.workers.dev/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "payotte-mcp": {
      "url": "https://payotte-mcp.payotte.workers.dev/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"payotte-mcp","type":"http","url":"https://payotte-mcp.payotte.workers.dev/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

evaluation_adresse taxe_bienvenue_adresse risques_annee_construction trouver_expert verifier_titre stats_marche taux_courants taxe_mutation acheter_ou_louer salaire_requis contacter_expert fenetre_revision frais_revision estimer_economie frais_notaire_fr stats_marche_fr trouver_professionnel_fr verifier_titre_fr transfer_tax_us property_tax_us property_tax_appeal_us attorney_at_closing_us foreclosure_us seller_disclosure_us closing_costs_us first_time_buyer_programs_us home_prices_us community_property_us title_insurance_us natural_hazards_us verify_license_us compare_states_us state_overview_us find_property_owner_us federal_guide_us purchase_tax_uk house_prices_uk compare_nations_uk guide_uk check_professional_uk purchase_duty_au house_prices_au compare_states_au guide_au check_professional_au stamp_duty_in home_loan_emi_in house_prices_in compare_states_in guide_in check_professional_in purchase_costs_br mortgage_payment_br capital_gains_tax_br compare_states_br guide_br check_professional_br closing_costs_mx mortgage_payment_mx home_prices_mx and 28 more

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-payotte-com-payotte-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-payotte-com-payotte-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.