ArmorCodex

ArmorCodex lets you read, update, and review the policies that govern how AI coding agents interact with tools, files, and infrastructure. Set rules in natural language ("deny webfetch", "require approval for production database changes"), check current policy state, and register intent plans before tool calls run. Built by ArmorIQ for teams that need governance and audit on AI agent activity.

View in the ChatGPT registry

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Security
Primary Subcategory: Security & Compliance Posture Automation (GRC)
Secondary Subcategories: None listed
Brand: ArmorIQ
Access: No account required
First tracked: 2026-06-30
Tool count: 3
Geography: US

ChatGPT Plugin Discoverability Score

ChatGPT organic discovery is not live yet

ArmorCodex is tracked in the ChatGPT Plugin registry. Public organic-discovery measurement is not live for ChatGPT yet, so there is no score to publish today.

Get notified when your score goes live

Enter your work email and we’ll notify you when ChatGPT Plugin organic discovery scoring launches.

No spam. Unsubscribe any time.

Talk to our team

Primary Subcategory

Competing in ChatGPT Security & Compliance Posture Automation (GRC)

View Category

Listed in alphabetical order

Primary Subcategory

ArmorCodexOrganic discovery is pendingGet the score at launch

BastionOrganic discovery is pendingGet the score at launch

DigiTrust Evidence AssistantOrganic discovery is pendingGet the score at launch

LASECOrganic discovery is pendingGet the score at launch

SprintoOrganic discovery is pendingGet the score at launch

VantaOrganic discovery is pendingGet the score at launch

Score explained

How the Discoverability Score works

Organic discovery scoring for ArmorCodex on ChatGPT is not live yet. The score will use measured agent conversations when it launches.

InvisibleBuriedEmergingCompetitiveWinning

Organic discovery scoring is pending. Your Plugin score will appear on this scale when measurement goes live.

FoundDiagnostic

Whether Claude found your Plugin in connector search. It must be Found before it can reach the picker, but the score counts picker appearances—not search results.

PickedMain score

How often your Plugin appeared in the picker, or Claude invoked it directly, across contested conversations. This percentage is the Discoverability Score; the headline number is rounded.

PositionedDiagnostic

What position your Plugin appeared in when it was shown in the picker. This shows prominence, but it does not affect the score.

Read the full scoring methodology Recommended guideHow to get your Claude Connector organically discoveredFollow the practical steps agents use to find, shortlist, and choose your Connector.

Tools

3 tools agents can invoke

Returns the current ArmorCodex policy rule set held in this server's in-memory store. With no arguments, returns the full policy object including all rules and the current version. With an `id` argument, returns the single rule matching that id. Annotations: readOnlyHint=true because the tool only reads server state without modifying anything; destructiveHint=false because no state changes; idempotentHint=true because repeated calls with the same input return the same result without side effects; openWorldHint=false because all reads come from this MCP server's memory and no external system is contacted.
policy_read
Updates the ArmorCodex policy rule set held in this server's in-memory store. Supports two modes: `merge` (default) upserts the submitted rules into the existing set, and `replace` overwrites the entire rule set with the submitted payload. The previous rules are not snapshotted, so `replace` cannot be undone from this tool. Annotations: readOnlyHint=false because the tool mutates server state; destructiveHint=true because replace mode irreversibly drops the prior rule set; openWorldHint=false because all state lives in this MCP server's memory and no external system is contacted.
policy_update
Records a structured intent plan (goal plus an ordered list of steps describing the tools the agent intends to call) into this server's in-memory plan list and returns the generated plan id. This hosted server stores the plan only; it does not enforce or block subsequent tool calls. The companion local Codex plugin uses these plans to gate tool execution via PreToolUse hooks on the user's machine, but that enforcement is out of scope for this hosted MCP. Annotations: readOnlyHint=false because the tool appends a new record to the in-memory plan list; destructiveHint=false because each call appends a new plan and never modifies or deletes prior plans; idempotentHint=false because calling the tool twice with identical inputs produces two distinct plan ids and two records; openWorldHint=false because all state lives in this MCP server's memory and no external system is contacted.
register_intent_plan

ArmorCodex FAQ

How do I improve a ChatGPT Plugin's discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are ArmorCodex alternatives on ChatGPT?

As of 2026-08-14, ArmorCodex competes with Bastion, DigiTrust Evidence Assistant, LASEC, Sprinto, Vanta in ChatGPT Security & Compliance Posture Automation (GRC), ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.