getDeviceExposure — OT Intel API MCP Tool
getDeviceExposure
(get device exposure) is one of 40 tools on the
OT Intel API
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call getDeviceExposure from your client
- Claude Code OT Intel API getDeviceExposure run in your project directory
- Claude Desktop OT Intel API getDeviceExposure ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor OT Intel API getDeviceExposure ~/.cursor/mcp.json
- VS Code OT Intel API getDeviceExposure .vscode/mcp.json
- Zed OT Intel API getDeviceExposure ~/.config/zed/settings.json
- Windsurf OT Intel API getDeviceExposure ~/.codeium/windsurf/mcp_config.json
- Cline OT Intel API getDeviceExposure ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI OT Intel API getDeviceExposure ~/.gemini/settings.json
- Grok OT Intel API getDeviceExposure .mcp.json (in your project root)
- ChatGPT OT Intel API getDeviceExposure Settings → Connectors → Advanced → Developer mode
- Claude.ai OT Intel API getDeviceExposure Settings → Connectors → Add custom connector
- LangChain OT Intel API getDeviceExposure pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http ot-intel-api https://ot-intel-api.onrender.com/mcpOther tools on this server
- getCveTriage
- getThreatActor
- getActorsBySector
- getIocEnrichment
- getAdvisories
- getPatchFeasibility
- getAssetExposure
- getCampaigns
- getSectorDelta
- getMalwareProfile
- getSectorBrief
- getAsnProfile
- getDetectionArtifacts
- getComplianceMapping
- getComplianceBatch
- getThreatScore
- getPrecursorTtp
- getRootCauseLocalization
- getThreatHuntControlLoop
- getInvariantReachability
- getVendorRisk
- getRiskExposure
- getActionConformance
- getAiExposure
- getAiUplift
- getAiAttackFeasibility
- getClaimReliability
- getStixCoverage
- getMitigationMap
- getActorReport
- getActorDossier
- getSectorSitrep
- getCtiArticle
- getLinkedinPost
- getXThread
- getAnalystBrief
- getVendorRiskDelta
- submitSighting
- getGccBulletin
This list was read from the server itself, by connecting to it and calling tools/list on 20 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.