Skip to main content

Armor1

Overview

Visualize MCP (Model Context Protocol) server security risks and developer usage patterns across your organization. Monitor configured MCP servers for supply chain vulnerabilities, risky tool exposure, and insecure authentication modes. Track which developers are using which MCP servers and correlate risk posture with user activity.

Configurations

ConfigurationDescription
Blueprint Account NameA human-readable name for your account that will be used to identify this account across the application.
Armor1 Base URLThe Armor1 API base URL (e.g. https://stage-api.armor1.ai/). Found in your Armor1 tenant settings.
Armor1 Client IDThe client uaddress used to authenticate with the Armor1 API (e.g. mykey@client.armor1). Generated in your Armor1 tenant under Settings > API Keys.
Armor1 Client SecretThe client secret associated with the Client ID. Treat this as a password — store it securely.
Data Crawl FrequencyThe frequency at which Kscope will connect to Armor1 and collect updated MCP security data.

Permissions

The Armor1 blueprint requires a Client credential pair with the following scopes assigned in Armor1:

ScopeWhy it's needed
read:tenantAccess tenant metadata and configuration
read:tenant_usersList platform users within the tenant
read:tenant_clientsList API clients (uaddress identities) registered in the tenant
read:mcp_serversRead MCP server catalog entries and their risk analysis
read:mcp_usersAccess developer user profiles and MCP usage data
read:mcp_clientsRead MCP client catalog data to correlate servers with users
read:groupsRead user groups used for policy and access management
read:policiesRead policy instances governing MCP server and user access
read:skillsRead AI skill catalog entries and their risk assessments

Important Notes:

  • Create a dedicated API client in Armor1 for Kscope — avoid using personal credentials
  • The client only requires read-level access — no write operations are performed
  • Credentials are scoped to a single tenant; configure one blueprint per tenant

For more information about Armor1 API authentication, refer to the Armor1 API Documentation.

Schema Model

ResourceSource EntityNormalized EntityDescription
Armor1 Tenantarmor1.tenant.TenantTenantThe root Armor1 tenant node
Tenant Userarmor1.tenant.TenantUserTenantUserA platform user within the Armor1 tenant
Tenant Clientarmor1.tenant.TenantClientTenantClientAn API client (uaddress identity) registered in the tenant
MCP Server Catalogarmor1.mcpserver.MCPServerCatalogMCPServerCatalogA configured MCP server with risk analysis and tool definitions
MCP Server Risk Analysisarmor1.mcpserver.MCPServerRiskAnalysisMCPServerRiskAnalysisComputed risk score and status for an MCP server
MCP Toolarmor1.mcpserver.MCPToolMCPToolA tool exposed by an MCP server
MDM Device Userarmor1.mdm.MDMUserMDMUserA developer using MCP clients on a managed device
Platform Userarmor1.user.UserUserAn Armor1 platform user with roles and permission scopes
MCP Client Catalogarmor1.mcpclient.MCPClientCatalogMCPClientCatalogA registered MCP client application within the tenant
Grouparmor1.group.GroupGroupA user group used for policy and access management
Policy Instancearmor1.policy.PolicyInstancePolicyInstanceAn applied policy governing MCP server or user access
Shadow Server Catalogarmor1.shadowserver.ShadowServerCatalogShadowServerCatalogAn unauthorized or unmanaged MCP server discovered on a managed device
Skill Catalogarmor1.skill.SkillCatalogSkillCatalogA registered AI skill (agent capability) within the tenant
Skill Risk Assessmentarmor1.skill.SkillRiskAssessmentSkillRiskAssessmentComputed risk score and status for an AI skill
Risk Assessmentarmor1.risk.RiskAssessmentRiskAssessmentOverall risk posture snapshot for an MDM device user
Risk Assessment Recordarmor1.risk.RiskAssessmentRecordRiskAssessmentRecordA per-metric evaluation within a risk assessment
Risk Metricarmor1.risk.RiskMetricRiskMetricA shared metric definition used to score risk assessments

Security Insights

The Armor1 blueprint feeds data into the following analyzers:

AnalyzerWhat it detects
AI SecurityMCP server supply chain risks, risky tool exposure, insecure auth modes, and developer risk posture
ApplicationApplication-level risk scoring incorporating MCP server risk data

Insight Models

Model IDAlertDescription
SB-Armor1-HighRiskServersHigh-Risk MCP Servers DetectedMCP server catalogs with RiskLevel = danger
SB-Armor1-ShadowServersShadow MCP Servers DetectedShadow servers with no matching curated catalog entry
SB-Armor1-ExpiredServerTrustMCP Server Trust ExpiredCurated servers with Officiality = expired
SB-Armor1-HighRiskClientsHigh-Risk MCP Clients DetectedMCP client catalogs with RiskLevel = danger
SB-Armor1-RiskPostureChangeMCP Risk Posture DegradedServers or clients with warning or danger risk level
SB-Armor1-OpenRemediationActionsOpen MCP Remediation ActionsRisk assessment records in failure or warning status
SB-Armor1-DevicesWithoutOwnerUnowned MDM DevicesMDM device users with no linked platform identity
SB-Armor1-HighRiskSkillsHigh-Risk AI SkillsSkill catalog entries with warning or danger risk level
SB-Armor1-UsersExposedHighRiskServersUsers Exposed to High-Risk MCP ServersPlatform users whose devices connect to high-risk or shadow servers
SB-Armor1-UsersExposedHighRiskClientsUsers Exposed to High-Risk MCP ClientsPlatform users whose devices have high-risk remediation assessments

Correlations

Internal (within Armor1)

FromRelationshipToDescription
TenantTenantHasUserTenantUserPlatform users belonging to this tenant
TenantTenantHasClientTenantClientAPI clients (uaddress identities) registered in the tenant
TenantTenantHasMCPServerMCPServerCatalogMCP servers owned by this tenant
TenantTenantHasMCPClientMCPClientCatalogMCP client catalogs configured in this tenant
TenantTenantHasMDMUserMDMUserMDM device users within this tenant
TenantTenantHasGroupGroupUser groups scoped to this tenant
TenantTenantHasPolicyPolicyInstancePolicy instances governing this tenant
TenantTenantHasRiskAssessmentRiskAssessmentRisk assessments belonging to this tenant
TenantTenantOwnsSkillSkillCatalogAI skills owned by this tenant
MDMUserMDMUserHasPlatformIdentityUserResolves device-bound identity to platform user
MDMUserMDMUserRunsClientMCPClientCatalogAI clients active on a managed device
MDMUserMDMUserConnectsToServerMCPServerCatalogCurated servers each device reaches
MDMUserMDMUserCurrentRiskAssessmentRiskAssessmentCurrent overall risk assessment for a device user
MCPServerCatalogServerHasCurrentRiskAnalysisMCPServerRiskAnalysisServer linked to its latest risk analysis
MCPClientCatalogClientCatalogLoadsServerMCPServerCatalogServers each client class loads across the tenant
ShadowServerCatalogShadowServerResolvesToCuratedMCPServerCatalogUnresolved shadow server matched to catalog entry
ShadowServerCatalogShadowServerDiscoveredOnMDMUserDevice where the shadow server was observed
GroupGroupHasMemberMDMUserMDM device users who are members of this group
GroupGroupHasPolicyPolicyInstancePolicy instances assigned to this group
RiskAssessmentRiskAssessmentContainsRecordRiskAssessmentRecordAssessment to its per-metric evaluations
RiskAssessmentRecordRiskRecordEvaluatedByMetricRiskMetricRecord linked to its shared metric definition
SkillCatalogSkillHasCurrentRiskAssessmentSkillRiskAssessmentSkill to its most recent risk assessment
UserUserHasRoleRolePermission bundles assigned to each platform user
RoleRoleGrantsScopeScopePermission atoms within each role

Cross-Blueprint (enterprise blast radius)

FromRelationshipToDescription
armor1.mdm.MDMUserkorweave.UserSharedIdentityaws.iam.UserMCP exposure → cloud IAM (matches Email → IAM UserName)
armor1.mdm.MDMUserkorweave.UserSharedIdentitygithub.organization.UserMCP risk → repository access (email federation)
armor1.mdm.MDMUserkorweave.UserSharedIdentityjira.account.UserExposed MDM identity → Jira projects and issues
armor1.mdm.MDMUserkorweave.DeviceOwnerHasIAMAccessaws.iam.UserDevice user → cloud IAM (when UserID matches IAM UserName)
armor1.mcpserver.MCPServerCatalogarmor1.ServerCatalogHasNpmPackagenpm.package.PackageSupply chain risk traversal via npm package
armor1.mcpserver.MCPServerCatalogarmor1.ServerCatalogHasSourceRepogithub.repository.RepositoryHIGH risk server → source repo write access