io.usefulapi/rex-software

None of its 33 tools are described as changing anything. For 33 the reading was uncertain, so no mark is shown.

• rex_get_user_profile

  “The Rex user this server is signed in as: user id, name, email, whether they own the account, position and default office.”

  Publisher declares: read-only yes

  Takes no inputs.

• rex_list_accessible_accounts

  “The Rex agency accounts (account_id and name) this user can sign in to.”

  Publisher declares: read-only yes

  Takes no inputs.

• rex_describe_search_fields

  “The field names a search on the given service accepts in criteria, each with its label, type and (for enums) the value list.”

  Publisher declares: read-only yes

  3 inputs, 1 required

  • servicestringrequired“The Rex service, for example Contacts or Listings.”
  • matchstring“Only fields whose name or label contains this text (case-insensitive).”
  • include_order_byboolean“Also return the service's model description, which lists the fields order_by accepts (they can differ from the search field names).”
• rex_list_value_lists

  “The names of Rex's value lists (the allowed ids for fields such as note types, reminder types, lead sources and property categories).”

  Publisher declares: read-only yes

  Takes no inputs.

• rex_get_value_list

  “The allowed values (id and label) of one value list, for example property_category.”

  Publisher declares: read-only yes

  1 input, 1 required

  • list_namestringrequired“The list name from rex_list_value_lists.”
• rex_autocomplete_contacts

  “Quick lookup of contacts by (part of) a name: returns the best matches with id, name, email and phone.”

  Publisher declares: read-only yes

  2 inputs, 1 required

  • search_stringstringrequired“Part of the contact's or company's name.”
  • limitinteger“Matches to return, 1-50 (default 10).”
• rex_autocomplete_listings

  “Quick lookup of listings by (part of) an address: returns the best matches with listing id and address.”

  Publisher declares: read-only yes

  3 inputs, 1 required

  • search_stringstringrequired“Part of the property address, for example '12 Smith St' or 'Subiaco'.”
  • listing_statesarray“Only listings in these states, for example ["current"] (see rex_get_value_list listing_system_state).”
  • limitinteger“Matches to return, 1-50 (default 10).”
• rex_search_contacts

  “Search contacts (people and companies).”

  Publisher declares: read-only yes

  5 inputs

  • criteriaarray“Filters, combined with AND: [{ name, type?, value }].”
  • order_byobject“Sort, sortable field name to direction, for example { "system_modtime": "DESC" }.”
  • offsetinteger“Rows to skip (default 0).”
  • limitinteger“Rows to return, 1-100 (default 20).”
  • search_statestring“Which records to search: active (default), archive or trash.”
• rex_search_listings

  “Search listings (properties for sale or rent).”

  Publisher declares: read-only yes

  5 inputs

  • criteriaarray“Filters, combined with AND: [{ name, type?, value }].”
  • order_byobject“Sort, sortable field name to direction, for example { "system_modtime": "DESC" }.”
  • offsetinteger“Rows to skip (default 0).”
  • limitinteger“Rows to return, 1-100 (default 20).”
  • search_statestring“Which records to search: active (default), archive or trash.”
• rex_search_properties

  “Search properties (the physical addresses behind listings, appraisals and tenancies).”

  Publisher declares: read-only yes

  5 inputs

  • criteriaarray“Filters, combined with AND: [{ name, type?, value }].”
  • order_byobject“Sort, sortable field name to direction, for example { "system_modtime": "DESC" }.”
  • offsetinteger“Rows to skip (default 0).”
  • limitinteger“Rows to return, 1-100 (default 20).”
  • search_statestring“Which records to search: active (default), archive or trash.”
• rex_search_leads

  “Search leads (enquiries from portals, the website and email).”

  Publisher declares: read-only yes

  5 inputs

  • criteriaarray“Filters, combined with AND: [{ name, type?, value }].”
  • order_byobject“Sort, sortable field name to direction, for example { "system_modtime": "DESC" }.”
  • offsetinteger“Rows to skip (default 0).”
  • limitinteger“Rows to return, 1-100 (default 20).”
  • search_statestring“Which records to search: active (default), archive or trash.”
• rex_search_appraisals

  “Search appraisals (listing presentations / market appraisals).”

  Publisher declares: read-only yes

  5 inputs

  • criteriaarray“Filters, combined with AND: [{ name, type?, value }].”
  • order_byobject“Sort, sortable field name to direction, for example { "system_modtime": "DESC" }.”
  • offsetinteger“Rows to skip (default 0).”
  • limitinteger“Rows to return, 1-100 (default 20).”
  • search_statestring“Which records to search: active (default), archive or trash.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-03.

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.