REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Live ocean container and shipment tracking with ETAs, holds, fees, and last free days.
Pick the AI app you use, then copy the settings.
Passed 5/5 checks · What you ask goes through the maker’s server (mcp.terminal49.com)
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 2 min
No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
CustomizeConnectors
Copy each value into the field with the same name in Claude, then click Continue
Terminal49https://mcp.terminal49.comLeave Authentication as Claude detected it, then click Add
+ConnectorsTerminal49
Use Terminal49 and tell me what you can do for me, then show me one thing✓ If Claude says it is using Terminal49 or shows a Terminal49 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 ChatGPT on business plans only
ChatGPT Business, Enterprise or Edu on the web, added by a workspace admin or owner · On Free, Plus or Pro: your ChatGPT plan cannot connect MCP yet
Plugins+Add custom MCP server
Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin
Terminal49https://mcp.terminal49.comStart a new chat and pick Terminal49 from your plugins before typing
Use Terminal49 and tell me what you can do for me, then show me one thing✓ If ChatGPT says it is using Terminal49 or shows a Terminal49 tool in the answer, you are connected
Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Claude Code · about 2 min
No key, nothing to install
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --transport http --scope user terminal49 https://mcp.terminal49.comYou should see Terminal49 listed as connected
Use Terminal49 and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Terminal49 or shows a Terminal49 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 · about 2 min
No key, nothing to install
Use Terminal49 and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Terminal49 or shows a Terminal49 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 · about 2 min
No key, nothing to install
Use Terminal49 and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Terminal49 or shows a Terminal49 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.
Address for apps that connect over the web
https://mcp.terminal49.comJSON settings are under “For developers” below
Claude Code
claude mcp add --transport http --scope user terminal49 https://mcp.terminal49.comCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"terminal49": {
"url": "https://mcp.terminal49.com"
}
}
}VS Code (mcp.json)
{
"servers": {
"terminal49": {
"type": "http",
"url": "https://mcp.terminal49.com"
}
}
}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.
Connect over the internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
The server asks you to sign in before it lists its tools.
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 12, 2026
The registry name was verified with the GitHub account Terminal49, which owns the repo
Code last changed 3 days ago
Uses MIT
Responded in 133 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
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 5 of 5 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 in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed 3 days ago, and the latest version (1.1.0) reached the registry 12 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT Business and above.
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
A powerful toolkit for coding, providing semantic retrieval and editing capabilities.
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.
Vercel-native Model Context Protocol server for Terminal49's API, built with TypeScript and the official MCP SDK.
@terminal49/mcp is a private workspace in this repository. Connect a client to the hosted server at https://mcp.terminal49.com (Streamable HTTP). OAuth 2.1 needs no API key: the client discovers https://auth.terminal49.com and opens a browser sign-in. Clients that can't run that flow send Authorization: Token YOUR_API_KEY. Use the Token scheme for API keys. The Bearer scheme is used for OAuth access tokens. A local stdio process reads T49_API_TOKEN instead. Build steps are in Local Development.
T49_API_TOKEN=your_token_herehttps://your-deployment.vercel.app/api/mcp| Tool | Description | Key Features |
|---|---|---|
| `search_container` | Search by container#, BL, booking, or reference | Fast fuzzy search |
| `track_container` | Create tracking request and get container data | SCAC autocomplete ✨ |
| `identify_tracking_number` | Predict a number's type and carrier and check whether it is already tracked | Creates nothing |
| `get_container` | Get detailed container info with flexible data loading | Optional custom fields and party roles |
| `get_shipment_details` | Get shipment routing, BOL, containers, ports | Optional custom fields and party roles |
| `get_container_transport_events` | Get full event timeline for a container | Milestone history |
| `get_supported_shipping_lines` | List 40+ major carriers with SCAC codes | Filterable by name/code |
| `get_container_route` | Get ports in route order with ETAs and the current vessel | Premium feature |
| `get_location` | Get a port, terminal, or metro area | FIRMS code, address, time zone |
| `get_vessel` | Get a vessel's position and, optionally, its projected track to a port | Projection is a premium feature |
| `list_shipments` | List shipments with filters and pagination | Fleet-level visibility |
| `list_containers` | List containers with filters and pagination | Returns ResourceLinks ✨ |
| `summarize_containers` | Count containers grouped by terminal, status, carrier, port, hold, or date | Same filters as list_containers |
| `list_parties` | Find parties by company name, or read one by ID | Feeds advanced_filters.customer_id and advanced_filters.parties |
| `list_custom_field_definitions` | List the account's custom fields, their types, and enum options | Needs a signed-in user |
| `list_tracking_requests` | List tracking requests and statuses | Audit and monitoring |
| `get_tracking_request` | Get one tracking request's status, failure reason, and shipment | Follow-up after tracking |
| `list_documents` | Find documents by file name, reference, or type | Never returns extracted data or file links |
| `get_document` | Get one document, with opt-in extracted data, source email, and download link | Untrusted content is labeled |
| `search_docs` | Search the public Terminal49 documentation | Returns links to cite |
| `whoami` | Identify the credential, its account, the features it can use, and the session's toolsets | Explains empty or unauthorized results |
| `set_party_role` | Attach, replace, or detach a party (such as the drayage carrier) on containers or shipments | Destructive write, only on request |
| `set_custom_field` | Set or clear one of the account's custom fields on containers or shipments | Destructive write, only on request |
| `search_importers` | Find US importers by name, by what they import, or both | Trade intelligence, per account |
| `get_importer_profile` | One importer's totals, monthly series, ports, origins, carriers, and products | Trade intelligence, per account |
| `search_commodities` | Turn a product description or HS prefix into four-digit HS codes | Trade intelligence, per account |
| `rank_importers` | Rank importers by containers for a product, US port, or origin country | Trade intelligence, per account |
| `get_trade_trends` | Time series of containers, TEUs, or estimated value | Trade intelligence, per account |
| `get_trade_breakdown` | Nested totals over one to three dimensions | Trade intelligence, per account |
| `get_trade_data_coverage` | Where trade data starts, the latest and last full month | Trade intelligence, per account |
| Prompt | Description | Use Case |
|---|---|---|
| `track-shipment` | Track container with optional carrier | Quick tracking start (SCAC autocomplete ✨) |
| `check-demurrage` | Analyze demurrage/detention risk | LFD calculations |
| `analyze-delays` | Identify delays and root causes | Timeline analysis |
The track-shipment prompt's carrier argument supports MCP completions (completion/complete): suggestions are sourced live from get_supported_shipping_lines, filtered by what the user has typed, and returned as SCAC codes.
list_containers ResourceLinks)The server advertises MCP instructions (a server-level operating guide) at initialize time: it explains the ocean container/shipment tracking domain, key vocabulary (SCAC, BOL/booking, POL/POD, LFD, demurrage, holds), the read tools vs the single write tool (track_container), and the canonical tool-chaining order.
list_containers returns MCP resource_link content blocks — one per container row — that point at the registered terminal49://container/{id} resource. Clients can render the compact list and resolve full per-container detail on demand via resources/read, instead of paying for every container's full payload up front.
Tool results separate the human-readable answer from agent-steering metadata. The steering block (presentation guidance + suggested follow-up tools, derived from the _response_contract) is tagged with annotations: { audience: ['assistant'] } so spec-aware clients can hide it from end users, while the answer block stays user-visible.
registerTool(), registerPrompt(), registerResource() patternsPOST /api/mcp - stateless, JSON responses@sentry/node ^10.55.0SENTRY_DSN is settrack-shipment: Quick container tracking with optional carriercheck-demurrage: Demurrage/detention risk analysisanalyze-delays: Journey delay identification and root causecompletion/complete on the track-shipment prompt's carrier arg, sourced from get_supported_shipping_lineslist_containers rows link to the terminal49://container/{id} resourceaudience: ['assistant']terminal49://shipment/{id} resource template (only the container template is currently registered)./api/mcp.ts # Vercel serverless function (HTTP)
/packages/mcp/ ├── src/ │ ├── server.ts # MCP server (stdio) │ ├── index.ts # Stdio entry point │ ├── tools/ # MCP tools │ └── resources/ # MCP resources └── package.json
The MCP server depends on the workspace package @terminal49/sdk. Build that package before you build packages/mcp.
Transport:
/api/mcp (for hosted use)node packages/mcp/dist/index.js after the build in Local Development)The public connector URL is https://mcp.terminal49.com. Store assets and submission metadata are checked in at the repository root:
chatgpt-app-submission.json — locked ChatGPT listing copy and review casesclaude-connector-submission.json — values to enter in Claude's submission portalserver.json — official MCP Registry metadata used for Copilot discoverypublic/store-icons/terminal49-{light,dark}.png — 512×512 brand iconsCline and other clients that read a marketplace install guide from the server subfolder use packages/mcp/llms-install.md.
OpenAI generates a unique domain-verification token during submission. Add that exact value to the existing MCP Vercel project:
vercel env add OPENAI_APPS_CHALLENGE
After the project redeploys, verify that the well-known endpoint returns only the token you pasted:
curl --fail --silent \
https://mcp.terminal49.com/.well-known/openai-apps-challenge
Do not commit the token. The endpoint returns an empty 404 response while OPENAI_APPS_CHALLENGE is unset. Submit the connector and the values in chatgpt-app-submission.json through the OpenAI plugin submission flow.
Use the Claude Connectors Directory portal and enter the values in claude-connector-submission.json. Upload the light icon from public/store-icons/terminal49-light.png; the dark variant is available for clients that support theme-specific assets.
GitHub's Copilot registry is a curated downstream discovery surface. The root server.json is the official MCP Registry entry (io.github.Terminal49/terminal49).
.github/workflows/publish-mcp.yml publishes that file to https://registry.modelcontextprotocol.io. It runs when a push to main changes server.json, and a maintainer can start it with workflow_dispatch on main. The job authenticates with GitHub OIDC (mcp-publisher login github-oidc) and then runs mcp-publisher publish. The io.github.Terminal49 namespace is authorized for OIDC from this organization repository, so the workflow needs no registry secret.
Bump version in server.json for each metadata change. The registry keeps published versions, and a second publish of the same version is rejected.