Overview
This article explains how Netskope counts AI Assets for billing purposes under the AI Command Center (AICC) subscription. AI Assets include AI Applications, MCP Servers, and AI Identities.
Definitions
AI Application – An AI Application is any web application identified as belonging to the Generative AI, Coding AI, or any other AI category by the Netskope App Catalog.
MCP Server – An MCP Server is any software application, service, or endpoint that communicates or processes data using the Model Context Protocol (MCP) over HTTP.
AI Identity – An AI Identity is any user account or credentials used to access an AI Application or MCP Server. AI Identities include any of the following:
- Corporate login credentials
- Personal accounts
- API tokens
Counting Methodology
AI Applications
Each entry in the Netskope App Catalog counts as one AI Asset, regardless of how many users or devices access it. If an AI Application is blocked for all users then it will not be counted as an AI Asset.
| Example | Count |
|---|---|
| ChatGPT.com accessed by 2,000 users on 2,000 devices | 1 AI Asset |
| ChatGPT.com and chatgptbrasil.com.br both in use | 2 AI Assets |
The second example counts as 2 AI Assets because ChatGPT.com and chatgptbrasil.com.br are listed as separate applications in the Netskope App Catalog.
MCP Servers
MCP Server counting is based on the Fully Qualified Domain Name (FQDN). Each unique FQDN counts as one AI Asset. If a MCP Server is blocked for all users then it will not be counted as an AI Asset.
Example 1: Multiple MCP Servers on an Internal Network
An organization runs the following MCP servers on its internal network:
| FQDN | Count |
|---|---|
| mcp.prod.internal.netskope.com | 1 AI Asset |
| mcp.dev.internal.netskope.com | 1 AI Asset |
| mcp-backup.prod.internal.netskope.com | 1 AI Asset |
| Total | 3 AI Assets |
Each distinct FQDN counts as one AI Asset.
Example 2: Publicly Hosted MCP Servers, for example, Zapier.
The following URLs all share a single FQDN (actions.zapier.com):
https://actions.zapier.com/mcp/github https://actions.zapier.com/mcp/slack https://actions.zapier.com/mcp/<user_or_app_key>/sse
Counted as: 1 AI Asset. All paths under actions.zapier.com resolve to a single FQDN.
Example 3: Claude (Anthropic)
The following URLs have different subdomains and appear as separate rows on the MCP Server page:
https://microsoft365.mcp.claude.com/mcp https://pubmed.mcp.claude.com/mcp
Counted as: 2 AI Assets. Each subdomain appears as a distinct entry in the MCP Server page.
AI Identities
Each unique account or credential used to access an AI Application or MCP Server counts as one AI Asset. Multiple identities belonging to the same employee each count separately.
Example: John Doe is a single employee with the following identities:
| Identity | Type | Counted |
|---|---|---|
| jdoe@netskope.com | Corporate SSO | Yes |
| john@gmail.com | Personal Google Workspace | Yes |
| johndoe@gmail.com | Client-specific Gmail | Yes |
| doe_test_user | Test account, no usage | No |
| api_key_prod_456 | Service API key | Yes |