# Contact Affordance (remote · contact-affordance-mcp.ottobot2025.workers.dev)

Check how to contact a business website, and whether that contact path actually works.

- Trust score: 70/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `contact-affordance-mcp.ottobot2025.workers.dev`: 70/100 (this document), [markdown](https://verifymcp.io/servers/org-ottobot-contact-affordance/contact-affordance-mcp.md), [page](https://verifymcp.io/servers/org-ottobot-contact-affordance/contact-affordance-mcp)

## Channel facts

- Endpoint: `https://contact-affordance-mcp.ottobot2025.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## 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-09-28.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 86/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 132 tokens (~132/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 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 Contact Affordance MCP server?

Contact Affordance is a hosted endpoint at https://contact-affordance-mcp.ottobot2025.workers.dev/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 org-ottobot-contact-affordance 'https://contact-affordance-mcp.ottobot2025.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "org-ottobot-contact-affordance": {
      "url": "https://contact-affordance-mcp.ottobot2025.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-ottobot-contact-affordance": {
      "type": "http",
      "url": "https://contact-affordance-mcp.ottobot2025.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.org-ottobot-contact-affordance]
url = "https://contact-affordance-mcp.ottobot2025.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-ottobot-contact-affordance": {
      "type": "remote",
      "url": "https://contact-affordance-mcp.ottobot2025.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-ottobot-contact-affordance --url 'https://contact-affordance-mcp.ottobot2025.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-ottobot-contact-affordance:
    url: "https://contact-affordance-mcp.ottobot2025.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "org-ottobot-contact-affordance": {
      "Transport": "http",
      "Url": "https://contact-affordance-mcp.ottobot2025.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-ottobot-contact-affordance -t streamable-http -u 'https://contact-affordance-mcp.ottobot2025.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "org-ottobot-contact-affordance": {
      "type": "http",
      "url": "https://contact-affordance-mcp.ottobot2025.workers.dev/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-09-28 (score 70, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 70, +1)

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

### 2026-09-25 (score 69, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 68, +1)

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

### 2026-09-21 (score 67, +1)

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

### 2026-09-19 (score 66, +1)

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

### 2026-09-17 (score 65, +1)

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

### 2026-09-14 (score 64, +1)

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

## MCP tools (1)

### `check_contact_path` (~132 tokens)

Given a business website URL, report how a human is meant to make contact and whether that path is actually reachable. Returns a verdict of 'reachable' or 'inconclusive', the forms found with their resolved handler URLs, and any published phone or email. Never submits anything. Answers 'inconclusive' rather than guessing when a site is client-rendered, bot-protected or parked -- about 64% of real sites cannot be judged from outside, and a confident wrong answer is worse than an honest one.

Input parameters:

- `url` (string, required): The business website URL, e.g. https://example.com

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-ottobot-contact-affordance/contact-affordance-mcp#diagnostics

## Score history

- 2026-09-28: 70
- 2026-09-27: 70
- 2026-09-26: 69
- 2026-09-25: 69
- 2026-09-24: 68
- 2026-09-23: 68
- 2026-09-22: 67
- 2026-09-21: 67
- 2026-09-20: 66
- 2026-09-19: 66
- 2026-09-18: 65
- 2026-09-17: 65
- 2026-09-16: 64
- 2026-09-15: 64
- 2026-09-14: 64
- 2026-09-13: 63
- 2026-09-12: 63
- 2026-09-11: 62
- 2026-09-10: 62
- 2026-09-09: 61
- 2026-09-08: 61
- 2026-09-07: 60

## Common questions

### What is the Contact Affordance MCP server?

Contact Affordance is an MCP server listed in the public MCP registry as org.ottobot/contact-affordance. Check how to contact a business website, and whether that contact path actually works. This page covers its hosted endpoint (https://contact-affordance-mcp.ottobot2025.workers.dev/mcp).

### Is the Contact Affordance MCP server safe to use?

Contact Affordance scores 70 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 Contact Affordance MCP server expose?

Contact Affordance exposes 1 tool: check_contact_path. Their descriptions and schemas cost roughly 132 tokens of context every time the server is loaded.

### Does the Contact Affordance MCP server require authentication?

No. We connected to Contact Affordance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Contact Affordance MCP server still maintained?

Contact Affordance is still listed as active in the MCP registry. We last reached this channel on 28 September 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://contact-affordance-mcp.ottobot2025.workers.dev/mcp
- Repository: https://github.com/modelcontextprotocol/registry
- Changelog RSS feed: https://verifymcp.io/servers/org-ottobot-contact-affordance/contact-affordance-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-ottobot-contact-affordance/contact-affordance-mcp.json
- HTML version of this page: https://verifymcp.io/servers/org-ottobot-contact-affordance/contact-affordance-mcp