Security & Testing
leak.town
Manages fake endpoints and captures requests for testing and security purposes.
ENDPOINT 1
https://leak.town/api/mcp
MCP server metadata
- Name
- leak.town
- Version
- 0.1.0
leak.town creates temporary HTTP/DNS/email capture towns for webhook debugging, DNS testing, payload inspection, and pen-testing. QUICK START: call create_town to get a token + url. Pass that token to every other tool. Tokens are the only auth — keep them out of logs. DEFAULT (core) toolset covers: town lifecycle, endpoint CRUD, request inspection, replay. Optional toolsets — call list_toolsets to see what's available, enable_toolset to turn one on: • dns — manage DNS records on the town's subdomain • storage — key-value storage scoped to a town • files — upload/manage static files served by an endpoint • share — read-only share links for showing a town to others • domains — custom domains (requires authToken, not a town token) • shell — remote shell sessions delivered into a captured request • remote_js — instrument a browser via injected JS (DOM, eval, network) • export_import — archive a town's config as a zip and re-import When a user asks about something a tool obviously matches, just call it. When unsure which toolset is relevant, list_toolsets first.
Known tools 36
claim_townClaim an anonymous (token-only) town for the authenticated user, associating it with their account so it shows up in list_towns.
Inferred read-onlyget_instance_configGet public instance configuration: vhosts, default town lifetime, body/email/file size limits, registration mode, and feature toggles.
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.leak-town]
url = "https://leak.town/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"leak-town": {
"type": "http",
"url": "https://leak.town/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: leak-town
Remote MCP URL: https://leak.town/api/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": {
"leak-town": {
"url": "https://leak.town/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"leak-town": {
"type": "http",
"url": "https://leak.town/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "leak-town",
"transport": "streamable-http",
"url": "https://leak.town/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
ENDPOINT 2
https://leak.town/api/mcp/full
MCP server metadata
- Name
- leak.town
- Version
- 0.1.0
leak.town creates temporary HTTP/DNS/email capture towns for webhook debugging, DNS testing, payload inspection, and pen-testing. QUICK START: call create_town to get a token + url. Pass that token to every other tool. Tokens are the only auth — keep them out of logs. DEFAULT (core) toolset covers: town lifecycle, endpoint CRUD, request inspection, replay. Optional toolsets — call list_toolsets to see what's available, enable_toolset to turn one on: • dns — manage DNS records on the town's subdomain • storage — key-value storage scoped to a town • files — upload/manage static files served by an endpoint • share — read-only share links for showing a town to others • domains — custom domains (requires authToken, not a town token) • shell — remote shell sessions delivered into a captured request • remote_js — instrument a browser via injected JS (DOM, eval, network) • export_import — archive a town's config as a zip and re-import When a user asks about something a tool obviously matches, just call it. When unsure which toolset is relevant, list_toolsets first.
Known tools 91
claim_townClaim an anonymous (token-only) town for the authenticated user, associating it with their account so it shows up in list_towns.
Inferred read-onlyexport_endpointExport a single endpoint as a zip archive (configuration + any associated static files).
Inferred read-onlyget_available_hostsAvailable town hosts for the calling user: built-in `system_hosts`, the user's own `user_hosts`, and `shared_hosts` granted by other domain owners.
Inferred read-onlyget_instance_configGet public instance configuration: vhosts, default town lifetime, body/email/file size limits, registration mode, and feature toggles.
Potential side effectsimport_endpointImport a single endpoint from a zip archive previously produced by export_endpoint (pass file_base64 with the base64-encoded zip bytes).
Inferred read-onlyimport_townImport a previously-exported town configuration bundle (endpoints, DNS records, settings).
Inferred read-onlylist_owned_domainsList the calling user's verified domains (under `domains`) and domains other users have shared with them (under `shared_domains`, each with the owner's username and avatar).
Inferred read-onlyremote_js_get_browser_storageGet browser storage (localStorage, sessionStorage, cookies) from a remote browser session.
Inferred read-onlyremote_js_set_browser_storageSet a browser storage value in a remote browser session.
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.leak-town]
url = "https://leak.town/api/mcp/full"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"leak-town": {
"type": "http",
"url": "https://leak.town/api/mcp/full"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: leak-town
Remote MCP URL: https://leak.town/api/mcp/full
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": {
"leak-town": {
"url": "https://leak.town/api/mcp/full"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"leak-town": {
"type": "http",
"url": "https://leak.town/api/mcp/full"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "leak-town",
"transport": "streamable-http",
"url": "https://leak.town/api/mcp/full"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for leak.town was fetched 2026-08-11T18:59:51.851Z and is being refreshed.
leak.town is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.