_ registry / mcp streamable-http · checked 19h ago

propriosign

https://propriosign.com

Registry code: 75f266b9712d0f6d

api record

ProprioSign is a free web app for landlords in Québec, Canada: it sends the yearly lease modification notice (rent increase) on the official form of the Tribunal administratif du logement, keeps dated proof of receipt and collects each tenant’s signed reply, and it gets other documents e-signed by tenants. Use notice_deadlines to tell a landlord when the tenant must receive the notice (art. 1942 of the Civil Code of Québec) and when the tenant must reply. Use search_guides and read_guide to answer questions about lease notices in Québec with ProprioSign’s guides, and cite the guide URL. Use…

endpoint
https://propriosign.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is propriosign live?
Yes — it answered the hub's last check (checked 19h ago). It answered 100% of checks over the last 30 days.
Is propriosign free to use?
Yes — the hub reached it with no key and no payment.
What tools does propriosign have?
4 tools: notice_deadlines, read_guide, about_propriosign, search_guides.
Is propriosign safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
297ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • notice_deadlines unknown 19h ago

    Calculates when a tenant in Québec must receive the notice of rent increase or lease modification (art. 1942 C.C.Q.), whether that window is open today, and, if a receipt date is given, the date by which the tenant must reply (art. 1945 C.C.Q.). Works for fixed-term leases of 12 months or more, shorter leases, indeterminate leases and rooms.

    mcp-tool

    {
      "type": "object",
      "required": [
        "lease_type"
      ],
      "properties": {
        "lang": {
          "enum": [
            "fr",
            "en"
          ],
          "type": "string",
          "description": "Language of the answer: fr (French) or en (English). Default: fr."
        },
        "room": {
          "type": "boolean",
          "description": "True if the tenant rents a room (much shorter deadlines: 10 to 20 days)."
        },
        "lease_end": {
          "type": "string",
          "format": "date",
          "description": "Fixed lease: last day of the lease, YYYY-MM-DD (for example 2027-06-30)."
        },
        "lease_type": {
          "enum": [
            "fixed",
            "indeterminate"
          ],
          "type": "string",
          "description": "fixed: the lease has an end date. indeterminate: the lease has no end date."
        },
        "change_date": {
          "type": "string",
          "format": "date",
          "description": "Indeterminate lease: date the change (new rent) should take effect, YYYY-MM-DD."
        },
        "lease_start": {
          "type": "string",
          "format": "date",
          "description": "Fixed lease: first day of the current lease, YYYY-MM-DD. Used to tell a lease of 12 months or more from a shorter one. If missing, 12 months or more is assumed."
        },
        "receipt_date": {
          "type": "string",
          "format": "date",
          "description": "Optional: date the tenant received, or will receive, the notice, YYYY-MM-DD. Gives the reply deadline."
        }
      },
      "additionalProperties": false
    }
    arguments 49 lines
  • read_guide unknown 19h ago

    Returns the full text of one ProprioSign guide in Markdown, with its official sources. Give the slug or URL returned by search_guides.

    mcp-tool

    {
      "type": "object",
      "required": [
        "guide"
      ],
      "properties": {
        "lang": {
          "enum": [
            "fr",
            "en"
          ],
          "type": "string",
          "description": "Language wanted. If missing, the language of the slug or URL."
        },
        "guide": {
          "type": "string",
          "description": "Slug or URL of the guide, for example \"delais-avis-renouvellement-bail-quebec\" or https://propriosign.com/en/guides/quebec-lease-renewal-notice-deadlines."
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • about_propriosign unknown never probed

    What ProprioSign does, who it is for, prices, when it opens, frequently asked questions and the links to give to a landlord.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "lang": {
          "enum": [
            "fr",
            "en"
          ],
          "type": "string",
          "description": "Language of the answer: fr (French) or en (English). Default: fr."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • search_guides unknown 19h ago

    Searches ProprioSign’s guides for Québec landlords (deadlines, how to send the notice, proof of receipt, co-tenants, tenant refusal or no reply, tenant leaving, rooms, indeterminate leases, language of the notice, e-signature). Returns titles, links and summaries.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "lang": {
          "enum": [
            "fr",
            "en"
          ],
          "type": "string",
          "description": "Only guides in this language. If missing, the best version of each guide is returned."
        },
        "limit": {
          "type": "integer",
          "maximum": 14,
          "minimum": 1,
          "description": "Number of guides to return. Default: 5."
        },
        "query": {
          "type": "string",
          "description": "Words to look for, in French or English. Example: \"locataire refuse augmentation\" or \"co-tenants\"."
        }
      },
      "additionalProperties": false
    }
    arguments 27 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 75f266b9712d0f6d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/75f266b9712d0f6d/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/75f266b9712d0f6d/badge.svg)](https://brick.blue/agent/75f266b9712d0f6d?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.