# Connect nebty to Claude

> Add the nebty MCP server to Claude as a custom connector and sign in with your nebty account.

With the nebty MCP server, an AI assistant such as Claude can read your nebty data and, when you ask it to, act on it. You can ask questions like “Which new high-risk domains does my brand have?” in plain language, and the assistant looks up the answer in nebty.

- **Server URL:** `https://mcp.nebty-id.com/mcp`
- **Sign-in:** with your nebty account (OAuth). You do not need an API key. For your own scripts, use the [nebty API](https://docs.nebty-id.com/api/access/) instead.
- **Access:** the assistant sees the same brands and data as your nebty user, no more.

nebty is not listed in Claude’s connector directory yet. You add it as a **custom connector**.

## Before you start

- A nebty account with access to at least one brand.
- A Claude plan with custom connectors: Free, Pro, Max, Team or Enterprise. On the Free plan you can add one custom connector.
- On a Team or Enterprise plan, an Owner adds the connector for the organization first (see below).

## Add the connector (Pro and Max)

1. In Claude, go to **Customize > Connectors**.
2. Select **+ Add**, then **Add custom connector**.
3. Enter a name, for example `nebty`.
4. Enter the server URL `https://mcp.nebty-id.com/mcp` and select **Continue**.
5. Keep the authentication settings that Claude detects. Select **Continue**, then **Add**.
6. Select **Connect**. Claude opens the nebty sign-in page. Sign in with your nebty account.
7. nebty shows which access Claude asks for. Check it and select **Allow access**.

The connector is now ready. In a conversation, you can turn it on or off with the **+** button, then **Connectors**.

If the sign-in does not work, remove the connector and add it again. This time, under **OAuth client**, choose **Register automatically**. nebty supports this kind of client registration.

## Add the connector (Team and Enterprise)

An Owner or Primary Owner adds the connector once for the organization:

1. Go to **Organization settings > Connectors** and select **Add**.
2. Hover over **Custom** and select **Web**.
3. Enter the name `nebty` and the server URL `https://mcp.nebty-id.com/mcp`, then select **Continue**.
4. Keep the detected authentication settings and select **Add**.

Each member then connects with their own nebty account: **Customize > Connectors**, find nebty, select **Connect** and sign in. Every member sees only their own nebty brands.

## What you allow

When you select **Allow access**, nebty lists the requested access:

- Read website data
- Submit a new website for inspection
- Access the Nebty API via the MCP server

With this access, the assistant can use every tool of the nebty connector, for the brands your nebty user can see. Some tools have effects outside nebty, for example requesting a takedown or sending a takedown report by email. [What your assistant can do](https://docs.nebty-id.com/mcp/tools/) lists every tool and what it changes.

Claude asks for your approval before it uses a tool, unless you allowed that tool before. Read these requests, and do not choose **Allow always** for tools that request takedowns or send emails.

## Disconnect

To remove the connector, go to **Customize > Connectors** (Team and Enterprise Owners: **Organization settings > Connectors**), open the menu next to nebty and select **Remove**. To have nebty revoke the access on its side as well, contact nebty.

## Other MCP clients

Any MCP client that supports remote servers with OAuth can connect:

| Setting | Value |
| - | - |
| Server URL | `https://mcp.nebty-id.com/mcp` (Streamable HTTP) |
| Authorization | OAuth 2.1 with authorization code and PKCE (`S256`) |
| Discovery | `https://mcp.nebty-id.com/.well-known/oauth-protected-resource` |
| Client sign-up | Dynamic client registration at `https://app.nebty.de/o/register/` |
| Scopes | `nebty-mcp`, `nebty-core:read`, `nebty-core:write` |

The server does not accept API keys; for access with a key, use the [nebty API](https://docs.nebty-id.com/api/access/). Read tools need `nebty-core:read`, tools that change something need `nebty-core:write`. The old endpoint `/sse` is switched off and answers `410 Gone`; use `/mcp`.