# new.estate — listing drafts (remote · new.estate)

Create drafts of personal real estate listings on your new.estate account from a conversation.

- Trust score: 40/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `new.estate`: 40/100 (this document), [markdown](https://verifymcp.io/servers/estate-new-publish/api-mcp-publish.md), [page](https://verifymcp.io/servers/estate-new-publish/api-mcp-publish)

## Channel facts

- Endpoint: `https://new.estate/api/mcp/publish`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.2.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-11-05.

- **Endpoint Security**: 100/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **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 blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**Unverified: 6 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 new.estate — listing drafts MCP server?

new.estate — listing drafts is a hosted endpoint at https://new.estate/api/mcp/publish, 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 estate-new-publish 'https://new.estate/api/mcp/publish'
```

### Cursor

```json
{
  "mcpServers": {
    "estate-new-publish": {
      "url": "https://new.estate/api/mcp/publish"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "estate-new-publish": {
      "type": "http",
      "url": "https://new.estate/api/mcp/publish"
    }
  }
}
```

### Codex

```toml
[mcp_servers.estate-new-publish]
url = "https://new.estate/api/mcp/publish"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "estate-new-publish": {
      "type": "remote",
      "url": "https://new.estate/api/mcp/publish",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add estate-new-publish --url 'https://new.estate/api/mcp/publish' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  estate-new-publish:
    url: "https://new.estate/api/mcp/publish"
```

### Netclaw

```json
{
  "McpServers": {
    "estate-new-publish": {
      "Transport": "http",
      "Url": "https://new.estate/api/mcp/publish"
    }
  }
}
```

### Vellum

```bash
assistant mcp add estate-new-publish -t streamable-http -u 'https://new.estate/api/mcp/publish'
```

### Other

```json
{
  "mcpServers": {
    "estate-new-publish": {
      "type": "http",
      "url": "https://new.estate/api/mcp/publish"
    }
  }
}
```

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-28 (score 40)

First indexed and scored.

## MCP tools (0)

No tool schema has been captured from this endpoint yet.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/estate-new-publish/api-mcp-publish#diagnostics

## Score history

- 2026-11-05: 40
- 2026-11-04: 40
- 2026-11-03: 40
- 2026-11-02: 40
- 2026-11-01: 40
- 2026-10-31: 40
- 2026-10-30: 40
- 2026-10-29: 40
- 2026-10-28: 40

## Common questions

### What is the new.estate — listing drafts MCP server?

new.estate — listing drafts is an MCP server listed in the public MCP registry as estate.new/publish. Create drafts of personal real estate listings on your new.estate account from a conversation. This page covers its hosted endpoint (https://new.estate/api/mcp/publish).

### Is the new.estate — listing drafts MCP server safe to use?

new.estate — listing drafts scores 40 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.

### Does the new.estate — listing drafts MCP server require authentication?

Yes. new.estate — listing drafts 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 new.estate — listing drafts MCP server still maintained?

new.estate — listing drafts 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 new.estate — listing drafts MCP server?

VerifyMCP ran 5 checks on new.estate — listing drafts, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about new.estate — listing drafts: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 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://new.estate/api/mcp/publish
- Website: https://new.estate/en-US/docs/ai-assistants
- Changelog RSS feed: https://verifymcp.io/servers/estate-new-publish/api-mcp-publish.xml
- Changelog JSON feed: https://verifymcp.io/servers/estate-new-publish/api-mcp-publish/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/estate-new-publish/api-mcp-publish.json
- HTML version of this page: https://verifymcp.io/servers/estate-new-publish/api-mcp-publish