# Landfall (remote · landfall-production-74ad.up.railway.app)

Local business leads and website intelligence for AI agents: lead lists, contacts, tracking, SEO and

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

## Components

- remote · `landfall-production-74ad.up.railway.app`: 78/100 (this document), [markdown](https://verifymcp.io/servers/landfall-audit-landfall/v1-mcp.md), [page](https://verifymcp.io/servers/landfall-audit-landfall/v1-mcp)

## Channel facts

- Endpoint: `https://landfall-production-74ad.up.railway.app/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.4.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**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **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 Landfall MCP server?

Landfall is a hosted endpoint at https://landfall-production-74ad.up.railway.app/v1/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 landfall-audit-landfall 'https://landfall-production-74ad.up.railway.app/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "landfall-audit-landfall": {
      "url": "https://landfall-production-74ad.up.railway.app/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "landfall-audit-landfall": {
      "type": "http",
      "url": "https://landfall-production-74ad.up.railway.app/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.landfall-audit-landfall]
url = "https://landfall-production-74ad.up.railway.app/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "landfall-audit-landfall": {
      "type": "remote",
      "url": "https://landfall-production-74ad.up.railway.app/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add landfall-audit-landfall --url 'https://landfall-production-74ad.up.railway.app/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  landfall-audit-landfall:
    url: "https://landfall-production-74ad.up.railway.app/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "landfall-audit-landfall": {
      "Transport": "http",
      "Url": "https://landfall-production-74ad.up.railway.app/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add landfall-audit-landfall -t streamable-http -u 'https://landfall-production-74ad.up.railway.app/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "landfall-audit-landfall": {
      "type": "http",
      "url": "https://landfall-production-74ad.up.railway.app/v1/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-05 (score 78, +74)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-11-04 (score 4, −73)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] HSTS header: fail → unverified
- [security regression] Stability: 0.60 → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-02 (score 77, +1)

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

### 2026-10-30 (score 76, +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-10-28 (score 75, +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-10-26 (score 74, +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-10-24 (score 73, +1)

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

### 2026-10-22 (score 72, +1)

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

## MCP tools (8)

### `audit_landing_page` (~140 tokens)

Audit a landing page for paid ads (paid)

Audit a landing page before sending paid ad traffic. Returns a 0-100 readiness score, a ready / fix_first / not_ready verdict, Meta, Google and TikTok tags with IDs, conversion paths (forms, click-to-call, WhatsApp, booking), trust and speed facts, and the top 5 fixes in priority order. Costs 0.05 USDC per completed call, paid automatically via x402 if your client supports it. Never charged if the call fails.

Input parameters:

- `keyword` (string): Optional ad keyword or headline to check message match
- `url` (string, required): Public http(s) URL of the page or website

### `get_business_details` (~129 tokens)

Get contact and business details from a website (paid)

Extract contact and business details from a company website: name, phone numbers (normalised), emails, WhatsApp, postal address, opening hours, social profiles, review platforms, booking and chat tools, UK company and VAT numbers, and page headings. Reads the homepage plus its contact page when the homepage lacks a phone or email. Every value comes from the site itself. Costs 0.02 USDC per completed call, paid automatically via x402 if your client supports it. Never charged if the call fails.

Input parameters:

- `url` (string, required): Public http(s) URL of the page or website

### `check_tracking` (~125 tokens)

Check a website's ad pixels and analytics (paid)

Check which ad pixels and analytics a website runs: Meta Pixel, Google Ads and TikTok tags with their IDs, Google Analytics 4, tag managers (Google, Tealium, Adobe and others), conversion events, cookie consent tools and Google Consent Mode, the site platform (WordPress, Wix, Shopify, Squarespace...) and booking/chat tools. Costs 0.01 USDC per completed call, paid automatically via x402 if your client supports it. Never charged if the call fails.

Input parameters:

- `url` (string, required): Public http(s) URL of the page or website

### `check_structured_data` (~152 tokens)

Check a page's structured data (schema.org) (paid)

Check a page's structured data: finds every schema.org item (JSON-LD, microdata, RDFa), reports JSON-LD that does not parse, checks each item against the required and recommended properties for common types (LocalBusiness, Organization, Product, Offer, Article, FAQPage, BreadcrumbList, Event, Review, JobPosting and more), flags bad dates, ratings and URLs, and reports Open Graph, Twitter card and canonical tags, with a list of fixes. Costs 0.01 USDC per completed call, paid automatically via x402 if your client supports it. Never charged if the call fails.

Input parameters:

- `url` (string, required): Public http(s) URL of the page or website

### `check_crawlability` (~167 tokens)

Check whether search engines and AI crawlers can read a site (paid)

Check whether search engines and AI crawlers may read a page and how the site is mapped: robots.txt evaluated with Google's matching rules for Googlebot, Bingbot, GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Google-Extended, PerplexityBot, CCBot, Applebot-Extended and others (with the rule that decided each), meta robots and X-Robots-Tag, canonical link, declared sitemaps with entry counts and freshness, and llms.txt, with a list of fixes. Costs 0.01 USDC per completed call, paid automatically via x402 if your client supports it. Never charged if the call fails.

Input parameters:

- `url` (string, required): Public http(s) URL of the page or website

### `full_site_report` (~128 tokens)

Full site report: every check in one call (paid)

Every Landfall check in one call, for less than the tools cost separately: the landing page audit, business contact details, tracking and pixel check, structured data check and crawlability check, from a single read of the page. Ideal for agency audits, lead qualification and prospect research. Costs 0.08 USDC per completed call, paid automatically via x402 if your client supports it. Never charged if the call fails.

Input parameters:

- `keyword` (string): Optional ad keyword or headline to check message match
- `url` (string, required): Public http(s) URL of the page or website

### `preview_landing_page` (~82 tokens)

Preview a landing page audit (free)

Free quick check of a landing page: ready / fix_first / not_ready verdict, 0-100 score, issue counts and the most important blocker. Limited per hour. Use audit_landing_page for the evidence and fixes.

Input parameters:

- `url` (string, required): Public http(s) URL of the landing page, e.g. https://example.com/offer

### `sample_audit` (~28 tokens)

Example audit report (free)

Returns a complete example audit report for a fictional page, showing every field the paid audit returns.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/landfall-audit-landfall/v1-mcp#diagnostics

## Score history

- 2026-11-05: 78
- 2026-11-04: 4
- 2026-11-03: 77
- 2026-11-02: 77
- 2026-11-01: 76
- 2026-10-31: 76
- 2026-10-30: 76
- 2026-10-29: 75
- 2026-10-28: 75
- 2026-10-27: 74
- 2026-10-26: 74
- 2026-10-25: 73
- 2026-10-24: 73
- 2026-10-23: 72
- 2026-10-22: 72
- 2026-10-21: 71
- 2026-10-20: 71
- 2026-10-19: 70
- 2026-10-18: 70
- 2026-10-17: 70
- 2026-10-16: 70
- 2026-10-15: 23

## Common questions

### What is the Landfall MCP server?

Landfall is an MCP server listed in the public MCP registry as io.github.landfall-audit/landfall. Local business leads and website intelligence for AI agents: lead lists, contacts, tracking, SEO and. This page covers its hosted endpoint (https://landfall-production-74ad.up.railway.app/v1/mcp).

### Is the Landfall MCP server safe to use?

Landfall scores 78 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 Landfall MCP server expose?

Landfall exposes 8 tools: audit_landing_page, get_business_details, check_tracking, check_structured_data, check_crawlability, and 3 more. Their descriptions and schemas cost roughly 951 tokens of context every time the server is loaded.

### Does the Landfall MCP server require authentication?

Its publisher declares no required credentials for Landfall. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Landfall MCP server still maintained?

Landfall is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 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://landfall-production-74ad.up.railway.app/v1/mcp
- Website: https://landfall-production-74ad.up.railway.app/docs
- Changelog RSS feed: https://verifymcp.io/servers/landfall-audit-landfall/v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/landfall-audit-landfall/v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/landfall-audit-landfall/v1-mcp