General Tools
zapboxapp.com
Provides general utilities including third-party API calls, currency exchange conversions, and cloud-based note creation and reading.
ENDPOINT 1
https://api.zapboxapp.com/mcp
MCP server metadata
- Name
- zapbox
- Version
- 1.0.0
Known tools 9
call_apiCall a third-party API using a credential stored in your Zapbox Agent Secrets vault.
Inferred read-onlyfx_convertConvert an amount between any two currency codes at the latest cached rate.
Inferred read-onlyfx_ratesUSD-based exchange-rate table covering 160+ currencies, refreshed daily and cached server-side.
Inferred read-onlynote_writeOverwrite a Zapbox cloud note's content (last write wins — there is no merge).
Potential side effectsseo_auditFetch a public URL and return a scored on-page SEO audit (title, meta, headings, Open Graph, canonical, robots, images, links).
Inferred read-onlytransfer_statusList the files, sizes and expiry behind a Zapbox /transfer short code.
Potential side effectsCONNECT 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.zapbox]
url = "https://api.zapboxapp.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"zapbox": {
"type": "http",
"url": "https://api.zapboxapp.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: zapbox
Remote MCP URL: https://api.zapboxapp.com/mcp
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": {
"zapbox": {
"url": "https://api.zapboxapp.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"zapbox": {
"type": "http",
"url": "https://api.zapboxapp.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "zapbox",
"transport": "streamable-http",
"url": "https://api.zapboxapp.com/mcp"
}
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.