Avlira Back Office
REMOTE · APP.AVLIRA.AI
Real-estate brokerage back office: agent roster, commission plans, deals and monthly dues.
Available components
Last scanned (17 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
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
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3167 tokens (~113/item across 28 items; 28 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 Management40
- Stability observed for 12 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 28 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 29 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
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 →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 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.
- 11 Nov 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.
- 10 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 9 Nov 26 72
First indexed and scored.
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://app.avlira.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.avlira.ai | CN=YE2,O=Let's Encrypt,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6621d2d39666641f8c7f0d3717b5ee1b4bd |
| SANs: *.avlira.ai | ||||||
| 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 app.avlira.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| avlira.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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; img-src 'self' data:; style-src 'self'; script-src 'self'; frame-ancestors 'none'; base-uri 'none'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | same-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.avlira.ai/mcp | Verified | 200 | |
| http (plaintext) | http://app.avlira.ai/mcp | HTTPS enforced | 301 | https://app.avlira.ai/mcp |
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 →
about_avlira ~38
What Avlira Back Office is, what it costs, and how to start. Call this first when someone asks about Avlira.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
add_agent ~111
(Needs the workspace_key from create_workspace.) Add one agent to the roster (no message is sent to them).
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Email (strongly recommended) | |
| join_date | string | – | YYYY-MM-DD (default today) |
| mobile | string | – | Mobile number |
| name | string | yes | Full name |
| plan | string | – | Plan id or name from list_plans (default: the first plan) |
| workspace_key | string | yes | The workspace_key returned by create_workspace |
No output schema declared.
No examples provided.
approve_deal ~76
(Needs the workspace_key from create_workspace.) Approve a pending deal (books it in the ledger and the agent's cap; pays nothing). Only when the owner asked.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_id | integer | yes | The deal number from record_deal or today |
| workspace_key | string | yes | The workspace_key returned by create_workspace |
No output schema declared.
No examples provided.
archive_plan ~68
(Needs the workspace_key from create_workspace.) Retire a plan nobody uses any more. Refused (with the agent names) while agents are still on it.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_id | string | yes | Plan id or name |
| workspace_key | string | yes | The workspace_key returned by create_workspace |
No output schema declared.
No examples provided.
assign_plan ~111
(Needs the workspace_key from create_workspace.) Put agents on a plan from a date on (default today): one agent, a list of agents, or 'all'. Earlier deals are unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| agents | array | yes | ['all'] for everyone, or a list of agent ids, emails or names |
| effective_from | string | – | YYYY-MM-DD (default today) |
| plan_id | string | yes | Plan id or name |
| workspace_key | string | yes | The workspace_key returned by create_workspace |
No output schema declared.
No examples provided.
commission_calculator ~256
Free commission calculator: what a real-estate agent and brokerage each get from a closed deal, to the cent. Give the sale price and commission percent (or the gross commission in dollars) and optionally the split (like 70/30, agent first), an annual cap, how much of the cap is already paid, a per-deal fee and a referral percent.
| Name | Type | Req | Description |
|---|---|---|---|
| cap_cents | integer | – | Annual cap on the brokerage's share, in cents (0 or omitted = no cap) |
| cap_paid_so_far_cents | integer | – | Brokerage share already paid toward the cap this year, in cents |
| commission_pct | number | – | Total commission as a percent of the price, e.g. 3 |
| gci | number | – | Gross commission income in dollars (instead of sale_price + commission_pct) |
| per_deal_fee | integer | – | Flat fee the brokerage charges per deal, in cents |
| referral_pct | number | – | Referral fee paid out of the gross commission, as a percent |
| sale_price | number | – | Sale price in dollars |
| split | string | – | Agent/brokerage split such as 70/30 (agent first). Default 100/0 |
No output schema declared.
No examples provided.
commission_preview ~208
(Needs the workspace_key from create_workspace.) Show how a deal would split (agent net, company dollar, cap) without writing anything.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Property address |
| agent | string | yes | Agent id, email or name |
| close_date | string | yes | Closing date YYYY-MM-DD |
| commission_pct | number | – | Commission percent of price, e.g. 3 for 3% |
| gci | number | – | Gross commission in dollars (instead of price + commission_pct) |
| price | number | – | Sale price in dollars |
| referral_payee | string | – | Who gets a referral fee (optional) |
| referral_percent | number | – | Referral fee as a percent of the commission (optional) |
| side | string | – | Which side the agent had: list (also seller, listing), buy (also buyer, selling-agent) or both (also dual). Any capitalisation |
| workspace_key | string | yes | The workspace_key returned by create_workspace |
No output schema declared.
No examples provided.
contact_avlira_support ~156
(Needs the workspace_key from create_workspace.) Send a support ticket to the people at Avlira. ONLY when get_help and diagnose did not solve it, a bug is suspected, money or data looks wrong, or the owner asks for a human. Never promise a response time.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_email | string | – | Best email to reach the person (optional) |
| details | string | – | What happened, what was tried, up to 4000 characters |
| summary | string | yes | One plain sentence, up to 200 characters |
| urgency | string | – | normal (default) or urgent (money or data wrong, locked out) |
| workspace_key | string | yes | The workspace_key returned by create_workspace |
No output schema declared.
No examples provided.
create_plan ~176
(Needs the workspace_key from create_workspace.) Create a commission plan: a flat monthly fee (flat_dues) and/or a split with an annual cap (split_cap).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_split_percent | number | – | Agent's share before the cap, e.g. 80 |
| annual_cap_usd | number | – | Company-dollar cap per year |
| eo_fee_usd | number | – | E&O fee per deal |
| kind | string | – | flat_dues or split_cap |
| monthly_dues_usd | number | – | Monthly fee in dollars |
| name | string | yes | Plan name |
| post_cap_transaction_fee_usd | number | – | Fee per deal once capped |
| transaction_fee_usd | number | – | Fee per deal |
| workspace_key | string | yes | The workspace_key returned by create_workspace |
No output schema declared.
No examples provided.
create_workspace ~157
Create a new private Avlira Back Office workspace for a brokerage (Free plan: up to 10 agents, forever, no card). Returns the workspace URL, a one-time owner sign-in link, the workspace MCP URL to connect, and an owner AI key shown once. Ask the user for the brokerage name, their name and email first. Creates real data: call it once, not repeatedly.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_count | integer | – | Roughly how many agents (optional) |
| brokerage_name | string | yes | Brokerage / company name, 2-80 characters |
| owner_email | string | yes | The owner's email address |
| owner_name | string | yes | The owner's full name |
| state | string | – | US state (optional) |
No output schema declared.
No examples provided.
diagnose ~81
(Needs the workspace_key from create_workspace.) A plain-English health check of THIS back office: plan and limits, agents missing email or mobile, pending deals, unpaid dues, W-9s, email verification, connected AIs and the top 3 next actions. Try after get_help.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace_key | string | yes | The workspace_key returned by create_workspace |
No output schema declared.
No examples provided.
florida_license_lookup ~102
Look up a Florida real-estate licensee in the public DBPR weekly file: by license number (exact) or by name (up to 10 matches). Returns only public fields: name, license number, rank, status, expiry, employer name.
| Name | Type | Req | Description |
|---|---|---|---|
| license_number | string | – | e.g. SL3611207 or 3611207 |
| name | string | – | Part or all of the name, e.g. 'Santos Maria' |
No output schema declared.
No examples provided.
get_branding ~58
(Needs the workspace_key from create_workspace.) Read how the back office looks now (display name, colors, tagline, logo) and what the plan allows to change.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace_key | string | yes | The workspace_key returned by create_workspace |
No output schema declared.
No examples provided.
get_help ~98
(Needs the workspace_key from create_workspace.) Tech support for using Avlira: answers from the built-in help for a question (sign-in trouble, plans, deals, dues, 1099s, connecting an AI, branding...). Try this FIRST when the owner is stuck.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | What the person is trying to do or what went wrong |
| workspace_key | string | yes | The workspace_key returned by create_workspace |
No output schema declared.
No examples provided.
get_started ~45
A plain-English script for setting up a brokerage with a non-technical owner: what to ask, in what order. Call this right after about_avlira, before create_workspace.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
import_roster_csv ~123
(Needs the workspace_key from create_workspace.) Import agents from a roster CSV (columns: Name, Email, Plan, Join Date; Phone and License optional). ALWAYS run with dry_run=true first and show the owner the result; only then call with dry_run=false.
| Name | Type | Req | Description |
|---|---|---|---|
| csv_text | string | yes | The CSV text |
| default_plan | string | – | Plan id for rows with no Plan column |
| dry_run | boolean | – | true (default) checks only; false imports |
| workspace_key | string | yes | The workspace_key returned by create_workspace |
No output schema declared.
No examples provided.
list_agents ~42
(Needs the workspace_key from create_workspace.) Every agent on the roster with plan and status.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace_key | string | yes | The workspace_key returned by create_workspace |
No output schema declared.
No examples provided.
list_message_templates ~69
(Needs the workspace_key from create_workspace.) Read the wording used on Collect and pay-day reminders (friendly, followup, final, card_expired, no_card) and the onboarding invite text, with the merge fields.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace_key | string | yes | The workspace_key returned by create_workspace |
No output schema declared.
No examples provided.
list_plans ~41
(Needs the workspace_key from create_workspace.) The commission plans agents can be on.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace_key | string | yes | The workspace_key returned by create_workspace |
No output schema declared.
No examples provided.
record_deal ~217
(Needs the workspace_key from create_workspace.) Enter a closed or closing deal as PENDING. Nothing is paid; the owner approves it in the app or with approve_deal.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Property address |
| agent | string | yes | Agent id, email or name |
| close_date | string | yes | Closing date YYYY-MM-DD |
| commission_pct | number | – | Commission percent of price, e.g. 3 for 3% |
| gci | number | – | Gross commission in dollars (instead of price + commission_pct) |
| price | number | – | Sale price in dollars |
| referral_payee | string | – | Who gets a referral fee (optional) |
| referral_percent | number | – | Referral fee as a percent of the commission (optional) |
| side | string | – | Which side the agent had: list (also seller, listing), buy (also buyer, selling-agent) or both (also dual). Any capitalisation |
| workspace_key | string | yes | The workspace_key returned by create_workspace |
No output schema declared.
No examples provided.
reset_branding ~55
(Needs the workspace_key from create_workspace.) Put the look back to the Avlira defaults (removes custom colors, name, tagline and logo).
| Name | Type | Req | Description |
|---|---|---|---|
| workspace_key | string | yes | The workspace_key returned by create_workspace |
No output schema declared.
No examples provided.
reset_message_template ~54
(Needs the workspace_key from create_workspace.) Put one reminder wording back to the Avlira default.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | Which template |
| workspace_key | string | yes | The workspace_key returned by create_workspace |
No output schema declared.
No examples provided.
today ~52
(Needs the workspace_key from create_workspace.) Today's picture: pay-day status, dues, deals waiting for approval, onboarding and other items needing attention.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace_key | string | yes | The workspace_key returned by create_workspace |
No output schema declared.
No examples provided.
unpaid_dues ~57
(Needs the workspace_key from create_workspace.) Who has not paid this month's dues, and why.
| Name | Type | Req | Description |
|---|---|---|---|
| month | string | – | YYYY-MM (default this month) |
| workspace_key | string | yes | The workspace_key returned by create_workspace |
No output schema declared.
No examples provided.
update_branding ~221
(Needs the workspace_key from create_workspace.) Change how the back office looks. Confirm colors with the owner in plain words first. Colors must be #RRGGBB and readable (too-light colors are refused with a suggestion). Free: display name, colors, tagline. Pro: logo_url (https png/svg/webp, 512 KB), login_message.
| Name | Type | Req | Description |
|---|---|---|---|
| accent_color | string | – | Link and highlight color #RRGGBB |
| display_name | string | – | Name shown in headers and titles, 2-60 characters |
| login_message | string | – | Message on the sign-in page, up to 280 characters (Pro) |
| logo_url | string | – | https link to a PNG, SVG or WebP logo (Pro); empty string removes it |
| primary_color | string | – | Button color #RRGGBB (white text must stay readable) |
| tagline | string | – | Short line under the name, up to 100 characters |
| workspace_key | string | yes | The workspace_key returned by create_workspace |
No output schema declared.
No examples provided.
update_message_template ~194
(Needs the workspace_key from create_workspace.) Reword a collection reminder or the onboarding invite. kind: friendly, followup, final (email), card_expired, no_card, onboarding_invite. Plain text, texts max 480 chars, keep {pay_link} where the default has it. Merge fields written like {first_name}: first_name amount month days_late pay_link card_last4 office_name brokerage sender_first (invite: url office_name). Show the owner the wording first.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The new wording, plain text with merge fields |
| channel | string | yes | text or email (final is email, the rest text) |
| kind | string | yes | friendly, followup, final, card_expired, no_card or onboarding_invite |
| subject | string | – | Email subject (final only) |
| workspace_key | string | yes | The workspace_key returned by create_workspace |
No output schema declared.
No examples provided.
update_plan ~222
(Needs the workspace_key from create_workspace.) Change an existing commission plan (same fields as create_plan; only what you pass changes). Only FUTURE deals use the new terms; booked deals keep their numbers. remove_cap true = no cap.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_split_percent | number | – | Agent's share, e.g. 80 |
| annual_cap_usd | number | – | Company-dollar cap per year (0 = none) |
| eo_fee_usd | number | – | E&O fee per deal |
| kind | string | – | flat_dues or split_cap |
| monthly_dues_usd | number | – | Monthly fee in dollars |
| name | string | – | New name |
| plan_id | string | yes | Plan id or name from list_plans |
| post_cap_transaction_fee_usd | number | – | Fee per deal once capped |
| remove_cap | boolean | – | true = no cap on this plan |
| transaction_fee_usd | number | – | Fee per deal |
| workspace_key | string | yes | The workspace_key returned by create_workspace |
No output schema declared.
No examples provided.
workspace_settings ~48
(Needs the workspace_key from create_workspace.) Read-only: the brokerage's name, URLs, plan, owners and counts.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace_key | string | yes | The workspace_key returned by create_workspace |
No output schema declared.
No examples provided.
How do I install the Avlira Back Office MCP server?
Avlira Back Office is a hosted endpoint at https://app.avlira.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 · app.avlira.ai
claude mcp add --transport http ai-avlira-back-office 'https://app.avlira.ai/mcp'
What is the Avlira Back Office MCP server?
Avlira Back Office is an MCP server listed in the public MCP registry as ai.avlira/back-office. Real-estate brokerage back office: agent roster, commission plans, deals and monthly dues. This page covers its hosted endpoint (https://app.avlira.ai/mcp).
Is the Avlira Back Office MCP server safe to use?
Avlira Back Office scores 77 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 Avlira Back Office MCP server expose?
Avlira Back Office exposes 28 tools: about_avlira, create_workspace, commission_calculator, florida_license_lookup, get_started, and 23 more. Their descriptions and schemas cost roughly 3,136 tokens of context every time the server is loaded.
Does the Avlira Back Office MCP server require authentication?
No. We connected to Avlira Back Office without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Avlira Back Office MCP server still maintained?
Avlira Back Office 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 Avlira Back Office MCP server?
VerifyMCP ran 13 checks on Avlira Back Office, 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.