# Open To Close MCP by usefulapi (remote · open-to-close.usefulapi.io)

Review Open To Close properties and transaction records; add contacts and property notes.

- Trust score: 18/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `open-to-close.usefulapi.io`: 18/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-open-to-close/open-to-close.md), [page](https://verifymcp.io/servers/io-usefulapi-open-to-close/open-to-close)

## Channel facts

- Endpoint: `https://open-to-close.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.6.3`

## 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-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - 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.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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.

## Install

### How do I install the Open To Close MCP by usefulapi server?

Open To Close MCP by usefulapi is a hosted endpoint at https://open-to-close.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-open-to-close 'https://open-to-close.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-open-to-close": {
      "url": "https://open-to-close.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  io-usefulapi-open-to-close:
    url: "https://open-to-close.usefulapi.io/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-open-to-close": {
      "type": "http",
      "url": "https://open-to-close.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-11-01 (score 18, −44)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [security regression] Stability: 0.03 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

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

- [security improvement] Authorization: partial → pass
- [functional improvement] Stability: unverified → 0.03
- [functional improvement] MCP protocol: fail → pass
- [functional] New prompt “add_a_confirmed_property_note”
- [functional] New prompt “create_a_contact_after_checking_for_duplicates”
- [functional] New prompt “find_contacts_for_a_property”
- [functional] New prompt “inspect_a_property_s_tasks”
- [functional] New prompt “review_property_assignments”
- [functional] MCP protocol version: 2025-06-18 → 2025-11-25
- [functional] Server version: 1.2.0 → 1.4.0
- [functional] Server version: 1.1.0 → 1.2.0
- [functional] Server version: 1.0.3 → 1.1.0

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

First indexed and scored.

## MCP tools (20)

### `opentoclose_list_agents` (~122 tokens)

List agents with name/email search and documented sorting. One offset/limit page. GET /v1/agents/.

Input parameters:

- `email` (string)
- `first_name` (string)
- `last_name` (string)
- `limit` (integer): Rows per call, default 20, maximum 100. If the page is full, request the next offset; no total count is documented.
- `offset` (integer): Rows to skip, default 0.
- `sort_by` (string)
- `sort_dir` (string)

### `opentoclose_list_contacts` (~122 tokens)

List contacts with name/email search and documented sorting. One offset/limit page. GET /v1/contacts.

Input parameters:

- `email` (string)
- `first_name` (string)
- `last_name` (string)
- `limit` (integer): Rows per call, default 20, maximum 100. If the page is full, request the next offset; no total count is documented.
- `offset` (integer): Rows to skip, default 0.
- `sort_by` (string)
- `sort_dir` (string)

### `opentoclose_list_contact_roles` (~23 tokens)

List contact roles. GET /v1/contactRoles/.

### `opentoclose_list_file_roles` (~23 tokens)

List file roles. GET /v1/fileRoles/.

### `opentoclose_list_property_fields` (~26 tokens)

List property fields grouped into sections. GET /v1/propertyFields.

### `opentoclose_list_property_field_groups` (~26 tokens)

List property field groups. GET /v1/propertyFieldGroups.

### `opentoclose_list_property_field_sections` (~26 tokens)

List property field sections. GET /v1/propertyFieldSections.

### `opentoclose_list_property_templates` (~23 tokens)

List property templates. GET /v1/propertyTemplates/.

### `opentoclose_list_teams` (~25 tokens)

List teams and their members. GET /v1/teams/.

### `opentoclose_list_time_zones` (~24 tokens)

List time zones. GET /v1/timeZones/.

### `opentoclose_list_tags` (~21 tokens)

List tags. GET /v1/tags.

### `opentoclose_list_properties` (~101 tokens)

List properties with team/agent summaries through the current v1.1 endpoint. Maximum 50 per call. This does not return a property's full field values. GET /v1.1/properties.

Input parameters:

- `limit` (integer): Rows per call, default 20, maximum 50. If the page is full, request the next offset; no total count is documented.
- `offset` (integer): Rows to skip, default 0.

### `opentoclose_list_property_contacts` (~68 tokens)

List contacts associated with a property, optionally filtered by name/email. GET /v1/properties/{property_id}/contacts.

Input parameters:

- `email` (string)
- `first_name` (string)
- `last_name` (string)
- `property_id` (integer, required)

### `opentoclose_list_property_documents` (~48 tokens)

Read a property's document folders and document metadata/links. Does not download files. GET /v1/properties/{property_id}/documents.

Input parameters:

- `property_id` (integer, required)

### `opentoclose_list_property_notes` (~94 tokens)

List notes associated with a property. One offset/limit page. GET /v1/properties/{property_id}/notes.

Input parameters:

- `limit` (integer): Rows per call, default 20, maximum 100. If the page is full, request the next offset; no total count is documented.
- `offset` (integer): Rows to skip, default 0.
- `property_id` (integer, required)

### `opentoclose_get_property_note` (~51 tokens)

Read one note associated with a property. GET /v1/properties/{property_id}/notes/{record_id}.

Input parameters:

- `property_id` (integer, required)
- `record_id` (integer, required)

### `opentoclose_list_property_tasks` (~39 tokens)

List tasks associated with a property. GET /v1/properties/{property_id}/tasks.

Input parameters:

- `property_id` (integer, required)

### `opentoclose_get_property_task` (~51 tokens)

Read one task associated with a property. GET /v1/properties/{property_id}/tasks/{record_id}.

Input parameters:

- `property_id` (integer, required)
- `record_id` (integer, required)

### `opentoclose_create_contact` (~162 tokens)

WRITE: create a contact. Search existing contacts first to avoid duplicates, then confirm the requested details. Creates a contact record without associating it with a property. Returns a created record ID. POST /v1/contacts.

Input parameters:

- `address` (string)
- `cell_phone` (string)
- `city` (string)
- `contact_role_id` (integer)
- `country` (string)
- `email` (string)
- `first_name` (string)
- `last_name` (string)
- `middle_name` (string)
- `nick_name` (string)
- `office_email` (string)
- `phone` (string)
- `state` (string)
- `zip` (string)

### `opentoclose_add_property_note` (~132 tokens)

WRITE: add a note to a property. Confirm the property and note content/visibility with the user first. Adds another note on each call; inspect current notes before retrying. Optional visibility fields are omitted unless supplied; the vendor documents null defaults. POST /v1/properties/{property_id}/notes.

Input parameters:

- `description` (string, required)
- `global` (boolean)
- `personal` (boolean)
- `pinned` (boolean)
- `priority` (string)
- `priority_date` (string)
- `private` (boolean)
- `property_id` (integer, required)

## Diagnostics

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

## Score history

- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 18
- 2026-10-31: 62
- 2026-10-30: 59

## Common questions

### What is the Open To Close MCP by usefulapi server?

Open To Close MCP by usefulapi is listed in the public MCP registry as io.usefulapi/open-to-close. Review Open To Close properties and transaction records; add contacts and property notes. This page covers its hosted endpoint (https://open-to-close.usefulapi.io/mcp).

### Is the Open To Close MCP by usefulapi server safe to use?

Open To Close 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 Open To Close MCP by usefulapi server expose?

Open To Close MCP by usefulapi exposes 20 tools: opentoclose_list_agents, opentoclose_list_contacts, opentoclose_list_contact_roles, opentoclose_list_file_roles, opentoclose_list_property_fields, and 15 more. Their descriptions and schemas cost roughly 1,207 tokens of context every time the server is loaded.

### Does the Open To Close MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Open To Close 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 Open To Close MCP by usefulapi server still maintained?

Open To Close 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.

### What did VerifyMCP test on the Open To Close MCP by usefulapi server?

VerifyMCP ran 4 checks on Open To Close 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 Open To Close 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.

## Links

- Remote endpoint: https://open-to-close.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/open-to-close/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-open-to-close/open-to-close.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-open-to-close/open-to-close/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-usefulapi-open-to-close/open-to-close.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-open-to-close/open-to-close