Connect Claude to SecurityTrackr over MCP

4 min read · Documentation checked 2026-11-13

Use your SecurityTrackr account with MFA set up. MCP is available on every SecurityTrackr plan, including Free, within your organisation's limits. Your agent provider's access rules and charges apply separately.

Remote MCP server URL:

https://app.securitytrackr.com/api/mcp

Add a remote connector in Claude

Use Claude's remote custom connector settings. Availability and connector limits depend on your Claude plan and organisation policy.

  1. Open Customize → Connectors and add a custom connector named SecurityTrackr.
  2. Enter the server URL above and continue to the detected authentication settings.
  3. Choose Sign in now. For the OAuth client, prefer Claude's published identity (CIMD). Use Register automatically (DCR) only if your client does not support CIMD.
  4. Add the connector and complete SecurityTrackr sign-in and consent.
  5. Enable SecurityTrackr for the conversation through the chat's connectors menu.

For Team or Enterprise, an authorised organisation administrator first adds the Web custom connector under Organization settings → Connectors. Members then connect individually from their own connector settings.

Source: Claude's remote custom connector guide.

Approve access in SecurityTrackr

Complete sign-in in the browser and review the requested permissions. For a first read-only check, keep observations.read and remove permissions you do not need. Choose one-time access for 15 minutes, or a persistent connection when offered. Longer access and sensitive permissions require fresh MFA verification.

MCP uses OAuth. Prefer Client ID Metadata Documents (CIMD) when your client supports them. SecurityTrackr retains Dynamic Client Registration (DCR) for compatibility with clients that do not. Both require your consent before accessing the register. A SecurityTrackr REST API token is not a substitute.

Check the connection

Enable the connection in your agent and ask for an overview of your register:

Use SecurityTrackr to summarise the top 5 unhandled risks in our register. Include their observation identifiers and explain their priority. Do not change any records.

Check that the agent actually called SecurityTrackr and that its answer matches records you can open. An empty result can be valid. Confirm the connection under Account → Connected agents, where you can also disconnect it.

If the connection fails

Check the server URL, finish the browser sign-in and MFA prompts, and confirm that the connection is enabled in the conversation. A permission error can mean your role or approved scopes do not allow that action. Reconnect when access expires; refresh the client's tool list if it still shows old tools.

This setup is based on the linked provider documentation. It is not an end-to-end certification of every client version or workspace configuration.

Read the shared MCP guide for permissions, duplicate review, background AI jobs and revocation.