# The Landing Company of Madison Park (remote · landingonmadison.com)

Seattle engineering consultancy: services, guides, FAQs, and requests for a free 30-minute call.

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `landingonmadison.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-landingonmadison-landing-company/landingonmadison.md), [page](https://verifymcp.io/servers/com-landingonmadison-landing-company/landingonmadison)

## Channel facts

- Endpoint: `https://landingonmadison.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- 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-11-06.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 68/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 416 tokens (~59/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the The Landing Company of Madison Park MCP server?

The Landing Company of Madison Park is a hosted endpoint at https://landingonmadison.com/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 com-landingonmadison-landing-company 'https://landingonmadison.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-landingonmadison-landing-company": {
      "url": "https://landingonmadison.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-landingonmadison-landing-company": {
      "type": "http",
      "url": "https://landingonmadison.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-landingonmadison-landing-company]
url = "https://landingonmadison.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-landingonmadison-landing-company": {
      "type": "remote",
      "url": "https://landingonmadison.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-landingonmadison-landing-company --url 'https://landingonmadison.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-landingonmadison-landing-company:
    url: "https://landingonmadison.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-landingonmadison-landing-company": {
      "Transport": "http",
      "Url": "https://landingonmadison.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-landingonmadison-landing-company -t streamable-http -u 'https://landingonmadison.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-landingonmadison-landing-company": {
      "type": "http",
      "url": "https://landingonmadison.com/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-06 (score 74, +1)

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

### 2026-11-04 (score 73, +1)

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

### 2026-11-03 (score 72, 0)

- [security] Tool “request_consultation” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] Tool “request_consultation” changed its title: Request a free 30-minute call → Request a call

### 2026-11-02 (score 72)

First indexed and scored.

## MCP tools (7)

### `get_firm_overview` (~39 tokens)

About the firm

What The Landing Company of Madison Park is, who it helps, who does the work, where it is based, and how to start.

### `list_services` (~56 tokens)

Services

The services the firm offers, each with the situations it fits and what the work involves. Optionally limit to services for companies and engineering teams, or for local small businesses.

Input parameters:

- `audience` (string): Omit to list every service.

### `get_approach` (~25 tokens)

How the firm works

How an engagement runs, from understanding the problem to handing the work back.

### `get_faq` (~28 tokens)

Frequently asked questions

Answers to common questions, including whether an independent consultant or a larger firm is the better fit.

### `list_guides` (~32 tokens)

Guides

Short practical guides the firm has written on difficult technology decisions. Returns each guide’s slug and the question it answers.

### `get_guide` (~30 tokens)

Read a guide

The full text of one guide, by slug from list_guides.

Input parameters:

- `slug` (string, required)

### `request_consultation` (~154 tokens)

Request a call

Sends The Landing Company a request for a 30-minute call with Campion Fellin, with the person’s name, email, problem description, and optionally company and availability. It does not book a time: the reply comes by email within one business day.

Input parameters:

- `availability` (string): Days, times and time zone that suit them, if they said.
- `company` (string): Their company or organization, if they gave one.
- `email` (string, required): Where to send the reply.
- `name` (string, required): The person’s name.
- `problem` (string, required): A few sentences in the person’s words: what has been difficult, what they have tried, and what a good outcome looks like.

## Diagnostics

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

## Score history

- 2026-11-06: 74
- 2026-11-05: 73
- 2026-11-04: 73
- 2026-11-03: 72
- 2026-11-02: 72

## Common questions

### What is the The Landing Company of Madison Park MCP server?

The Landing Company of Madison Park is an MCP server listed in the public MCP registry as com.landingonmadison/landing-company. Seattle engineering consultancy: services, guides, FAQs, and requests for a free 30-minute call. This page covers its hosted endpoint (https://landingonmadison.com/mcp).

### Is the The Landing Company of Madison Park MCP server safe to use?

The Landing Company of Madison Park scores 74 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 The Landing Company of Madison Park MCP server expose?

The Landing Company of Madison Park exposes 7 tools: get_firm_overview, list_services, get_approach, get_faq, list_guides, and 2 more. Their descriptions and schemas cost roughly 364 tokens of context every time the server is loaded.

### Does the The Landing Company of Madison Park MCP server require authentication?

No. We connected to The Landing Company of Madison Park without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the The Landing Company of Madison Park MCP server still maintained?

The Landing Company of Madison Park is still listed as active in the MCP registry. We last reached this channel on 6 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 The Landing Company of Madison Park MCP server?

VerifyMCP ran 13 checks on The Landing Company of Madison Park, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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://landingonmadison.com/mcp
- Website: https://landingonmadison.com/connector
- Changelog RSS feed: https://verifymcp.io/servers/com-landingonmadison-landing-company/landingonmadison.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-landingonmadison-landing-company/landingonmadison/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-landingonmadison-landing-company/landingonmadison.json
- HTML version of this page: https://verifymcp.io/servers/com-landingonmadison-landing-company/landingonmadison