IPinfo MCP integration for AI agents.
Connect AI agents to IPinfo through 27 structured actions, including batch lite lookup, map ips, and batch lookup. Review authentication, inputs, workflows…
- ACTION CONTRACTS
- 27
- 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 IPinfo integration exposes
The IPinfo Agent App exposes 27 provider-backed actions for location and data work. Its current contract lets an authorized agent look up multiple lite api ips or field paths in a single batch request, upload up to 500,000 ip addresses to the ipinfo map tool and return the generated report url, and look up multiple ipinfo legacy or lite-compatible paths in a single batch request through the legacy batch endpoint. 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 IPinfo account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real IPinfo capabilities.
Showing 12 of 27 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
batch_lite_lookupREADLook up multiple Lite API IPs or field paths in a single batch request.
INPUTS: queries
map_ipsREVIEWUpload up to 500,000 IP addresses to the IPinfo map tool and return the generated report URL.
INPUTS: ipAddresses / cli
batch_lookupREADLook up multiple IPinfo legacy or Lite-compatible paths in a single batch request through the legacy batch endpoint.
INPUTS: ips / filter
get_abuse_contactREADRetrieve abuse contact data for a specific IP address when the token includes that dataset.
INPUTS: ip
get_carrier_infoREADRetrieve carrier enrichment data for a specific IP address when the token includes that dataset.
INPUTS: ip
get_city_by_ipREADRetrieve the city name for a specific IP address.
INPUTS: ip
get_company_infoREADRetrieve company enrichment data for a specific IP address when the token includes that dataset.
INPUTS: ip
get_core_field_by_meREADRetrieve a single Lookup API core field for the caller's current IP address.
INPUTS: field
get_country_by_ipREADRetrieve the ISO 3166-1 alpha-2 country code for a specific IP address.
INPUTS: ip
get_current_ipREADRetrieve the caller's current public IP address as plain text.
get_current_ip_infoREADRetrieve the full legacy IPinfo profile for the caller's current IP address, including location, ASN, company, privacy, carrier, abuse, and hosted domain data when available.
get_current_locREADRetrieve the caller's current coordinates in latitude,longitude format.
INPUT CONTRACTS
Know what the action needs before it runs.
batch_lite_lookup
queriesOPTIONAL- The Lite API queries to send to the batch lookup endpoint.
map_ips
ipAddressesREQUIRED- The IP addresses to upload to the IPinfo map tool.
cliOPTIONAL- The optional CLI mode flag accepted by the IPinfo map tool.
batch_lookup
ipsREQUIRED- The IP addresses or field paths to send to the batch lookup endpoint.
filterOPTIONAL- Whether null results should be omitted from the returned map.
get_abuse_contact
ipOPTIONAL- The IPv4 or IPv6 address to look up.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Batch Lite Lookup
Look up multiple Lite API IPs or field paths in a single batch request. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
batch_lite_lookupVerify with Batch Lookup
Look up multiple IPinfo legacy or Lite-compatible paths in a single batch request through the legacy batch endpoint. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
batch_lookupSAFETY BOUNDARY
Operate IPinfo with explicit limits
- Authorize IPinfo with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned IPinfo 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 IPinfo rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the IPinfo task completed successfully.
CONNECTION MODEL
API key
IPinfo access token used to authenticate API requests. Get it from the IPinfo dashboard: https://ipinfo.io/dashboard/lite.
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
- 26
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
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 IPinfo.