Landfall
REMOTE · LANDFALL-PRODUCTION-74AD.UP.RAILWAY.APP
Local business leads and website intelligence for AI agents: lead lists, contacts, tracking, SEO and
Available components
Last scanned (3 hours ago)
Scores higher than 76% of remote servers
Unreachable for 1 day in a row. Last reached 4 Nov 2026.
Category Marketing and SEO
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. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +74
The score moved with no change recorded against any check. We would rather say so than guess.
- 4 Nov 26 −73
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: 0.60 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 2 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +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.
- 22 Oct 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://landfall-production-74ad.up.railway.app/v1/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of landfall-production-74ad.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://landfall-production-74ad.up.railway.app/v1/mcp | Unreachable | ||
| http (plaintext) | http://landfall-production-74ad.up.railway.app/v1/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_landing_page Audit a landing page for paid ads (paid) ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | – | Optional ad keyword or headline to check message match |
| url | string | yes | Public http(s) URL of the page or website |
No output schema declared.
No examples provided.
check_crawlability Check whether search engines and AI crawlers can read a site (paid) ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public http(s) URL of the page or website |
No output schema declared.
No examples provided.
check_structured_data Check a page's structured data (schema.org) (paid) ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public http(s) URL of the page or website |
No output schema declared.
No examples provided.
check_tracking Check a website's ad pixels and analytics (paid) ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public http(s) URL of the page or website |
No output schema declared.
No examples provided.
full_site_report Full site report: every check in one call (paid) ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | – | Optional ad keyword or headline to check message match |
| url | string | yes | Public http(s) URL of the page or website |
No output schema declared.
No examples provided.
get_business_details Get contact and business details from a website (paid) ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public http(s) URL of the page or website |
No output schema declared.
No examples provided.
preview_landing_page Preview a landing page audit (free) ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public http(s) URL of the landing page, e.g. https://example.com/offer |
No output schema declared.
No examples provided.
sample_audit Example audit report (free) ~28
Returns a complete example audit report for a fictional page, showing every field the paid audit returns.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
remote · landfall-production-74ad.up.railway.app
claude mcp add --transport http landfall-audit-landfall 'https://landfall-production-74ad.up.railway.app/v1/mcp'
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.