Rex Software MCP by usefulapi
REMOTE · REX-SOFTWARE.USEFULAPI.IO
Read contacts, listings, tenancies and tasks; create a person contact, note or reminder.
Available components
Last scanned (10 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 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.
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.
- 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 5 Nov 2026 · Probed https://rex-software.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 rex-software.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | 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://rex-software.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/rex-software/ |
| http (plaintext) | http://rex-software.usefulapi.io/mcp | Inconclusive | 302 | http://rex-software.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 →
rex_autocomplete_contacts Find contacts by name ~89
Quick lookup of contacts by (part of) a name: returns the best matches with id, name, email and phone. Use the id with rex_get_contact. POST /v1/rex/Contacts/autocomplete.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Matches to return, 1-50 (default 10). |
| search_string | string | yes | Part of the contact's or company's name. |
No output schema declared.
No examples provided.
rex_autocomplete_listings Find listings by address ~125
Quick lookup of listings by (part of) an address: returns the best matches with listing id and address. Use the id with rex_get_listing. POST /v1/rex/Listings/autocomplete.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Matches to return, 1-50 (default 10). |
| listing_states | array | – | Only listings in these states, for example ["current"] (see rex_get_value_list listing_system_state). |
| search_string | string | yes | Part of the property address, for example '12 Smith St' or 'Subiaco'. |
No output schema declared.
No examples provided.
rex_create_contact Create a person contact ~130
WRITE: create a new person contact in Rex with a name and optionally one email and one phone. Search first (rex_autocomplete_contacts) to avoid duplicates. Not retried. Returns the new contact id. POST /v1/rex/Contacts/create.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Primary email address. | |
| first_name | string | yes | First name. |
| last_name | string | yes | Last name. |
| phone | string | – | Primary phone number. |
| phone_type | string | – | Phone type id from the value list (for example mobile, home or work); omit to let Rex choose. |
No output schema declared.
No examples provided.
rex_create_note Create a note ~137
WRITE: add a note to one or more contacts and/or properties (for example after a call or an open home). Not retried. Returns the new note id. POST /v1/rex/Notes/create.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_ids | array | – | Contacts the note is about. |
| note | string | yes | The note text. |
| note_type | string | – | Note type id from the value list (for example phonecall); omit to use Rex's default. |
| property_ids | array | – | Properties the note is about. |
| update_last_contacted | boolean | – | Also set the contacts' last-contacted date to today. |
No output schema declared.
No examples provided.
rex_create_reminder Create a reminder ~206
WRITE: create a follow-up reminder (task) due on a date, optionally linked to a contact, property or listing and assigned to a user (default: Rex's default remindee). Not retried. Returns the new reminder id. POST /v1/rex/Reminders/create.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | – | Contact id to link. |
| date | string | yes | Due date, yyyy-mm-dd. |
| description | string | yes | What to do, for example 'Call Will about the appraisal'. |
| listing_id | integer | – | Listing id to link. |
| priority | string | – | Priority id from the value list (for example high). |
| property_id | integer | – | Property id to link. |
| remindee_user_id | integer | – | The Rex user id to remind (from rex_search_users); omit for the default. |
| reminder_type | string | – | Reminder type id from the value list (for example email); omit to use Rex's default. |
No output schema declared.
No examples provided.
rex_describe_search_fields List the search fields of a Rex service ~192
The field names a search on the given service accepts in criteria, each with its label, type and (for enums) the value list. Call this before building criteria on a field you are not sure of. Sorting (order_by) uses a separate list of sortable fields whose names can differ (for example name_last, not contact.name_last): set include_order_by to get it. POST /v1/rex/<Service>/describeSearchFields (and <Service>/describeModel for include_order_by).
| Name | Type | Req | Description |
|---|---|---|---|
| include_order_by | boolean | – | Also return the service's model description, which lists the fields order_by accepts (they can differ from the search field names). |
| match | string | – | Only fields whose name or label contains this text (case-insensitive). The big services have hundreds of fields, so filter. |
| service | string | yes | The Rex service, for example Contacts or Listings. |
No output schema declared.
No examples provided.
rex_get_appraisal Get an appraisal ~59
One appraisal by id (date, state, agents, property, price expectations and commission estimate). The id comes from a search or autocomplete. POST /v1/rex/Appraisals/read.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The appraisal id. |
No output schema declared.
No examples provided.
rex_get_contact Get a contact ~102
One contact by id (names, emails, phones, addresses, tags, relationships and the related properties and listings). The id comes from a search or autocomplete. POST /v1/rex/Contacts/read.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Limit the reply to these parts of the record ("core" is always included; related data is "related.<name>"). Omit for the whole record, which is large. |
| id | integer | yes | The contact id. |
No output schema declared.
No examples provided.
rex_get_deal Get a deal ~54
One deal by id (state, value, parties and expected close date). The id comes from a search or autocomplete. POST /v1/rex/Deals/read.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The deal id. |
No output schema declared.
No examples provided.
rex_get_lead Get a lead ~58
One lead by id (contact, source, status, assignee and the original enquiry). The id comes from a search or autocomplete. POST /v1/rex/Leads/read.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The lead id. |
No output schema declared.
No examples provided.
rex_get_listing Get a listing ~103
One listing by id (state, price, agents, the property with its attributes, images, related contacts and events). The id comes from a search or autocomplete. POST /v1/rex/Listings/read.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Limit the reply to these parts of the record ("core" is always included; related data is "related.<name>"). Omit for the whole record, which is large. |
| id | integer | yes | The listing id. |
No output schema declared.
No examples provided.
rex_get_note Get a note ~56
One note by id (text, type and the contacts and properties it is linked to). The id comes from a search or autocomplete. POST /v1/rex/Notes/read.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The note id. |
No output schema declared.
No examples provided.
rex_get_property Get a property ~105
One property by id (address, attributes (bedrooms, land area and so on), features, owners and the property's history). The id comes from a search or autocomplete. POST /v1/rex/Properties/read.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Limit the reply to these parts of the record ("core" is always included; related data is "related.<name>"). Omit for the whole record, which is large. |
| id | integer | yes | The property id. |
No output schema declared.
No examples provided.
rex_get_reminder Get a reminder ~58
One reminder by id (description, date, remindee, completion state and linked records). The id comes from a search or autocomplete. POST /v1/rex/Reminders/read.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The reminder id. |
No output schema declared.
No examples provided.
rex_get_tenancy Get a tenancy ~55
One tenancy by id (property, tenants, lease dates and rent). The id comes from a search or autocomplete. POST /v1/rex/Tenancies/read.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | The tenancy id. |
No output schema declared.
No examples provided.
rex_get_user_profile Get the signed-in Rex user ~52
The Rex user this server is signed in as: user id, name, email, whether they own the account, position and default office. Good first call. POST /v1/rex/UserProfile/read.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rex_get_value_list Get the values of a Rex value list ~65
The allowed values (id and label) of one value list, for example property_category. The ids are what writes and criteria expect. POST /v1/rex/SystemValues/getCategoryValues.
| Name | Type | Req | Description |
|---|---|---|---|
| list_name | string | yes | The list name from rex_list_value_lists. |
No output schema declared.
No examples provided.
rex_list_accessible_accounts List the Rex accounts the user can access ~55
The Rex agency accounts (account_id and name) this user can sign in to. A user with several accounts picks one with the Account id field when connecting. POST /v1/rex/UserProfile/getAccessibleAccounts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rex_list_value_lists List the Rex value lists ~58
The names of Rex's value lists (the allowed ids for fields such as note types, reminder types, lead sources and property categories). Use a name with rex_get_value_list. POST /v1/rex/SystemValues/getValueCategories.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rex_search_activities Search activities ~230
Search activities (the log of calls, emails and other actions on records). Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). Useful fields: parent_object_type, parent_object_id, type_id, system_ctime, system_created_user_id. POST /v1/rex/Activities/search.
| Name | Type | Req | Description |
|---|---|---|---|
| criteria | array | – | Filters, combined with AND: [{ name, type?, value }]. Only the in type gives an OR. Field names come from rex_describe_search_fields. |
| limit | integer | – | Rows to return, 1-100 (default 20). |
| offset | integer | – | Rows to skip (default 0). Use next_offset from the previous reply. |
| order_by | object | – | Sort, sortable field name to direction, for example { "system_modtime": "DESC" }. Sortable names can differ from search field names (rex_describe_search_fields with include_order_by lists them). |
| search_state | string | – | Which records to search: active (default), archive or trash. |
No output schema declared.
No examples provided.
rex_search_appointments Search appointments ~243
Search appointments (calendar items such as inspections and meetings). Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). The searchable fields follow Reminders (reminder_date, remindee_user_id, contact_id, property_id, listing_id). Call rex_describe_search_fields with service Appointments for the full list. POST /v1/rex/Appointments/search.
| Name | Type | Req | Description |
|---|---|---|---|
| criteria | array | – | Filters, combined with AND: [{ name, type?, value }]. Only the in type gives an OR. Field names come from rex_describe_search_fields. |
| limit | integer | – | Rows to return, 1-100 (default 20). |
| offset | integer | – | Rows to skip (default 0). Use next_offset from the previous reply. |
| order_by | object | – | Sort, sortable field name to direction, for example { "system_modtime": "DESC" }. Sortable names can differ from search field names (rex_describe_search_fields with include_order_by lists them). |
| search_state | string | – | Which records to search: active (default), archive or trash. |
No output schema declared.
No examples provided.
rex_search_appraisals Search appraisals ~241
Search appraisals (listing presentations / market appraisals). Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). Useful fields: appraisal_date, appraisal_state, appraisal_type_id, agent_id, property_id, listing_id, pipeline_stage_id, expected_close_date, price_asking. POST /v1/rex/Appraisals/search.
| Name | Type | Req | Description |
|---|---|---|---|
| criteria | array | – | Filters, combined with AND: [{ name, type?, value }]. Only the in type gives an OR. Field names come from rex_describe_search_fields. |
| limit | integer | – | Rows to return, 1-100 (default 20). |
| offset | integer | – | Rows to skip (default 0). Use next_offset from the previous reply. |
| order_by | object | – | Sort, sortable field name to direction, for example { "system_modtime": "DESC" }. Sortable names can differ from search field names (rex_describe_search_fields with include_order_by lists them). |
| search_state | string | – | Which records to search: active (default), archive or trash. |
No output schema declared.
No examples provided.
rex_search_campaigns Search campaigns ~221
Search campaigns (nurture and marketing campaigns with their members). Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). Call rex_describe_search_fields with service Campaigns for the searchable fields. POST /v1/rex/Campaigns/search.
| Name | Type | Req | Description |
|---|---|---|---|
| criteria | array | – | Filters, combined with AND: [{ name, type?, value }]. Only the in type gives an OR. Field names come from rex_describe_search_fields. |
| limit | integer | – | Rows to return, 1-100 (default 20). |
| offset | integer | – | Rows to skip (default 0). Use next_offset from the previous reply. |
| order_by | object | – | Sort, sortable field name to direction, for example { "system_modtime": "DESC" }. Sortable names can differ from search field names (rex_describe_search_fields with include_order_by lists them). |
| search_state | string | – | Which records to search: active (default), archive or trash. |
No output schema declared.
No examples provided.
rex_search_contacts Search contacts ~255
Search contacts (people and companies). Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). Useful fields: contact.name_full, contact.name_first, contact.name_last, contact.email_address, contact.phone_number, contact.type, contact.tags, contact.interest_level, contact.last_contacted_date, system_modtime. To find someone by name, rex_autocomplete_contacts is simpler. POST /v1/rex/Contacts/search.
| Name | Type | Req | Description |
|---|---|---|---|
| criteria | array | – | Filters, combined with AND: [{ name, type?, value }]. Only the in type gives an OR. Field names come from rex_describe_search_fields. |
| limit | integer | – | Rows to return, 1-100 (default 20). |
| offset | integer | – | Rows to skip (default 0). Use next_offset from the previous reply. |
| order_by | object | – | Sort, sortable field name to direction, for example { "system_modtime": "DESC" }. Sortable names can differ from search field names (rex_describe_search_fields with include_order_by lists them). |
| search_state | string | – | Which records to search: active (default), archive or trash. |
No output schema declared.
No examples provided.
rex_search_deals Search deals ~222
Search deals (the sales pipeline). Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). Useful fields: deal.deal_state, deal.expected_close_date, deal.archive_date, deal.tags, deal.description. POST /v1/rex/Deals/search.
| Name | Type | Req | Description |
|---|---|---|---|
| criteria | array | – | Filters, combined with AND: [{ name, type?, value }]. Only the in type gives an OR. Field names come from rex_describe_search_fields. |
| limit | integer | – | Rows to return, 1-100 (default 20). |
| offset | integer | – | Rows to skip (default 0). Use next_offset from the previous reply. |
| order_by | object | – | Sort, sortable field name to direction, for example { "system_modtime": "DESC" }. Sortable names can differ from search field names (rex_describe_search_fields with include_order_by lists them). |
| search_state | string | – | Which records to search: active (default), archive or trash. |
No output schema declared.
No examples provided.
rex_search_leads Search leads ~248
Search leads (enquiries from portals, the website and email). Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). Useful fields: lead.contact_id, lead.listing_id, lead.property_id, lead.assignee_id, lead.lead_source_id, lead.lead_status_id, lead.system_completed_time, system_ctime. POST /v1/rex/Leads/search.
| Name | Type | Req | Description |
|---|---|---|---|
| criteria | array | – | Filters, combined with AND: [{ name, type?, value }]. Only the in type gives an OR. Field names come from rex_describe_search_fields. |
| limit | integer | – | Rows to return, 1-100 (default 20). |
| offset | integer | – | Rows to skip (default 0). Use next_offset from the previous reply. |
| order_by | object | – | Sort, sortable field name to direction, for example { "system_modtime": "DESC" }. Sortable names can differ from search field names (rex_describe_search_fields with include_order_by lists them). |
| search_state | string | – | Which records to search: active (default), archive or trash. |
No output schema declared.
No examples provided.
rex_search_listing_events Search listing events ~217
Search listing events (open homes and inspections). Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). Call rex_describe_search_fields with service ListingEvents for the searchable fields. POST /v1/rex/ListingEvents/search.
| Name | Type | Req | Description |
|---|---|---|---|
| criteria | array | – | Filters, combined with AND: [{ name, type?, value }]. Only the in type gives an OR. Field names come from rex_describe_search_fields. |
| limit | integer | – | Rows to return, 1-100 (default 20). |
| offset | integer | – | Rows to skip (default 0). Use next_offset from the previous reply. |
| order_by | object | – | Sort, sortable field name to direction, for example { "system_modtime": "DESC" }. Sortable names can differ from search field names (rex_describe_search_fields with include_order_by lists them). |
| search_state | string | – | Which records to search: active (default), archive or trash. |
No output schema declared.
No examples provided.
rex_search_listings Search listings ~279
Search listings (properties for sale or rent). Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). Useful fields: listing.system_listing_state (for example "current"), listing.system_publication_status, listing.price_match, listing.listing_agent_id, listing.listing_category_id, property.adr_suburb_or_town, property.adr_postcode, property.adr_street_name, property.attr_bedrooms. To find a listing by address, rex_autocomplete_listings is simpler. POST /v1/rex/Listings/search.
| Name | Type | Req | Description |
|---|---|---|---|
| criteria | array | – | Filters, combined with AND: [{ name, type?, value }]. Only the in type gives an OR. Field names come from rex_describe_search_fields. |
| limit | integer | – | Rows to return, 1-100 (default 20). |
| offset | integer | – | Rows to skip (default 0). Use next_offset from the previous reply. |
| order_by | object | – | Sort, sortable field name to direction, for example { "system_modtime": "DESC" }. Sortable names can differ from search field names (rex_describe_search_fields with include_order_by lists them). |
| search_state | string | – | Which records to search: active (default), archive or trash. |
No output schema declared.
No examples provided.
rex_search_notes Search notes ~229
Search notes recorded against contacts and properties. Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). Useful fields: system_ctime, system_created_user_id, id. Call rex_describe_search_fields with service Notes for related contact and property fields. POST /v1/rex/Notes/search.
| Name | Type | Req | Description |
|---|---|---|---|
| criteria | array | – | Filters, combined with AND: [{ name, type?, value }]. Only the in type gives an OR. Field names come from rex_describe_search_fields. |
| limit | integer | – | Rows to return, 1-100 (default 20). |
| offset | integer | – | Rows to skip (default 0). Use next_offset from the previous reply. |
| order_by | object | – | Sort, sortable field name to direction, for example { "system_modtime": "DESC" }. Sortable names can differ from search field names (rex_describe_search_fields with include_order_by lists them). |
| search_state | string | – | Which records to search: active (default), archive or trash. |
No output schema declared.
No examples provided.
rex_search_properties Search properties ~249
Search properties (the physical addresses behind listings, appraisals and tenancies). Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). Useful fields: property.system_search_key, property.adr_suburb_or_town, property.adr_postcode, property.adr_street_name, property.attr_bedrooms, property.attr_bathrooms. POST /v1/rex/Properties/search.
| Name | Type | Req | Description |
|---|---|---|---|
| criteria | array | – | Filters, combined with AND: [{ name, type?, value }]. Only the in type gives an OR. Field names come from rex_describe_search_fields. |
| limit | integer | – | Rows to return, 1-100 (default 20). |
| offset | integer | – | Rows to skip (default 0). Use next_offset from the previous reply. |
| order_by | object | – | Sort, sortable field name to direction, for example { "system_modtime": "DESC" }. Sortable names can differ from search field names (rex_describe_search_fields with include_order_by lists them). |
| search_state | string | – | Which records to search: active (default), archive or trash. |
No output schema declared.
No examples provided.
rex_search_reminders Search reminders and tasks ~253
Search reminders (follow-up tasks) linked to contacts, properties and listings. Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). Useful fields: reminder_date, system_completed_time, remindee_user_id, contact_id, property_id, listing_id, reminder_type_id, priority_id. Open reminders have no system_completed_time (type is, value Null). POST /v1/rex/Reminders/search.
| Name | Type | Req | Description |
|---|---|---|---|
| criteria | array | – | Filters, combined with AND: [{ name, type?, value }]. Only the in type gives an OR. Field names come from rex_describe_search_fields. |
| limit | integer | – | Rows to return, 1-100 (default 20). |
| offset | integer | – | Rows to skip (default 0). Use next_offset from the previous reply. |
| order_by | object | – | Sort, sortable field name to direction, for example { "system_modtime": "DESC" }. Sortable names can differ from search field names (rex_describe_search_fields with include_order_by lists them). |
| search_state | string | – | Which records to search: active (default), archive or trash. |
No output schema declared.
No examples provided.
rex_search_tenancies Search tenancies ~223
Search tenancies (property management leases). Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). Useful fields: id, property_id, system_record_state, lease_current_expiry, crt.contact_id. POST /v1/rex/Tenancies/search.
| Name | Type | Req | Description |
|---|---|---|---|
| criteria | array | – | Filters, combined with AND: [{ name, type?, value }]. Only the in type gives an OR. Field names come from rex_describe_search_fields. |
| limit | integer | – | Rows to return, 1-100 (default 20). |
| offset | integer | – | Rows to skip (default 0). Use next_offset from the previous reply. |
| order_by | object | – | Sort, sortable field name to direction, for example { "system_modtime": "DESC" }. Sortable names can differ from search field names (rex_describe_search_fields with include_order_by lists them). |
| search_state | string | – | Which records to search: active (default), archive or trash. |
No output schema declared.
No examples provided.
rex_search_users Search users ~235
Search the users (staff) of the agency account. Filters (criteria) combine with AND; results are paged with offset/limit (next_offset says where to continue). Useful fields: first_name, last_name, email, status, user_group_id. User ids are used elsewhere as agent, assignee and remindee ids. POST /v1/rex/AccountUsers/search.
| Name | Type | Req | Description |
|---|---|---|---|
| criteria | array | – | Filters, combined with AND: [{ name, type?, value }]. Only the in type gives an OR. Field names come from rex_describe_search_fields. |
| limit | integer | – | Rows to return, 1-100 (default 20). |
| offset | integer | – | Rows to skip (default 0). Use next_offset from the previous reply. |
| order_by | object | – | Sort, sortable field name to direction, for example { "system_modtime": "DESC" }. Sortable names can differ from search field names (rex_describe_search_fields with include_order_by lists them). |
| search_state | string | – | Which records to search: active (default), archive or trash. |
No output schema declared.
No examples provided.
How do I install the Rex Software MCP by usefulapi server?
Rex Software MCP by usefulapi is a hosted endpoint at https://rex-software.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 · rex-software.usefulapi.io
claude mcp add --transport http io-usefulapi-rex-software 'https://rex-software.usefulapi.io/mcp'
What is the Rex Software MCP by usefulapi server?
Rex Software MCP by usefulapi is listed in the public MCP registry as io.usefulapi/rex-software. Read contacts, listings, tenancies and tasks; create a person contact, note or reminder. This page covers its hosted endpoint (https://rex-software.usefulapi.io/mcp).
Is the Rex Software MCP by usefulapi server safe to use?
Rex Software 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 Rex Software MCP by usefulapi server expose?
Rex Software MCP by usefulapi exposes 33 tools: rex_get_user_profile, rex_list_accessible_accounts, rex_describe_search_fields, rex_list_value_lists, rex_get_value_list, and 28 more. Their descriptions and schemas cost roughly 5,104 tokens of context every time the server is loaded.
Does the Rex Software MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Rex Software 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 Rex Software MCP by usefulapi server still maintained?
Rex Software MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.