Skip to main content
Glama
duksh

PeerGlass

by duksh

rir_detect_transfers

Read-onlyIdempotent

Detect historical ownership transfers and cross-registry movements for IP prefixes or ASNs by analyzing consecutive WHOIS record changes.

Instructions

Detect past ownership or cross-RIR transfers for an IP prefix or ASN.

An ownership transfer happens when a registered org (e.g. 'GOOGL-ARIN') changes to another org ('META-1-ARIN') in the registration record. A cross-RIR transfer is rarer — it means the resource physically moved between registries (e.g. from ARIN to RIPE NCC after an acquisition).

Transfer types detected: 🏢 Org Change — The registering organization changed 🌍→🌎 Cross-RIR — The resource moved to a different RIR 🔄 Intra-RIR — Maintainer changed within the same RIR

How it works: compares consecutive historical WHOIS object versions. If 'org' or 'mnt-by' changed between versions, a transfer is flagged. If RIR-specific suffixes in the handles differ, it's cross-RIR.

Results are cached for 12 hours.

Args: params (TransferDetectInput): - resource (str): IP prefix (e.g. '8.8.8.0/24') or ASN (e.g. 'AS15169') - response_format (str): 'markdown' (default) or 'json'

Returns: str: List of detected transfers with dates, types, from/to org, and evidence. JSON schema: { "resource": str, "resource_type": str, "transfers_detected": int, "transfers": [{"transfer_date": str, "transfer_type": str, "from_org": str, "to_org": str, "from_rir": str, "to_rir": str, "evidence": str}], "current_holder": str, "first_registered": str, "sources": [str], "notes": [str] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/duksh/peerglass'

If you have feedback or need assistance with the MCP directory API, please join our Discord server