Propstack MCP by usefulapi
REMOTE · PROPSTACK.USEFULAPI.IO
Read Propstack contacts, properties, projects, deals, tasks, events; create and update CRM records.
Available components
Last scanned (5 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 17 Oct 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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
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 Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 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 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 19 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
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.
- 15 Oct 26 +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.
- 14 Oct 26 +3
- The server rewrote its instructions, which are the text every model session reads security
- 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 functional
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 59
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 17 Oct 2026 · Probed https://propstack.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 propstack.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://propstack.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://propstack.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://propstack.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://propstack.usefulapi.io/mcp |
| Authorisation server | https://propstack.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://propstack.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/propstack/ |
| http (plaintext) | http://propstack.usefulapi.io/mcp | Inconclusive | 302 | http://propstack.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 →
propstack_create_contact Create contact ~303
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| 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. |
No output schema declared.
No examples provided.
propstack_create_deal Create deal ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| broker_id | integer | – | User id of the deal owner. |
| contact_id | integer | yes | Contact (prospect) id. |
| deal_stage_id | integer | yes | Pipeline stage id. |
| note | string | – | Internal note on the deal. |
| price | number | – | Expected price of the deal. |
| property_id | integer | yes | Property id. |
No output schema declared.
No examples provided.
propstack_create_task Create note, to-do or appointment ~326
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | 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 | yes | Title. |
No output schema declared.
No examples provided.
propstack_get_contact Get contact ~127
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | 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. |
No output schema declared.
No examples provided.
propstack_get_property Get property ~65
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| property_id | integer | yes | Propstack property id. |
No output schema declared.
No examples provided.
propstack_get_reference_data Get reference data ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | Which list to fetch. |
No output schema declared.
No examples provided.
propstack_get_task Get task ~80
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | integer | yes | Propstack task id (the id of a note, to-do or appointment). |
No output schema declared.
No examples provided.
propstack_list_activities List activities ~326
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
propstack_list_contacts List or search contacts ~441
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| 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. |
No output schema declared.
No examples provided.
propstack_list_deal_pipelines List deal pipelines ~49
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
propstack_list_deals List deals ~309
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
propstack_list_events List calendar events ~209
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
propstack_list_projects List projects ~49
List projects (Projekte: a project groups several property units): title, project id, status, address, owner. Not paged; at most 200 are returned. GET /projects.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
propstack_list_properties List or search properties ~394
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
propstack_list_users List users ~51
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
propstack_update_contact Update contact ~286
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Propstack contact id. |
| custom_fields | object | – | Custom field values by field name; only the given fields change. |
| description | string | – | Internal note on the contact. |
| 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. |
No output schema declared.
No examples provided.
propstack_update_deal Update deal ~121
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| broker_id | integer | – | New deal owner (user id). |
| deal_id | integer | yes | 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. |
No output schema declared.
No examples provided.
propstack_update_task Update task ~196
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Propstack task id. |
| title | string | – | Title. |
No output schema declared.
No examples provided.
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.
remote · propstack.usefulapi.io
claude mcp add --transport http io-usefulapi-propstack 'https://propstack.usefulapi.io/mcp'
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.