How to Use the IPinfo MCP in LangChain

Q: Does the IPinfo toolset support LangSmith tracing in LangChain?

Every call to getprivacydetails or getiprange registers as a tool run in LangSmith automatically. You get full visibility into the exact latency, input parameters, and raw JSON outputs returned by the server.

Q: How do I check the host server's own IP address in LangChain?

Your agent calls getownipdetails to resolve the current server's public IP address. This tool returns the active network details, allowing your LangChain routing logic to adapt based on its own deployment location.

Feed real-time IP telemetry straight into your LangChain reasoning loops using this MCP Server.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect IPinfo MCP to LangChain

Create your Vinkius account to connect IPinfo to LangChain and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup IPinfo with LangChain

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Link network data to agent decisions

`get_ip_details` pulls geographical coordinates and ISP ownership data directly into your active LangChain run via our MCP integration. Your agent reads this output, evaluates the risk level, and immediately decides which custom tool to execute next. By chaining this with `get_asn_details`, the agent maps out the origin network before executing downstream security actions. LangSmith traces every tool execution so you see exactly how these network decisions affect your pipeline latency.

Evaluate VPN traffic inside LangChain chains

`get_privacy_details` exposes active VPNs, proxies, and Tor exit nodes during an active run. The agent intercepts the traffic data and branches the execution path based on the privacy flags it finds. You can feed this raw JSON output directly into subsequent chain links to block or flag suspicious requests. This setup removes the guesswork from agentic routing by feeding verified privacy telemetry straight into your decision logic.

Audit network ranges using this MCP Server

`get_ip_range` retrieves the full CIDR block details to help your agent map out entire malicious subnets. The chain processes the block data, identifies potential collateral damage, and generates precise firewall rules. If the agent needs historical context, it calls `get_ip_historical` to check past ownership records within your LangChain MCP setup. This multi-server setup gives your LangChain agent the exact network parameters it needs to secure your infrastructure.

Setup guide

Set up IPinfo MCP in LangChain

Prerequisites

Python 3.10+ installed
langchain-mcp-adapters + langgraph packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install langchain-mcp-adapters langgraph langchain-openai. The MCP adapters package converts MCP tools into native LangChain BaseTool objects.
2

Connect via HTTP transport
Use MultiServerMCPClient with "transport": "http" pointing to your Vinkius endpoint. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Create a ReAct agent
Pass the discovered tools to create_react_agent() from LangGraph. The agent automatically routes IPinfo tool calls through the MCP protocol.
4

Run with any LLM
Swap ChatOpenAI for ChatAnthropic, ChatGoogleGenerativeAI, or any LangChain-compatible model. The MCP tools work identically across all providers.

agent.py

from langchain_mcp_adapters.client import MultiServerMCPClient
from langgraph.prebuilt import create_react_agent
from langchain_openai import ChatOpenAI

async with MultiServerMCPClient({
    "ipinfo-mcp": {
        "transport": "http",
        "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    }
}) as client:
    tools = client.get_tools()

    agent = create_react_agent(
        ChatOpenAI(model="gpt-4o"),
        tools,
    )
    result = await agent.ainvoke({
        "messages": "List recent IPinfo transactions"
    })
    print(result["messages"][-1].content)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by IPinfo. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect IPinfo now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about IPinfo MCP in LangChain

Instantiate the MultiServerMCPClient with the Vinkius transport URL, then pull the tools using client.get_tools(). Pass those tools directly to your LangChain agent constructor to let it call get_ip_details dynamically.

Yes, you should configure your LangChain run with standard error-handling chains to catch rate limits. The agent will read the API error from get_ip_details or get_asn_details and can retry the call or fall back gracefully.

Every call to get_privacy_details or get_ip_range registers as a tool run in LangSmith automatically. You get full visibility into the exact latency, input parameters, and raw JSON outputs returned by the server.

Your agent calls get_own_ip_details to resolve the current server's public IP address. This tool returns the active network details, allowing your LangChain routing logic to adapt based on its own deployment location.

Only the target IP addresses, range queries, or ASNs you explicitly pass to tools like get_privacy_details leave your local environment. Vinkius processes these parameters through an ephemeral, zero-trust sandbox to ensure no raw network payloads or client credentials are ever exposed or stored.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript