# Website Contact & Social Extractor (remote · contacts.noahsarch.tech)

Emails, phones, WhatsApp, social profiles and addresses from a website's public pages.

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

## Components

- remote · `contacts.noahsarch.tech`: 68/100 (this document), [markdown](https://verifymcp.io/servers/tech-noahsarch-website-contact-extractor/contacts.md), [page](https://verifymcp.io/servers/tech-noahsarch-website-contact-extractor/contacts)

## Channel facts

- Endpoint: `https://contacts.noahsarch.tech/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-11-04.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, 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**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1490 tokens (~212/item across 7 items; 5 tools + 2 resources), over budget; trim descriptions and params.
  - 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).
  - 81% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Website Contact & Social Extractor MCP server?

Website Contact & Social Extractor is a hosted endpoint at https://contacts.noahsarch.tech/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 tech-noahsarch-website-contact-extractor 'https://contacts.noahsarch.tech/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tech-noahsarch-website-contact-extractor": {
      "url": "https://contacts.noahsarch.tech/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tech-noahsarch-website-contact-extractor": {
      "type": "http",
      "url": "https://contacts.noahsarch.tech/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tech-noahsarch-website-contact-extractor]
url = "https://contacts.noahsarch.tech/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tech-noahsarch-website-contact-extractor": {
      "type": "remote",
      "url": "https://contacts.noahsarch.tech/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tech-noahsarch-website-contact-extractor --url 'https://contacts.noahsarch.tech/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tech-noahsarch-website-contact-extractor:
    url: "https://contacts.noahsarch.tech/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tech-noahsarch-website-contact-extractor": {
      "Transport": "http",
      "Url": "https://contacts.noahsarch.tech/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tech-noahsarch-website-contact-extractor -t streamable-http -u 'https://contacts.noahsarch.tech/mcp'
```

### Other

```json
{
  "mcpServers": {
    "tech-noahsarch-website-contact-extractor": {
      "type": "http",
      "url": "https://contacts.noahsarch.tech/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-03 (score 68, +1)

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

### 2026-11-01 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-31 (score 66)

First indexed and scored.

## MCP tools (5)

### `extract_contacts` (~347 tokens)

Extract contacts from a website

Fetch a site's homepage and up to max_pages-1 contact/about pages and return every email, phone (validated, E.164, type), WhatsApp link, social profile, postal address and organisation field found, with provenance per item. Example: url 'noahsarch.tech', max_pages 3, region 'AE'. Response: result with emails[] (email, source, role), phones[] (e164, international, region, type, source), whatsapp[], social{platform: [url, handle]}, addresses[], organization{}, pages[] (what was fetched, status) and summary{}, plus data_confidence, estimated_items[], sources[], data_version, warnings[] and a disclaimer. Charged per page actually fetched; failed fetches are free. URLs are not logged.

Input parameters:

- `follow_contact_pages` (boolean): Also fetch the site's contact/about/impressum pages (same site only).
- `include_social` (boolean): Include social-profile links (Facebook, Instagram, X, LinkedIn, YouTube, TikTok, Telegram, Snapchat, Pinterest, Threads, GitHub…).
- `max_pages` (integer): Homepage plus up to (max_pages-1) contact/about pages found on it. 1 = homepage only.
- `region`: ISO 3166-1 alpha-2 country used to interpret phone numbers written without a country code (e.g. 'AE', 'GB', 'US'). Omit if unknown.
- `respect_robots` (boolean): Honour the site's robots.txt (default). Set false only for sites you own.
- `url` (string, required): Website URL (scheme optional): 'example.com' or 'https://example.com/about'.

### `find_social_profiles` (~169 tokens)

Find a website's social-media profiles

Homepage only: Facebook, Instagram, X/Twitter, LinkedIn, YouTube, TikTok, Telegram, Snapchat, Pinterest, Threads, GitHub, TripAdvisor, Google Business links plus WhatsApp chat links, with handles. Share buttons are excluded. Example: url 'https://example.com'. Response: result with emails[] (email, source, role), phones[] (e164, international, region, type, source), whatsapp[], social{platform: [url, handle]}, addresses[], organization{}, pages[] (what was fetched, status) and summary{}, plus data_confidence, estimated_items[], sources[], data_version, warnings[] and a disclaimer. Charged per page actually fetched; failed fetches are free. URLs are not logged.

Input parameters:

- `url` (string, required): Website URL.

### `extract_contacts_bulk` (~253 tokens)

Extract contacts from up to 50 websites

One call for a lead list: each site gets homepage + contact pages (max_pages), results per site plus a summary (sites with email/phone/WhatsApp, failures). Charged per page fetched across all sites. Example: urls ['a.com','b.ae'], max_pages 2, region 'AE'. Response: result with emails[] (email, source, role), phones[] (e164, international, region, type, source), whatsapp[], social{platform: [url, handle]}, addresses[], organization{}, pages[] (what was fetched, status) and summary{}, plus data_confidence, estimated_items[], sources[], data_version, warnings[] and a disclaimer. Charged per page actually fetched; failed fetches are free. URLs are not logged.

Input parameters:

- `include_social` (boolean)
- `max_pages` (integer): Pages per site (homepage + contact pages).
- `region`: ISO 3166-1 alpha-2 country used to interpret phone numbers written without a country code (e.g. 'AE', 'GB', 'US'). Omit if unknown.
- `urls` (array, required): Up to 50 website URLs (one per company). Duplicate sites are merged.

### `extract_from_html` (~238 tokens)

Extract contacts from HTML you already have

Same parser, no fetching: emails (incl. obfuscated 'name [at] domain [dot] com'), phones, WhatsApp, social links, addresses, schema.org organisation data, and the contact-page links present. Free. Example: html '<a href="mailto:x@y.com">'. Response: result with emails[] (email, source, role), phones[] (e164, international, region, type, source), whatsapp[], social{platform: [url, handle]}, addresses[], organization{}, pages[] (what was fetched, status) and summary{}, plus data_confidence, estimated_items[], sources[], data_version, warnings[] and a disclaimer. Charged per page actually fetched; failed fetches are free. URLs are not logged.

Input parameters:

- `base_url`: Page URL, used to resolve relative links and decide which links are same-site.
- `html` (string, required): HTML (or plain text) you already have.
- `region`: ISO 3166-1 alpha-2 country used to interpret phone numbers written without a country code (e.g. 'AE', 'GB', 'US'). Omit if unknown.

### `check_url` (~170 tokens)

Check that a website is reachable

GET the URL (robots-respecting, public hosts only) and report status, final URL after redirects, content type, title, declared languages and whether a contact page is linked. Use before a bulk job or to clean a URL list. Example: url 'example.com'. Response: result with emails[] (email, source, role), phones[] (e164, international, region, type, source), whatsapp[], social{platform: [url, handle]}, addresses[], organization{}, pages[] (what was fetched, status) and summary{}, plus data_confidence, estimated_items[], sources[], data_version, warnings[] and a disclaimer. Charged per page actually fetched; failed fetches are free. URLs are not logged.

Input parameters:

- `respect_robots` (boolean)
- `url` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tech-noahsarch-website-contact-extractor/contacts#diagnostics

## Score history

- 2026-11-04: 68
- 2026-11-03: 68
- 2026-11-02: 67
- 2026-11-01: 67
- 2026-10-31: 66

## Common questions

### What is the Website Contact & Social Extractor MCP server?

Website Contact & Social Extractor is an MCP server listed in the public MCP registry as tech.noahsarch/website-contact-extractor. Emails, phones, WhatsApp, social profiles and addresses from a website's public pages. This page covers its hosted endpoint (https://contacts.noahsarch.tech/mcp).

### Is the Website Contact & Social Extractor MCP server safe to use?

Website Contact & Social Extractor scores 68 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 Website Contact & Social Extractor MCP server expose?

Website Contact & Social Extractor exposes 5 tools: extract_contacts, find_social_profiles, extract_contacts_bulk, extract_from_html, check_url. Their descriptions and schemas cost roughly 1,177 tokens of context every time the server is loaded.

### Does the Website Contact & Social Extractor MCP server require authentication?

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

### Is the Website Contact & Social Extractor MCP server still maintained?

Website Contact & Social Extractor is still listed as active in the MCP registry. 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://contacts.noahsarch.tech/mcp
- Website: https://agents.noahsarch.tech/
- Changelog RSS feed: https://verifymcp.io/servers/tech-noahsarch-website-contact-extractor/contacts.xml
- Changelog JSON feed: https://verifymcp.io/servers/tech-noahsarch-website-contact-extractor/contacts.json
- HTML version of this page: https://verifymcp.io/servers/tech-noahsarch-website-contact-extractor/contacts