DoorLoop MCP by usefulapi
REMOTE · DOORLOOP.USEFULAPI.IO
Read DoorLoop properties, units, leases, tenants and payments; create tasks and task updates.
Available components
Last scanned (3 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 6 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
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.
- 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
- 2 Nov 26 −47
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 64
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 6 Nov 2026 · Probed https://doorloop.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| 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 doorloop.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://doorloop.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/doorloop/ |
| http (plaintext) | http://doorloop.usefulapi.io/mcp | Inconclusive | 302 | http://doorloop.usefulapi.io/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 →
doorloop_create_task Create a task ~270
WRITE: create a task in DoorLoop. INTERNAL_TASK needs requested_by_user, TENANT_REQUEST needs requested_by_tenant, OWNER_REQUEST needs requested_by_owner, WORK_ORDER needs assigned_to_vendor. Notifications are off unless you set them. Each call creates a new task. DoorLoop API: POST /tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_to_users | array | – | User ids to assign. |
| assigned_to_vendor | string | – | Vendor id. Required for WORK_ORDER. |
| description | string | – | – |
| due_date | string | – | Due date (yyyy-mm-dd). |
| instructions_to_vendor | string | – | – |
| notify_assignees | boolean | – | Notify the assigned users. Default: no. |
| notify_tenant | boolean | – | Notify the tenant (TENANT_REQUEST only). Default: no. |
| priority | string | – | – |
| property | string | – | Property id. |
| requested_by_owner | string | – | Owner id. Required for OWNER_REQUEST. |
| requested_by_tenant | string | – | Tenant id. Required for TENANT_REQUEST. |
| requested_by_user | string | – | User id. Required for INTERNAL_TASK. |
| status | string | yes | Initial status. |
| subject | string | yes | Task subject. |
| type | string | yes | – |
| unit | string | – | Unit id. |
No output schema declared.
No examples provided.
doorloop_get_current_user Get current user ~39
Get the DoorLoop user that created this API key. Good first call to confirm the connection. DoorLoop API: GET /users/me.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
doorloop_get_lease Get a lease ~45
Get one lease by id. DoorLoop API: GET /leases/{leaseId}.
| Name | Type | Req | Description |
|---|---|---|---|
| lease_id | string | yes | The lease_id (from the matching list tool). |
No output schema declared.
No examples provided.
doorloop_get_property Get a property ~44
Get one property by id. DoorLoop API: GET /properties/{propertyId}.
| Name | Type | Req | Description |
|---|---|---|---|
| property_id | string | yes | The property_id (from the matching list tool). |
No output schema declared.
No examples provided.
doorloop_get_task Get a task ~44
Get one task by id. DoorLoop API: GET /tasks/{taskId}.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | The task_id (from the matching list tool). |
No output schema declared.
No examples provided.
doorloop_get_tenant Get a tenant ~46
Get one tenant by id. DoorLoop API: GET /tenants/{tenantId}.
| Name | Type | Req | Description |
|---|---|---|---|
| tenant_id | string | yes | The tenant_id (from the matching list tool). |
No output schema declared.
No examples provided.
doorloop_get_unit Get a unit ~44
Get one unit by id. DoorLoop API: GET /units/{unitId}.
| Name | Type | Req | Description |
|---|---|---|---|
| unit_id | string | yes | The unit_id (from the matching list tool). |
No output schema declared.
No examples provided.
doorloop_list_accounts List accounts ~131
List chart-of-accounts entries. DoorLoop API: GET /accounts.
| Name | Type | Req | Description |
|---|---|---|---|
| leaseChargeItem | boolean | – | Only lease charge items. |
| page_number | integer | – | Page number (default 1). |
| page_size | integer | – | Results per page (default 50, max 1000). |
| sort_by | string | – | Field name of the resource to sort by, for example createdAt. |
| sort_descending | boolean | – | Sort in descending order (default false). |
| type | string | – | Account type, for example REVENUE_INCOME or EXPENSE_EXPENSE. |
No output schema declared.
No examples provided.
doorloop_list_lease_charges List lease charges ~225
List charges (rent, fees, late fees) billed on leases. Use totalBalanceGreaterThan to find unpaid charges. DoorLoop API: GET /lease-charges.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Charge date from (yyyy-mm-dd). |
| date_to | string | – | Charge date to (yyyy-mm-dd). |
| lateFeeCharges | boolean | – | Only late-fee charges. |
| lease | string | – | Filter by lease id. |
| owner | string | – | Filter by owner id. |
| page_number | integer | – | Page number (default 1). |
| page_size | integer | – | Results per page (default 50, max 1000). |
| property | string | – | Filter by property id. |
| sort_by | string | – | Field name of the resource to sort by, for example createdAt. |
| sort_descending | boolean | – | Sort in descending order (default false). |
| totalBalanceGreaterThan | number | – | Only charges with a remaining balance above this amount. |
| unit | string | – | Filter by unit id. |
No output schema declared.
No examples provided.
doorloop_list_lease_payments List lease payments ~164
List rent payments received on leases. DoorLoop API: GET /lease-payments.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Payment date from (yyyy-mm-dd). |
| date_to | string | – | Payment date to (yyyy-mm-dd). |
| lease | string | – | Filter by lease id. |
| owner | string | – | Filter by owner id. |
| page_number | integer | – | Page number (default 1). |
| page_size | integer | – | Results per page (default 50, max 1000). |
| property | string | – | Filter by property id. |
| sort_by | string | – | Field name of the resource to sort by, for example createdAt. |
| sort_descending | boolean | – | Sort in descending order (default false). |
No output schema declared.
No examples provided.
doorloop_list_lease_tenants List lease tenants ~210
List tenants joined to their leases, with move-in and move-out dates. Best way to map tenants to leases. DoorLoop API: GET /leases/tenants.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | Filter by portfolio id. |
| lease | string | – | Filter by lease id. |
| movedInAt_from | string | – | Move-in date from (yyyy-mm-dd). |
| movedInAt_to | string | – | Move-in date to (yyyy-mm-dd). |
| page_number | integer | – | Page number (default 1). |
| page_size | integer | – | Results per page (default 50, max 1000). |
| property | string | – | Filter by property id. |
| sort_by | string | – | Field name of the resource to sort by, for example createdAt. |
| sort_descending | boolean | – | Sort in descending order (default false). |
| status | string | – | Occupancy status. |
| text | string | – | Filter by tenant name or email. |
No output schema declared.
No examples provided.
doorloop_list_leases List leases ~339
List leases with dates, rent, status and outstanding balance. Use calculatedStatus or situation to find at-risk or late leases. DoorLoop API: GET /leases.
| Name | Type | Req | Description |
|---|---|---|---|
| calculatedStatus | string | – | Collections stage. |
| end_date_from | string | – | Lease end date from (yyyy-mm-dd). |
| end_date_to | string | – | Lease end date to (yyyy-mm-dd). |
| evictionPending | boolean | – | Only leases with a pending eviction. |
| group | string | – | Filter by portfolio id. |
| outstandingBalanceGreaterThan | number | – | Only leases with an outstanding balance above this amount. |
| owner | string | – | Filter by owner id. |
| page_number | integer | – | Page number (default 1). |
| page_size | integer | – | Results per page (default 50, max 1000). |
| property | string | – | Filter by property id. |
| propertyClass | string | – | Filter by property class. |
| situation | string | – | Lease situation from balance and lifecycle. |
| sort_by | string | – | Field name of the resource to sort by, for example createdAt. |
| sort_descending | boolean | – | Sort in descending order (default false). |
| start_date_from | string | – | Lease start date from (yyyy-mm-dd). |
| start_date_to | string | – | Lease start date to (yyyy-mm-dd). |
| status | string | – | Filter by lease status. |
| tenant | string | – | Filter by tenant id. |
| term | string | – | Filter by lease term. |
| text | string | – | Filter by lease name. |
| unit | string | – | Filter by unit id. |
No output schema declared.
No examples provided.
doorloop_list_owners List owners ~141
List property owners. DoorLoop API: GET /owners.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Filter by active or inactive. |
| group | string | – | Filter by portfolio id. |
| page_number | integer | – | Page number (default 1). |
| page_size | integer | – | Results per page (default 50, max 1000). |
| property | string | – | Filter by property id. |
| sort_by | string | – | Field name of the resource to sort by, for example createdAt. |
| sort_descending | boolean | – | Sort in descending order (default false). |
| text | string | – | Filter by owner name or email. |
No output schema declared.
No examples provided.
doorloop_list_portfolios List portfolios ~98
List portfolios (property groups). DoorLoop API: GET /property-groups.
| Name | Type | Req | Description |
|---|---|---|---|
| page_number | integer | – | Page number (default 1). |
| page_size | integer | – | Results per page (default 50, max 1000). |
| sort_by | string | – | Field name of the resource to sort by, for example createdAt. |
| sort_descending | boolean | – | Sort in descending order (default false). |
No output schema declared.
No examples provided.
doorloop_list_properties List properties ~146
List properties (buildings) with address, class and portfolio. DoorLoop API: GET /properties.
| Name | Type | Req | Description |
|---|---|---|---|
| class | string | – | Filter by property class. |
| group | string | – | Filter by portfolio id. |
| owner | string | – | Filter by owner id. |
| page_number | integer | – | Page number (default 1). |
| page_size | integer | – | Results per page (default 50, max 1000). |
| sort_by | string | – | Field name of the resource to sort by, for example createdAt. |
| sort_descending | boolean | – | Sort in descending order (default false). |
| text | string | – | Filter by property name. |
No output schema declared.
No examples provided.
doorloop_list_tasks List tasks ~250
List tasks, work orders, tenant requests and owner requests. DoorLoop API: GET /tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| assignedToUser | string | – | Filter by user id or "unassigned". |
| createdAt_from | string | – | Created from (yyyy-mm-dd). |
| createdAt_to | string | – | Created to (yyyy-mm-dd). |
| dueDate_from | string | – | Due date from (yyyy-mm-dd). |
| dueDate_to | string | – | Due date to (yyyy-mm-dd). |
| page_number | integer | – | Page number (default 1). |
| page_size | integer | – | Results per page (default 50, max 1000). |
| property | string | – | Filter by property id. |
| propertyGroup | string | – | Filter by portfolio id. |
| sort_by | string | – | Field name of the resource to sort by, for example createdAt. |
| sort_descending | boolean | – | Sort in descending order (default false). |
| status | string | – | Filter by task status. |
| text | string | – | Filter by subject, description or reference. |
| type | string | – | Filter by task type. |
| unit | string | – | Filter by unit id. |
No output schema declared.
No examples provided.
doorloop_list_tenants List tenants ~167
List tenants and prospects with contact details. DoorLoop API: GET /tenants.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | Filter by portfolio id. |
| lease | string | – | Filter by lease id. |
| page_number | integer | – | Page number (default 1). |
| page_size | integer | – | Results per page (default 50, max 1000). |
| property | string | – | Filter by property id. |
| sort_by | string | – | Field name of the resource to sort by, for example createdAt. |
| sort_descending | boolean | – | Sort in descending order (default false). |
| text | string | – | Filter by tenant name or email. |
| type | string | – | Filter by tenant type. |
| unit | string | – | Filter by unit id. |
No output schema declared.
No examples provided.
doorloop_list_units List units ~166
List rental units with rent, bedrooms and status. Without filter_active the API returns active units only. DoorLoop API: GET /units.
| Name | Type | Req | Description |
|---|---|---|---|
| active | string | – | Which units to return by status. |
| group | string | – | Filter by portfolio id. |
| owner | string | – | Filter by owner id. |
| page_number | integer | – | Page number (default 1). |
| page_size | integer | – | Results per page (default 50, max 1000). |
| property | string | – | Filter by property id. |
| sort_by | string | – | Field name of the resource to sort by, for example createdAt. |
| sort_descending | boolean | – | Sort in descending order (default false). |
| text | string | – | Filter by unit name. |
No output schema declared.
No examples provided.
doorloop_list_users List users ~97
List DoorLoop users of the company. DoorLoop API: GET /users.
| Name | Type | Req | Description |
|---|---|---|---|
| page_number | integer | – | Page number (default 1). |
| page_size | integer | – | Results per page (default 50, max 1000). |
| sort_by | string | – | Field name of the resource to sort by, for example createdAt. |
| sort_descending | boolean | – | Sort in descending order (default false). |
No output schema declared.
No examples provided.
doorloop_list_vendors List vendors ~148
List maintenance vendors. DoorLoop API: GET /vendors.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Filter by active or inactive. |
| insurance_expires_before | string | – | Insurance expires before (yyyy-mm-dd). |
| openBalance | boolean | – | Only vendors with an open balance. |
| page_number | integer | – | Page number (default 1). |
| page_size | integer | – | Results per page (default 50, max 1000). |
| property | string | – | Filter by property id. |
| sort_by | string | – | Field name of the resource to sort by, for example createdAt. |
| sort_descending | boolean | – | Sort in descending order (default false). |
No output schema declared.
No examples provided.
doorloop_post_task_update Post an update on a task ~160
WRITE: post a message on an existing task and optionally change its status, priority, due date or assignees. Each call adds a new update. Notifications are off unless you set them. DoorLoop API: POST /tasks/update.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_to_users | array | – | User ids to assign. |
| due_date | string | – | New due date (yyyy-mm-dd). |
| message | string | yes | Update message. |
| notify_assignees | boolean | – | Notify the assigned users. Default: no. |
| notify_tenant | boolean | – | Notify the tenant. Default: no. |
| priority | string | – | – |
| status | string | – | – |
| task_id | string | yes | Task id (from doorloop_list_tasks). |
No output schema declared.
No examples provided.
How do I install the DoorLoop MCP by usefulapi server?
DoorLoop MCP by usefulapi is a hosted endpoint at https://doorloop.usefulapi.io/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 · doorloop.usefulapi.io
claude mcp add --transport http io-usefulapi-doorloop 'https://doorloop.usefulapi.io/mcp'
What is the DoorLoop MCP by usefulapi server?
DoorLoop MCP by usefulapi is listed in the public MCP registry as io.usefulapi/doorloop. Read DoorLoop properties, units, leases, tenants and payments; create tasks and task updates. This page covers its hosted endpoint (https://doorloop.usefulapi.io/mcp).
Is the DoorLoop MCP by usefulapi server safe to use?
DoorLoop MCP by usefulapi scores 18 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 DoorLoop MCP by usefulapi server expose?
DoorLoop MCP by usefulapi exposes 21 tools: doorloop_get_current_user, doorloop_list_properties, doorloop_get_property, doorloop_list_units, doorloop_get_unit, and 16 more. Their descriptions and schemas cost roughly 2,974 tokens of context every time the server is loaded.
Does the DoorLoop MCP by usefulapi server require authentication?
Its publisher declares no required credentials for DoorLoop MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the DoorLoop MCP by usefulapi server still maintained?
DoorLoop MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 6 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 DoorLoop MCP by usefulapi server?
VerifyMCP ran 4 checks on DoorLoop MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about DoorLoop MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.