IPGeolocation.io MCP integration for AI agents.
Connect AI agents to IPGeolocation.io through 3 structured actions, including get astronomy, get timezone, and lookup ip. Review authentication, inputs, work…
- ACTION CONTRACTS
- 3
- 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 IPGeolocation.io integration exposes
The IPGeolocation.io Agent App exposes 3 provider-backed actions for location, data, and developer tools work. Its current contract lets an authorized agent get sunrise, sunset, moonrise, moonset, and moon phase data for a location, get time zone information by ip address, coordinates, location, or time zone name, and look up ip geolocation data with optional field controls. 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 IPGeolocation.io account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real IPGeolocation.io capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_astronomyREADGet sunrise, sunset, moonrise, moonset, and moon phase data for a location.
INPUTS: ip / lat / long / location / date
get_timezoneREADGet time zone information by IP address, coordinates, location, or time zone name.
INPUTS: ip / lat / long / location / timeZone
lookup_ipREADLook up IP geolocation data with optional field controls.
INPUTS: ip / fields / excludes / includeHostname / includeGeoAccuracy
INPUT CONTRACTS
Know what the action needs before it runs.
get_astronomy
ipOPTIONAL- The IPv4 or IPv6 address to look up.
latOPTIONAL- The latitude coordinate.
longOPTIONAL- The longitude coordinate.
locationOPTIONAL- The location string accepted by IPGeolocation.io.
dateOPTIONAL- The date to use for astronomy data in YYYY-MM-DD format.
get_timezone
ipOPTIONAL- The IPv4 or IPv6 address to look up.
latOPTIONAL- The latitude coordinate.
longOPTIONAL- The longitude coordinate.
locationOPTIONAL- The location string accepted by IPGeolocation.io.
timeZoneOPTIONAL- The IANA time zone name.
lookup_ip
ipOPTIONAL- The IPv4 or IPv6 address to look up.
fieldsOPTIONAL- Specific response fields to request from IPGeolocation.io.
excludesOPTIONAL- Specific response fields to exclude from the IPGeolocation.io response.
includeHostnameOPTIONAL- Whether to include hostname data in the geolocation response.
includeGeoAccuracyOPTIONAL- Whether to include geo accuracy fields in the geolocation response.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Astronomy
Get sunrise, sunset, moonrise, moonset, and moon phase data for a location. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_astronomyVerify with Get Timezone
Get time zone information by IP address, coordinates, location, or time zone name. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_timezoneSAFETY BOUNDARY
Operate IPGeolocation.io with explicit limits
- Authorize IPGeolocation.io with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned IPGeolocation.io 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 IPGeolocation.io rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the IPGeolocation.io task completed successfully.
CONNECTION MODEL
API key
IPGeolocation.io API key passed as the apiKey query parameter. Get or manage API keys in the IPGeolocation.io dashboard: https://app.ipgeolocation.io/.
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
- 3
- 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 IPGeolocation.io.