World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
MCP server for the Litport API: create and manage proxies, traffic caps, usage, pools, proxy URLs.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 12/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Litport MCP. Follow https://mcp.popnx.com/i/litportnet-litport-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Litport MCP for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "litport": { "command": "npx", "args": [ "-y", "@litportnet/litport-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Litport MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"litport": {
"command": "npx",
"args": [
"-y",
"@litportnet/litport-mcp"
]
}
}
}Use Litport MCP and tell me what you can do for me, then show me one thing✓ If Claude says it is using Litport MCP or shows a Litport MCP tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Litport MCP yet
Litport MCP runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Litport MCP
B · Others in Other that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Litport MCP for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user litport -- npx -y @litportnet/litport-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Litport MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user litport -- npx -y @litportnet/litport-mcpYou should see Litport MCP listed as connected
Use Litport MCP and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Litport MCP or shows a Litport MCP tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Litport MCP for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "litport": { "command": "npx", "args": [ "-y", "@litportnet/litport-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Litport MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use Litport MCP and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Litport MCP or shows a Litport MCP tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Litport MCP for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "litport": { "type": "stdio", "command": "npx", "args": [ "-y", "@litportnet/litport-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Litport MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use Litport MCP and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Litport MCP or shows a Litport MCP tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user litport -- npx -y @litportnet/litport-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"litport": {
"command": "npx",
"args": [
"-y",
"@litportnet/litport-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"litport": {
"command": "npx",
"args": [
"-y",
"@litportnet/litport-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"litport": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@litportnet/litport-mcp"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account litportnet, which owns the repo
Code last changed 9 days ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for @litportnet/litport-mcp@0.3.0
Checks only this package version, not every dependency · checked Nov 15, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/litportnet-litport-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 9 days ago, and the latest version (0.3.0) reached the registry 9 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| This one Litport MCP | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A Model Context Protocol server for the Litport API: inspect proxy tokens, usage, packages, and pay-per-GB pools/geo targeting; create, change, reissue the credentials of, and delete pay-per-GB proxies; change a token's location, rotation interval, or get a new IP; manage a package's allowed-IP list; build ready-to-use proxy connection URLs; and contact Litport support — directly from a coding agent or chat client.
The server cannot buy, renew, or cancel a package, or top up or move account balance. It can create and delete pay-per-GB proxies, which are live and billed per GB from the account balance as they are used. It can change a pay-per-GB proxy's label, on/off switch, pool, expiry, and traffic cap, and reissue the credentials of any proxy the account owns. A package's proxies can only be relabelled or have their credentials reissued; they end with their package. It can also change a token's location and rotation interval, request a new IP for a datacenter/ISP token, and add, remove, or set a package's allowed IPs.
Create an API key at litport.net/users/settings, then add the server to your MCP client's config with LITPORT_API_KEY in its env block.
The key is optional. Without one the server offers only the support tools and the three tools that need no account (explain_proxy_error, search_docs, get_doc).
claude mcp add litport -e LITPORT_API_KEY=lit_your_key_here -- npx -y @litportnet/litport-mcp
Or in .mcp.json:
{
"mcpServers": { "litport": { "command": "npx", "args": ["-y", "@litportnet/litport-mcp"], "env": { "LITPORT_API_KEY": "lit_your_key_here" } } } }
Add the same block to claude_desktop_config.json under mcpServers:
{
"mcpServers": { "litport": { "command": "npx", "args": ["-y", "@litportnet/litport-mcp"], "env": { "LITPORT_API_KEY": "lit_your_key_here" } } } }
Add the same block to .cursor/mcp.json, or use Cursor's Settings → MCP → Add new MCP Server with command npx -y @litportnet/litport-mcp and LITPORT_API_KEY in the environment variables field.
Proxy tokens carry a username/password pair. Putting every password from list_tokens into the model's context by default is unnecessary exposure for a browse operation, so the server ships two ways to reach a real password:
| Option | Behavior |
|---|---|
Default (LITPORT_MCP_REVEAL_CREDENTIALS unset) | list_tokens masks each token's password (null, with passwordSet: true), and adds a hint pointing at get_token_credentials or build_proxy_url. get_token_credentials and build_proxy_url always return the real password for the one token requested. |
LITPORT_MCP_REVEAL_CREDENTIALS=1 | list_tokens returns every password unmasked, alongside everything else. |
Either way, nothing is ever permanently unreachable — the default just keeps bulk listings out of the model's context until a specific token is named. create_token and reissue_credentials return the one proxy's username and password the same way get_token_credentials does, by design: the real values are in the result, whatever LITPORT_MCP_REVEAL_CREDENTIALS says. update_token and delete_token never return credentials, so a label, cap or on/off change does not put a password into the model's context.
| Tool | Calls the API? | Writes? | Description |
|---|---|---|---|
list_tokens | yes | List proxy tokens, paginated by cursor and an optional packageId filter; masks passwords by default. | |
get_token_credentials | yes | Get one token by id, including its real password. | |
get_token_usage | yes | Get bandwidth usage for a token, optionally by domain and/or hourly charges. | |
get_usage | yes | Get daily usage for many proxies at once over a date range, deleted proxies included, with the daily charge for pay-per-GB proxies. | |
get_token_location | yes | Get a token's current location/carrier target and whether it can change now. | |
list_location_options | yes | List the region/city (datacenter/ISP) or city/carrier (mobile) values a token can move to. | |
set_token_location | yes | yes | Change a token's location (and carrier, for mobile), or send random: true for another location the proxy can use right now. |
set_rotation | yes | yes | Change a token's rotation interval. |
get_new_ip | yes | yes | Get a new IP for a datacenter/ISP token. A static token uses its weekly allowance; a rotating one has a short wait between calls. Not safe to blindly retry on a static token. |
create_token | yes | yes | Create a live pay-per-GB proxy, optionally locked to a pool, with a label, your own externalRef, an expiry and a traffic cap. Returns its credentials. Send externalRef so a retry cannot create a second proxy. |
update_token | yes | yes | Change a pay-per-GB proxy's label, on/off switch, pool, expiry or traffic cap (a package's proxy takes a label only). Returns the proxy without its credentials. |
reissue_credentials | yes | yes | Issue a new username, password and change-IP key for a proxy. The old password stops and its open connections close. A requestId makes a retry safe. |
delete_token | yes | yes | Delete a pay-per-GB proxy. Its history and usage stay. Returns no credentials. |
list_packages | yes | List proxy packages: product, status, add-ons, limits, dates, and token IDs. | |
get_package | yes | Get one package by its public numeric ID. | |
get_allowed_ips | yes | Get a package's allowed-IP list and limit. | |
set_allowed_ips | yes | yes | Set a package's whole allowed-IP list at once. |
add_allowed_ip | yes | yes | Add one IP to a package's allowed-IP list. |
remove_allowed_ip | yes | yes | Remove one IP from a package's allowed-IP list. |
list_pools | yes | List pay-per-GB pools and the hubs each connects through. | |
list_targeting_options | yes | List available countries, regions, or cities for one or more pools. | |
get_balance | yes | Get the account's pay-per-GB balance and plan. | |
explain_proxy_error | no (local) | Look up an X-Proxy-Error-Code or SOCKS5 reply: what happened, whether to retry, what to do. | |
build_proxy_url | yes | Compose a ready-to-use proxy connection URL for a token, with pool/geo/session targeting or a passwordless allowed-IP endpoint. | |
search_docs | yes (public) | Search the Litport documentation index for pages matching a query. | |
get_doc | yes (public) | Fetch a Litport documentation page as markdown. | |
contact_support | yes (works without a key) | yes | Start a support conversation with a first message. |
get_support_replies | yes (works without a key) | Read a support conversation and its replies. | |
reply_to_support | yes (works without a key) | yes | Add a message to a support conversation. |
The read tools are annotated readOnlyHint: true, destructiveHint: false, idempotentHint: true. Every write tool documents in its own description whether it changes something and whether it is safe to repeat; get_new_ip, create_token and reissue_credentials are the exceptions (idempotentHint: false) — see below.
When the API refuses a call, the tool's error text holds the API's message, code, retryable, nextChangeAt and Retry-After (whichever it sent) and a docs link. retryable: true means the same call, sent again unchanged after the wait, can succeed and is safe to send; false means change something first, or, after an unclear failure of a call that is not safe to repeat, read the current state before deciding.
Three tools reach Litport support through the support API.
| Tool | Arguments | What it does |
|---|---|---|
contact_support | message, email | Starts a conversation with a first message. |
get_support_replies | conversationId, after | Reads the conversation. after is the highest message seq already received. |
reply_to_support | message, conversationId | Adds a message. |
Without `LITPORT_API_KEY` the conversation is a guest one. contact_support requires email (where we can reach you), and a guest conversation can answer general questions only. The access token that the API returns once stays in the server process for the session and is never shown to the model, so a guest conversation can be read only by the session that started it. Litport limits new guest conversations to 3 per hour and 10 per day per IP address.
With `LITPORT_API_KEY` the tools use your account's own conversation, where support can help with your orders and proxies. email is not used.
conversationId defaults to the conversation started or used most recently in the session. Replies are not pushed: get_support_replies returns pollAfterSeconds (30), so poll about that often. Messages are limited to 4,000 characters and 30 per conversation per 24 hours, and the API takes no attachments. Do not put API keys or proxy passwords in a message. You can also email mike@litport.net.
set_token_location sends only the keys you give it — region/city for a datacenter/ISP token, or city/carrier for a mobile token — so give exactly one of those two shapes. With those, it is safe to repeat: resending the already-saved target is a no-op. A standard US Shared Mobile token allows this once per 48 hours; on a 409 CHANGE_LIMIT the error carries nextChangeAt and a Retry-After header, both of which the tool surfaces, so the model knows when it can try again instead of retrying blindly.
random: true (sent alone, without region, city, carrier or country; the tool refuses the mix without calling the API) moves the token to another location it can use right now: a different city when there is one, and for a mobile token otherwise another carrier in the same city. It is saved as the target like any other change, and the same waits apply. It is not safe to repeat blindly: each repeat moves the proxy again wherever no wait applies, so after a lost result read get_token_location first. 409 LOCATION_UNAVAILABLE means no other location is available; nothing changed.
set_rotation changes a token's rotation interval to one of its own rotation.options values, and answers NOT_SUPPORTED when rotation.changeable is false (e.g. a Multi-location mobile token, whose interval always follows its current phone).
get_new_ip requests a new IP for a datacenter/ISP token. On a static token it spends the weekly allowance and is not safe to blindly retry: call get_token_location first and check canChangeNow/nextChangeAt, because a second call inside the same week fails with CHANGE_LIMIT rather than returning a second new IP. If a call's result is lost or ambiguous, re-read get_token_location instead of calling it again.
On a rotating token it works at any time. The new IP is always different from the current one, and the token's automatic timer restarts. Two calls must be at least the type's shortest rotation interval apart (the smallest value in the token's rotation.options); inside that wait the call fails with CHANGE_LIMIT, nextChangeAt and Retry-After. LOCATION_UNAVAILABLE means no other IP qualifies right now: nothing changed, and the call still uses up the wait. After a lost result, get_token_location cannot confirm the change (its canChangeNow/nextChangeAt are about the location, not this wait). Calling again after Retry-After is harmless and just gives another new IP; a CHANGE_LIMIT right after a lost re