Sycek MCP Server

The **Sycek MCP Client** is a [Model Context Protocol](https://modelcontextprotocol.io) server that gives AI assistants direct access to the Sycek

Remote serverstreamable-httpPython

What is the Sycek MCP MCP server?

The Sycek MCP Client is a Model Context Protocol server that gives AI assistants direct access to the Sycek OSINT platform's 20 intelligence tools. Instead of switching between dashboards, you. Exposed over MCP by the sycek mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

Its toolset

Everything the assistant can do here goes through one of these:

  • BreachINT — Expose credential exposure, infrastructure ownership, and identity linkage across breach databases, stealer logs, and WHOIS records

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration

You will need 2 environment variables: SYCEK_API_KEY, SYCEK_API_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Sycek MCP's toolset — BreachINT — is a fair guide to whether it matches your workflow. It is maintained by sycekosint; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the sycek mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
BreachINTExpose credential exposure, infrastructure ownership, and identity linkage across breach databases, stealer logs, and WHOIS records.

How to install the Sycek MCP MCP server

{
  "mcpServers": {
    "sycek": {
      "command": "uvx",
      "args": ["sycek-osint-mcp"],
      "env": {
        "SYCEK_API_KEY": "your-value",
        "SYCEK_API_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
SYCEK_API_KEYCredential the server authenticates with.Yes
SYCEK_API_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Sycek MCP to BreachINT.

Frequently asked questions

It connects Sycek MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (BreachINT) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Sycek MCP directly.