Data Collection
war-tracker.com
Provides access to War-Tracker's classified conflict event data, including recent events, event details, tracked regions and countries, and map navigation.
ENDPOINT 1
https://war-tracker.com
MCP server metadata
- Name
- WebMCP
Known tools 5
wartracker_list_recent_eventsList recent classified conflict events from War-Tracker, ordered most-recent first.
Inferred read-onlywartracker_get_eventFetch the full machine-readable payload for a single War-Tracker event by id:
Inferred read-onlywartracker_list_regionsList the regions War-Tracker tracks. Each entry has a slug (use with the region
Inferred read-onlywartracker_list_countriesList the countries with the most War-Tracker events in the last 90 days.
Inferred read-onlywartracker_view_event_on_mapNavigate the human user's current War-Tracker tab to focus on a specific event
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.webmcp]
url = "https://war-tracker.com"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"webmcp": {
"type": "http",
"url": "https://war-tracker.com"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: webmcp
Remote MCP URL: https://war-tracker.com
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"webmcp": {
"url": "https://war-tracker.com"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"webmcp": {
"type": "http",
"url": "https://war-tracker.com"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "webmcp",
"transport": "streamable-http",
"url": "https://war-tracker.com"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.