# Propstack MCP by usefulapi (remote · propstack.usefulapi.io)

Read Propstack contacts, properties, projects, deals, tasks, events; create and update CRM records.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `propstack.usefulapi.io`: 63/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-propstack/propstack.md), [page](https://verifymcp.io/servers/io-usefulapi-propstack/propstack)

## Channel facts

- Endpoint: `https://propstack.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3749 tokens (~208/item across 18 items; 18 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Propstack MCP by usefulapi server?

Propstack MCP by usefulapi is a hosted endpoint at https://propstack.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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-propstack 'https://propstack.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-propstack": {
      "url": "https://propstack.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-propstack": {
      "type": "http",
      "url": "https://propstack.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-propstack]
url = "https://propstack.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-propstack": {
      "type": "remote",
      "url": "https://propstack.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-propstack --url 'https://propstack.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-propstack:
    url: "https://propstack.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-propstack": {
      "Transport": "http",
      "Url": "https://propstack.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-propstack -t streamable-http -u 'https://propstack.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-propstack": {
      "type": "http",
      "url": "https://propstack.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-15 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 62, +3)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-13 (score 59, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 59)

First indexed and scored.

## MCP tools (18)

### `propstack_list_contacts` (~441 tokens)

List or search contacts

List or search CRM contacts (Kontakte). Returns business fields only (name, company, email, phone numbers, status, source, tags, owner, dates), never birth data, identity or tax numbers, income or portal tokens. Search by free text (name, email, address, phone), exact email, exact phone number, or filter by status, source, tag, owner and dates. Archived contacts are excluded unless archived is set. GET /contacts.

Input parameters:

- `archived` (string): 'only' = only archived contacts, 'include' = archived and active. Default: active only.
- `broker_id` (integer): Only contacts looked after by this user id (see propstack_list_users).
- `created_after` (string): Only contacts created at or after this ISO 8601 date-time.
- `created_before` (string): Only contacts created at or before this ISO 8601 date-time.
- `email` (string): Exact email address of the contact.
- `include_children` (boolean): Also return sub-contacts (contact persons of a company).
- `order` (string): Sort direction.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per` (integer): Results per page, 1-100 (default 25).
- `phone_number` (string): Exact phone number (spaces and dashes are ignored).
- `query` (string): Free-text search over first name, last name, emails, address and phone numbers.
- `sort_by` (string): Sort field.
- `source_ids` (array): Only contacts from one of these source ids (see propstack_get_reference_data contact_sources).
- `status_ids` (array): Only contacts with one of these contact-status ids.
- `tag_ids` (array): Only contacts with these tag (Merkmal) ids (see propstack_get_reference_data contact_tags).
- `updated_after` (string): Only contacts updated at or after this ISO 8601 date-time.
- `updated_before` (string): Only contacts updated at or before this ISO 8601 date-time.

### `propstack_get_contact` (~127 tokens)

Get contact

One contact by id with address, salutation, language, notes, GDPR status, owner, status, source, tags, sub-contacts and owned properties. Birth data, identity and tax numbers, income and the portal token are never returned. GET /contacts/{id}.

Input parameters:

- `contact_id` (integer, required): Propstack contact id.
- `custom_fields` (array): Names of custom fields to return (only these; sensitive ones such as birth date or income are never returned).
- `include` (array): Related records to include: sub-contacts and/or properties the contact owns.

### `propstack_list_properties` (~394 tokens)

List or search properties

List or search properties (Objekte / units): address, type, marketing type (buy/rent), rooms, areas, prices, status. Images and owners are not returned. Filter by free text, status, tag, project, marketing type, object type, price and area ranges. GET /units.

Input parameters:

- `archived` (string): 'only' = only archived properties, 'include' = archived and active. Default: active only.
- `base_rent_from` (number): Minimum cold rent.
- `base_rent_to` (number): Maximum cold rent.
- `country` (string): Two-letter ISO country code, e.g. DE.
- `living_space_from` (number): Minimum living space in square metres.
- `living_space_to` (number): Maximum living space in square metres.
- `marketing_type` (string): Sale or rent.
- `order` (string): Sort direction.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per` (integer): Results per page, 1-100 (default 25).
- `price_from` (number): Minimum purchase price.
- `price_to` (number): Maximum purchase price.
- `project_id` (integer): Only the units of this project id.
- `query` (string): Free-text search over unit id, street, zip code, city, district and exposee id.
- `rooms_from` (number): Minimum number of rooms.
- `rooms_to` (number): Maximum number of rooms.
- `rs_type` (string): Property type.
- `sort_by` (string): Sort field.
- `status_ids` (array): Only properties in one of these status ids (see propstack_get_reference_data property_statuses).
- `tag_ids` (array): Only properties with one of these tag ids (see propstack_get_reference_data property_tags).

### `propstack_get_property` (~65 tokens)

Get property

One property (Objekt) by id: address, type, rooms, areas, prices, status and the description, location and furnishing texts (clipped). No images or owner. GET /units/{id}.

Input parameters:

- `property_id` (integer, required): Propstack property id.

### `propstack_list_projects` (~49 tokens)

List projects

List projects (Projekte: a project groups several property units): title, project id, status, address, owner. Not paged; at most 200 are returned. GET /projects.

### `propstack_list_deals` (~309 tokens)

List deals

List deals (a deal links a contact to a property and sits in a pipeline stage). Filter by pipeline, stage, category (qualified/unqualified/lost), contact, property, project or owner. Use propstack_list_deal_pipelines for stage ids. GET /client_properties.

Input parameters:

- `broker_id` (integer): Only deals owned by this user id.
- `category` (string): Deal category.
- `contact_id` (integer): Only the deals of this contact.
- `created_after` (string): Only deals created at or after this ISO 8601 date-time.
- `created_before` (string): Only deals created at or before this ISO 8601 date-time.
- `deal_pipeline_id` (integer): Only deals in this pipeline.
- `deal_stage_ids` (array): Only deals in these stages.
- `include_contact` (boolean): Embed a short contact record in each deal (default false).
- `include_property` (boolean): Embed a short property record in each deal (default false).
- `order` (string): Sort direction.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per` (integer): Results per page, 1-100 (default 25).
- `project_id` (integer): Only the deals of this project.
- `property_id` (integer): Only the deals of this property.
- `sort_by` (string): Sort field (default created_at).

### `propstack_list_deal_pipelines` (~49 tokens)

List deal pipelines

List the deal pipelines with their stages (id, name, position, win chance). Use the stage ids to filter deals or to move a deal. GET /deal_pipelines.

### `propstack_list_activities` (~326 tokens)

List activities

List the activity timeline (notes, tasks, appointments, e-mails, SMS, letters, rejections, inquiries) with title, linked contacts and properties, state and dates. Message and note bodies are not returned. Filter by type, contact, property, project, owner, category or date. GET /activities.

Input parameters:

- `broker_id` (integer): Only activities assigned to this user id.
- `category_id` (integer): Only this activity type id (see propstack_get_reference_data activity_types).
- `contact_id` (integer): Only activities linked to this contact.
- `created_after` (string): Only activities created at or after this ISO 8601 date-time.
- `created_before` (string): Only activities created at or before this ISO 8601 date-time.
- `item_type` (string): Kind of activity; 'reminder' is a to-do.
- `only_inquiries` (boolean): Only inquiries (Anfragen).
- `order` (string): Sort direction.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per` (integer): Results per page, 1-100 (default 25).
- `project_id` (integer): Only activities linked to this project.
- `property_id` (integer): Only activities linked to this property.
- `starts_after` (string): Only activities that start at or after this ISO 8601 date-time.
- `starts_before` (string): Only activities that start at or before this ISO 8601 date-time.

### `propstack_get_task` (~80 tokens)

Get task

One task by id (a note, to-do or appointment): title, body text (clipped), type, linked contacts, properties and projects (id and name only), due date or start/end. GET /tasks/{id}.

Input parameters:

- `task_id` (integer, required): Propstack task id (the id of a note, to-do or appointment).

### `propstack_list_events` (~209 tokens)

List calendar events

List calendar appointments (Termine, e.g. viewings) in a time window, with title, place, start/end, state and the linked contact, property and project (id and name only). Paged: follow next_page. GET /events.

Input parameters:

- `broker_id` (integer): Only events assigned to this user id.
- `contact_id` (integer): Only events with this contact.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per` (integer): Results per page, 1-100 (default 25).
- `project_id` (integer): Only events for this project.
- `property_id` (integer): Only events for this property.
- `starts_after` (string): Only events that start after this ISO 8601 date-time.
- `starts_before` (string): Only events that start before this ISO 8601 date-time.
- `state` (string): Event state.

### `propstack_list_users` (~51 tokens)

List users

List the users (staff, Nutzer) of the Propstack account: id, name, work email, position, phone, team. Use the ids as owner/broker filters. GET /brokers.

### `propstack_get_reference_data` (~89 tokens)

Get reference data

Look up the ids used by other tools: property_statuses, activity_types (note/task/appointment types, needed as note_type_id), contact_sources, reservation_reasons (rejection reasons), contact_tags or property_tags. GET /property_statuses, /activity_types, /contact_sources, /reservation_reasons or /groups.

Input parameters:

- `kind` (string, required): Which list to fetch.

### `propstack_create_contact` (~303 tokens)

Create contact

WRITE: create a CRM contact. Propstack matches on the email address: if a contact with the same email already exists it is UPDATED with the given fields instead of creating a duplicate. Consent flags (newsletter, contact permission, GDPR status) cannot be set here. Returns the contact id. POST /contacts.

Input parameters:

- `academic_title` (string): Academic title, e.g. Dr.
- `broker_id` (integer): User id of the person looking after the contact.
- `client_source_id` (integer): Contact source id (see propstack_get_reference_data contact_sources).
- `client_status_id` (integer): Contact status id.
- `company` (string): Company the contact works for.
- `custom_fields` (object): Custom field values by field name; only the given fields change.
- `description` (string): Internal note on the contact.
- `email` (string): Primary email address.
- `first_name` (string): First name.
- `home_cell` (string): Mobile number.
- `home_phone` (string): Landline number.
- `is_company` (boolean): True if the contact is a company.
- `language` (string): Contact language.
- `last_name` (string): Last name.
- `office_cell` (string): Business mobile number.
- `office_phone` (string): Business phone number.
- `position` (string): Position in the company.
- `salutation` (string): Salutation: mr or ms.

### `propstack_update_contact` (~286 tokens)

Update contact

WRITE: change the given fields of an existing contact; fields not given stay as they are. Returns the updated contact (business fields). PUT /contacts/{id}.

Input parameters:

- `academic_title` (string): Academic title, e.g. Dr.
- `broker_id` (integer): User id of the person looking after the contact.
- `client_source_id` (integer): Contact source id (see propstack_get_reference_data contact_sources).
- `client_status_id` (integer): Contact status id.
- `company` (string): Company the contact works for.
- `contact_id` (integer, required): Propstack contact id.
- `custom_fields` (object): Custom field values by field name; only the given fields change.
- `description` (string): Internal note on the contact.
- `email` (string): Primary email address.
- `first_name` (string): First name.
- `home_cell` (string): Mobile number.
- `home_phone` (string): Landline number.
- `is_company` (boolean): True if the contact is a company.
- `language` (string): Contact language.
- `last_name` (string): Last name.
- `office_cell` (string): Business mobile number.
- `office_phone` (string): Business phone number.
- `position` (string): Position in the company.
- `salutation` (string): Salutation: mr or ms.

### `propstack_create_task` (~326 tokens)

Create note, to-do or appointment

WRITE: create a note, a to-do (with due date) or an appointment (with start and end) in Propstack, linked to contacts, properties or projects. note_type_id is the activity type id (see propstack_get_reference_data activity_types). No e-mail or SMS is sent to the contact; the only mail is the reminder to the assignee when remind_at is set. Returns the new task id. POST /tasks.

Input parameters:

- `body` (string): Note text (plain text; stored as escaped HTML with line breaks).
- `broker_id` (integer): User id the task is assigned to.
- `contact_ids` (array): Contacts the activity is linked to (usually one).
- `due_date` (string): Due date and time (todo only).
- `ends_at` (string): End (appointment only).
- `kind` (string, required): note = plain note, todo = task with due_date, appointment = event with starts_at and ends_at.
- `location` (string): Place (appointment only).
- `note_type_id` (integer, required): Activity type id; must match the kind (see propstack_get_reference_data activity_types).
- `project_ids` (array): Projects the activity is linked to.
- `property_ids` (array): Properties the activity is linked to.
- `remind_at` (string): When Propstack e-mails a reminder to the assignee, before due_date (todo only). This sends a mail to a colleague.
- `starts_at` (string): Start (appointment only).
- `title` (string, required): Title.

### `propstack_update_task` (~196 tokens)

Update task

WRITE: change the given fields of an existing note, to-do or appointment (for example mark a to-do done, move its due date, or reschedule). Fields not given stay as they are. PUT /tasks/{id}.

Input parameters:

- `body` (string): Note text (plain text; stored as escaped HTML with line breaks).
- `broker_id` (integer): User id the task is assigned to.
- `done` (boolean): Mark a to-do done (true) or open (false).
- `due_date` (string): New due date and time (to-do).
- `ends_at` (string): New end (appointment).
- `location` (string): New place (appointment).
- `remind_at` (string): New reminder time (to-do).
- `starts_at` (string): New start (appointment).
- `task_id` (integer, required): Propstack task id.
- `title` (string): Title.

### `propstack_create_deal` (~123 tokens)

Create deal

WRITE: create a deal linking a contact to a property in a pipeline stage (see propstack_list_deal_pipelines for stage ids). Returns the new deal. POST /client_properties.

Input parameters:

- `broker_id` (integer): User id of the deal owner.
- `contact_id` (integer, required): Contact (prospect) id.
- `deal_stage_id` (integer, required): Pipeline stage id.
- `note` (string): Internal note on the deal.
- `price` (number): Expected price of the deal.
- `property_id` (integer, required): Property id.

### `propstack_update_deal` (~121 tokens)

Update deal

WRITE: change the given fields of a deal, typically move it to another pipeline stage or update its note or price. Fields not given stay as they are. PUT /client_properties/{id}.

Input parameters:

- `broker_id` (integer): New deal owner (user id).
- `deal_id` (integer, required): Propstack deal id.
- `deal_stage_id` (integer): Move the deal to this stage.
- `note` (string): Internal note on the deal (replaces the previous note).
- `price` (number): Expected price of the deal.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-propstack/propstack#diagnostics

## Score history

- 2026-10-17: 63
- 2026-10-16: 63
- 2026-10-15: 63
- 2026-10-14: 62
- 2026-10-13: 59
- 2026-10-12: 59

## Common questions

### What is the Propstack MCP by usefulapi server?

Propstack MCP by usefulapi is listed in the public MCP registry as io.usefulapi/propstack. Read Propstack contacts, properties, projects, deals, tasks, events; create and update CRM records. This page covers its hosted endpoint (https://propstack.usefulapi.io/mcp).

### Is the Propstack MCP by usefulapi server safe to use?

Propstack MCP by usefulapi scores 63 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 Propstack MCP by usefulapi server expose?

Propstack MCP by usefulapi exposes 18 tools: propstack_list_contacts, propstack_get_contact, propstack_list_properties, propstack_get_property, propstack_list_projects, and 13 more. Their descriptions and schemas cost roughly 3,544 tokens of context every time the server is loaded.

### Does the Propstack MCP by usefulapi server require authentication?

Yes. Propstack MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Propstack MCP by usefulapi server still maintained?

Propstack MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://propstack.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/propstack/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-propstack/propstack.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-propstack/propstack.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-propstack/propstack