# com.robtex/mcp (remote · mcp.robtex.com)

DNS, IP, AS, domain reputation, and Lightning Network intelligence (44 tools)

- Trust score: 73/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.robtex.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-robtex-mcp/mcp.md), [page](https://verifymcp.io/servers/com-robtex-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.robtex.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-08-03.

- **Endpoint Security**: 77/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 is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 3385 tokens (~73/item across 46 items; 46 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-robtex-mcp https://mcp.robtex.com/mcp
```

### Codex

```toml
[mcp_servers.com-robtex-mcp]
url = "https://mcp.robtex.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-robtex-mcp --url https://mcp.robtex.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-robtex-mcp:
    url: "https://mcp.robtex.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-robtex-mcp": {
      "type": "http",
      "url": "https://mcp.robtex.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-08-02 (score 73, +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.

### 2026-07-31 (score 72, +3)

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

### 2026-07-30 (score 69, −2)

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

### 2026-07-29 (score 71, +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-07-28 (score 70, +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-07-27 (score 69, 0)

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

### 2026-07-26 (score 69)

First indexed and scored.

## MCP tools (46)

### `latest_lightning_channels` (~42 tokens)

Returns the most recently opened Lightning Network channels, sorted by open time descending.

Input parameters:

- `count` (integer): Number of channels to return (1-1000)

### `ip_reputation` (~82 tokens)

Check an IP address reputation against 100+ real-time blocklists (DNSBLs). Returns listing status, threat categories, AS info, and blocklist details.

Input parameters:

- `ip` (string, required): IPv4 or IPv6 address to check (e.g., 8.8.8.8, 2001:4860:4860::8888)

### `lookup_dns` (~74 tokens)

Lookup DNS records (A, AAAA, MX, NS, TXT, CNAME, SOA) for a given hostname. Also returns domain reputation info (Majestic, Tranco rankings, blocklist status).

Input parameters:

- `hostname` (string, required): Hostname or domain to lookup (e.g., example.com, www.example.com)

### `reverse_lookup_dns_records` (~161 tokens)

Find hostnames that use a specific DNS record value. Query which hostnames point to an IP address, use a particular nameserver, or reference any DNS value. For example: 'which hostnames point to 1.2.3.4?' or 'which hostnames use chris.ns.cloudflare.com as their nameserver?'

Input parameters:

- `limit` (integer): Maximum number of hostnames to return
- `offset` (integer): Offset for pagination
- `record_type` (string): Type of DNS record to search (A, AAAA, NS, MX, CNAME, TXT)
- `value` (string, required): The DNS record value to search for (e.g., IP address, nameserver hostname, mail server, CNAME target)

### `reverse_lookup_mx` (~92 tokens)

Find hostnames that use a specific mail server. For example: which hostnames use aspmx.l.google.com as their mail server?

Input parameters:

- `limit` (integer): Maximum number of hostnames to return
- `mx_server` (string, required): The mail server hostname to search for (e.g., aspmx.l.google.com, mx1.example.com)
- `offset` (integer): Offset for pagination

### `reverse_lookup_ns` (~89 tokens)

Find hostnames that use a specific nameserver. For example: which hostnames use chris.ns.cloudflare.com as their nameserver?

Input parameters:

- `limit` (integer): Maximum number of hostnames to return
- `nameserver` (string, required): The nameserver hostname to search for (e.g., chris.ns.cloudflare.com, ns1.example.com)
- `offset` (integer): Offset for pagination

### `reverse_lookup_ip` (~94 tokens)

Find hostnames that point to a specific IP address (IPv4 or IPv6). Searches both A and AAAA records. For example: which hostnames point to 1.2.3.4?

Input parameters:

- `ip` (string, required): The IP address to search for (IPv4 or IPv6)
- `limit` (integer): Maximum number of hostnames to return
- `offset` (integer): Offset for pagination

### `historic_reverse_lookup_ns` (~89 tokens)

Find hostnames that *previously* used a specific nameserver but no longer do. Tracks infrastructure migrations and past delegation relationships.

Input parameters:

- `limit` (integer): Maximum number of hostnames to return
- `nameserver` (string, required): The nameserver hostname to search for (e.g., chris.ns.cloudflare.com, ns1.example.com)
- `offset` (integer): Offset for pagination

### `historic_reverse_lookup_mx` (~92 tokens)

Find hostnames that *previously* used a specific mail server but no longer do. Tracks email provider migrations and past MX relationships.

Input parameters:

- `limit` (integer): Maximum number of hostnames to return
- `mx_server` (string, required): The mail server hostname to search for (e.g., aspmx.l.google.com, mx1.example.com)
- `offset` (integer): Offset for pagination

### `historic_reverse_lookup_ip` (~88 tokens)

Find hostnames that *previously* pointed to a specific IP address but no longer do. Tracks hosting migrations and past IP relationships. Searches both A and AAAA records.

Input parameters:

- `ip` (string, required): The IP address to search for (IPv4 or IPv6)
- `limit` (integer): Maximum number of hostnames to return
- `offset` (integer): Offset for pagination

### `lookup_mac` (~111 tokens)

Look up the manufacturer/vendor of a network device by its MAC address. Uses the official IEEE OUI (Organizationally Unique Identifier) database with ~30K entries.

Input parameters:

- `mac_address` (string, required): MAC address to look up (e.g., D8:A3:5C:12:34:56, D8-A3-5C-12-34-56, or D8A35C123456). Only the first 6 hex characters (OUI prefix) are used.

### `lookup_as_whois` (~69 tokens)

Lookup WHOIS information for an Autonomous System (AS) number from the RADB routing database. Returns routing policy, network information, and administrative contacts.

Input parameters:

- `asn` (string, required): AS number to lookup (e.g., "AS15169" or "15169" for Google)

### `lookup_lightning_node` (~55 tokens)

Lookup a Lightning Network node by public key. Returns node alias, peer count, channel count, and centrality ranking.

Input parameters:

- `pubkey` (string, required): Compressed secp256k1 public key (66 hex chars)

### `lookup_lightning_channel` (~64 tokens)

Lookup a Lightning channel by channel ID. Supports numeric, block x txn x vout, or block:txn:vout formats.

Input parameters:

- `channel_id` (string, required): Lightning channel ID (numeric, blockxtxnxvout, or block:txn:vout format)

### `lookup_lightning_channels_per_node` (~68 tokens)

Lookup all Lightning Network channels for a given node by public key.

Input parameters:

- `limit` (integer): Maximum number of channels to return
- `node` (string, required): Compressed secp256k1 public key (66 hex chars)
- `offset` (integer): Offset for pagination

### `get_recommended_lightning_peers` (~90 tokens)

Get recommended Lightning Network peers for a given node. Returns nodes that are NOT currently peered with the specified node but would improve its centrality score if connected.

Input parameters:

- `limit` (integer): Maximum number of recommended peers to return
- `offset` (integer): Offset for pagination
- `pubkey` (string, required): Compressed secp256k1 public key (66 hex chars)

### `search_lightning_nodes_by_alias` (~72 tokens)

Search for Lightning Network nodes by partial alias match. Returns nodes whose aliases contain the search term (case-insensitive).

Input parameters:

- `alias` (string, required): Search term to match against node aliases
- `limit` (integer): Maximum number of nodes to return
- `offset` (integer): Offset for pagination

### `domain_rdap` (~95 tokens)

Queries the authoritative RDAP registry for a domain. Returns availability status (HTTP 404 = available), and for registered domains: registrar name, registration/expiration dates, nameservers, DNSSEC status, and domain status flags. Uses IANA bootstrap to find the correct RDAP server per TLD. Covers 590+ TLDs.

Input parameters:

- `domain` (string, required): Domain name to look up (e.g., example.com)

### `parse_hostname` (~98 tokens)

Parse a hostname into its constituent parts using the Mozilla Public Suffix List (9700+ entries). Returns eTLD (effective TLD), registered domain, subdomain, labels, and depth. Handles multi-level eTLDs (co.uk, co.jp, com.au) and platform suffixes (github.io, herokuapp.com).

Input parameters:

- `hostname` (string, required): Hostname to parse (e.g. www.mail.example.co.uk)

### `is_subdomain` (~50 tokens)

Check whether a hostname is a subdomain (has labels beyond the registered domain). Uses the Mozilla Public Suffix List for accurate eTLD detection.

Input parameters:

- `hostname` (string, required): Hostname to check

### `registered_domain` (~50 tokens)

Extract the registered domain (eTLD+1) from a hostname. For example, www.mail.example.co.uk returns example.co.uk.

Input parameters:

- `hostname` (string, required): Hostname to extract registered domain from

### `tld_info` (~85 tokens)

Get information about a top-level domain or effective TLD. Returns whether it is in the Public Suffix List, how many sub-suffixes exist, and classification (ccTLD, gTLD, or infrastructure).

Input parameters:

- `tld` (string, required): TLD or eTLD to look up (e.g. "uk", "co.uk", "github.io")

### `reverse_lookup_cname` (~72 tokens)

Find hostnames that have a CNAME record pointing to the specified target. Useful for CDN and load balancer investigations.

Input parameters:

- `limit` (integer): Max results
- `offset` (integer): Offset for pagination
- `target` (string, required): CNAME target hostname (e.g. cdn.cloudflare.net)

### `historic_reverse_lookup_cname` (~67 tokens)

Find hostnames that previously had a CNAME record pointing to the specified target but no longer do. Tracks CDN and infrastructure migrations.

Input parameters:

- `limit` (integer): Max results
- `offset` (integer): Offset for pagination
- `target` (string, required): CNAME target hostname

### `ip_geolocation` (~43 tokens)

Get geographic location data for an IP address: country, city, region, latitude, longitude, timezone.

Input parameters:

- `ip` (string, required): IPv4 or IPv6 address

### `ip_network` (~44 tokens)

Get the containing network (BGP route), AS number, AS name, and route description for an IP address.

Input parameters:

- `ip` (string, required): IPv4 or IPv6 address

### `ip_to_asn` (~48 tokens)

Lightweight lookup: get just the AS number and netblock for an IP address. Fastest way to map IP to ASN.

Input parameters:

- `ip` (string, required): IPv4 or IPv6 address

### `ip_blocklist_check` (~70 tokens)

Check an IP address against IPsum, FireHOL, Tor exit node lists, C2 indicators, Roskomnadzor (Russia), and other threat intelligence feeds. Returns which lists the IP appears on and threat scores.

Input parameters:

- `ip` (string, required): IPv4 or IPv6 address to check

### `ip_threat_intel` (~56 tokens)

Combined threat intelligence: DNSBL listings, IPsum score, FireHOL lists, bad ASN flag, Tor exit status. Comprehensive threat assessment for an IP address.

Input parameters:

- `ip` (string, required): IPv4 or IPv6 address

### `as_info` (~55 tokens)

Get the name, organization, country, and description for an Autonomous System number. Lightweight version of as_whois.

Input parameters:

- `asn` (string, required): AS number (e.g. "AS15169" or "15169")

### `as_prefixes` (~57 tokens)

Get all IPv4 and IPv6 network prefixes (netblocks) announced by an Autonomous System. Returns BGP-visible routes.

Input parameters:

- `asn` (string, required): AS number (e.g. "AS15169" or "15169")

### `domain_reputation` (~58 tokens)

Get comprehensive domain reputation: Majestic rank, Tranco rank, HaGeZi blocklist status, Blackbook malware status, phishing database status, HSTS preload status, and disposable email detection.

Input parameters:

- `hostname` (string, required): Domain to check

### `domain_ranking` (~80 tokens)

Get domain popularity rankings from five independent sources: Majestic Million (backlinks), Tranco top 1M (aggregated traffic), Cloudflare Radar (1.1.1.1 DNS query popularity), Cisco Umbrella (OpenDNS query popularity), and Chrome UX Report (real Chrome user traffic).

Input parameters:

- `hostname` (string, required): Domain to check

### `domain_blocklist_check` (~66 tokens)

Check a domain against HaGeZi DNS blocklists, Steven Black unified hosts, Blackbook malware list, phishing databases, Roskomnadzor (Russia), and Citizen Lab censorship lists. Returns which lists the domain appears on.

Input parameters:

- `hostname` (string, required): Domain to check

### `dns_differential` (~41 tokens)

Resolve a domain through filtered public DNS resolvers and their unfiltered controls to detect provider threat-feed blocks.

Input parameters:

- `domain` (string, required): Domain to check

### `domain_shared_ip` (~63 tokens)

Find other domains hosted on the same IP address(es) as the target domain. Resolves the domain's A records, then performs reverse IP lookups for each.

Input parameters:

- `hostname` (string, required): Domain to check
- `limit` (integer): Max results per IP

### `domain_shared_ns` (~62 tokens)

Find other domains using the same nameserver(s) as the target domain. Resolves the domain's NS records, then performs reverse NS lookups for each.

Input parameters:

- `hostname` (string, required): Domain to check
- `limit` (integer): Max results per NS

### `domain_shared_mx` (~63 tokens)

Find other domains using the same mail server(s) as the target domain. Resolves the domain's MX records, then performs reverse MX lookups for each.

Input parameters:

- `hostname` (string, required): Domain to check
- `limit` (integer): Max results per MX

### `check_email` (~74 tokens)

Verify an email address by connecting to its mail server via SMTP. Checks MX records, tests if the address is accepted (RCPT TO), detects catch-all domains, and reports TLS support. Results are RAM-cached for 1 hour.

Input parameters:

- `email` (string, required): Email address to verify (e.g., user@example.com)

### `ping` (~20 tokens)

Check if the API is responding. Returns status and server timestamp.

### `lookup_bitcoin_transaction` (~65 tokens)

Returns full transaction details: inputs with addresses and values, outputs with spent status, fee, size/weight, SegWit flag, and Lightning Network channel correlation. Supports both confirmed and mempool transactions.

Input parameters:

- `txid` (string, required): Transaction ID (64 hex characters)

### `lookup_bitcoin_address` (~90 tokens)

Returns address balance, total received/sent, transaction counts, address type (P2PKH, P2SH, P2WPKH, P2TR), first/last seen block, and ransomware/abuse flags. Supports all Bitcoin address formats.

Input parameters:

- `address` (string, required): Bitcoin address (P2PKH, P2SH, Bech32, Bech32m)

### `lookup_bitcoin_block` (~57 tokens)

Returns block header (hash, timestamp, version, merkle root, difficulty, nonce), transaction count, and list of transaction IDs. Supports lookup by block height.

Input parameters:

- `height` (integer, required): Block height (0 = genesis block)

### `bitcoin_address_transactions` (~77 tokens)

Returns a paginated list of transactions involving a Bitcoin address. Filter by direction: received (incoming funds), sent (outgoing funds), or all. Returns up to 100 transactions per call, sorted by block height descending (most recent first).

Input parameters:

- `address` (string, required): Bitcoin address
- `direction` (string): Transaction direction filter

### `bitcoin_transaction_spends` (~56 tokens)

For a given transaction, returns which subsequent transactions consumed its outputs. Useful for UTXO tracking and chain analysis. Shows the spending txid for each output.

Input parameters:

- `txid` (string, required): Transaction ID (64 hex characters)

### `bitcoin_blockchain_stats` (~191 tokens)

Returns cumulative blockchain metrics over a configurable block range. Available metrics include: txs, fees, segwittx, inputs, outputs, insats, outsats, btcusd, volusd, unspentoutputs, fullyspent, unspentsats, addresses, satoshiblocks, clnopen, clnclose, satlnopen, satlnclose, basereward, blockreward, batched, rbf, version2tx, lowestfee, and more. Returns sampled data points suitable for charting.

Input parameters:

- `endBlock` (integer): End block height (defaults to latest)
- `metric` (string, required): Metric name (e.g., txs, fees, segwittx, btcusd, clnopen)
- `samples` (integer): Number of data points to return (evenly spaced across range)
- `startBlock` (integer): Start block height

## Diagnostics

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

## Score history

- 2026-08-03: 73
- 2026-08-02: 73
- 2026-08-01: 72
- 2026-07-31: 72
- 2026-07-30: 69
- 2026-07-29: 71
- 2026-07-28: 70
- 2026-07-27: 69
- 2026-07-26: 69

## Links

- Remote endpoint: https://mcp.robtex.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-robtex-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-robtex-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-robtex-mcp/mcp