IP2WHOIS MCP integration for AI agents.
Connect AI agents to IP2WHOIS through 2 structured actions, including lookup domain and lookup hosted domains. Review authentication, inputs, workflows, and…
- ACTION CONTRACTS
- 2
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the IP2WHOIS integration exposes
The IP2WHOIS Agent App exposes 2 provider-backed actions for security and data work. Its current contract lets an authorized agent look up whois registration details for a domain and list hosted domains associated with an ip address. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected IP2WHOIS account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real IP2WHOIS capabilities.
Showing 2 of 2 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
lookup_domainREADLook up WHOIS registration details for a domain.
INPUTS: domain
lookup_hosted_domainsREADList hosted domains associated with an IP address.
INPUTS: ip / page
INPUT CONTRACTS
Know what the action needs before it runs.
lookup_domain
domainOPTIONAL- The bare domain name to query.
lookup_hosted_domains
ipREQUIRED- The IPv4 or IPv6 address to query.
pageOPTIONAL- The result page to fetch.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Lookup Domain
Look up WHOIS registration details for a domain. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
lookup_domainVerify with Lookup Hosted Domains
List hosted domains associated with an IP address. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
lookup_hosted_domainsSAFETY BOUNDARY
Operate IP2WHOIS with explicit limits
- Authorize IP2WHOIS with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned IP2WHOIS data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in IP2WHOIS rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the IP2WHOIS task completed successfully.
CONNECTION MODEL
API key
IP2WHOIS API key passed with the key query parameter. Register for a free account to get your key: https://www.ip2location.io/ip2whois-documentation
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 2
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by IP2WHOIS.