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/mcpAdd an HTTP server in VS Code
Open a local project in VS Code with Copilot enabled. These steps cover GitHub Copilot in the editor. For a workplace agent, use the Copilot Studio and Microsoft 365 guide.
- Select Copilot as the session target. Run MCP: Add Server from the Command Palette.
- Choose HTTP and enter the server URL above. Give it the ID securitytrackr.
- Choose a personal configuration destination. Current Copilot sessions offer Global → Copilot Global; available destinations depend on your VS Code version and session configuration.
- Review the server trust prompt, then complete browser authentication when requested. Use Authenticate in the server actions if offered.
- Enable the SecurityTrackr tools for your Copilot conversation and run the read-only check below.
Source: VS Code's MCP setup guide. If your organisation disables custom MCP servers, ask its administrator about access.
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.