Arcjet

ChatGPT handles the OAuth flow automatically.

claude mcp add arcjet --transport http https://api.arcjet.com/mcp

Claude Code opens a browser for OAuth authentication on first connection. Once authenticated, you can use the/mcpcommand to verify the connection.

codex mcp add arcjet --url https://api.arcjet.com/mcp

Codex prompts you to authenticate with Arcjet when it first connects to the server.
- OpenSettingsin the sidebar.
- Navigate toConnectorsand selectAdd custom connector.
- Configure the connector:

- Name:Arcjet

- URL:https://api.arcjet.com/mcp

Add to.cursor/mcp.jsonin your project:

{ "mcpServers": { "arcjet": { "type": "streamable-http", "url": "https://api.arcjet.com/mcp" } } }

After you add the server, Cursor shows aNeeds loginprompt. Click it to authorize Cursor to access your Arcjet account.

Add to your.vscode/mcp.jsonin your project or user settings:

{ "servers": { "arcjet": { "type": "http", "url": "https://api.arcjet.com/mcp" } } }

- Open the Command Palette (Ctrl + Shift + P on Windows/Linux or Cmd + Shift + P on macOS).
- RunMCP: Add Server.
- SelectHTTP.
- Enter the URL:https://api.arcjet.com/mcp
- Enter the name:Arcjet
- SelectWorkspaceorUserdepending on your preference.

VS Code prompts you to authenticate with OAuth on first use.

{ "mcpServers": { "arcjet": { "serverUrl": "https://api.arcjet.com/mcp" } } }

Once connected, the following tools are available to your AI assistant:

- list-teams– Lists teams the authenticated user belongs to.
- list-sites– Lists sites within a specified team.
- create-site– Creates a new site within a specified team.
- get-site-key– Returns the SDK key (ARCJET_KEY) for a specific site.
- list-requests– Lists recent requests for a site. Supports filtering by conclusion (ALLOW,DENY,ERROR) and pagination.
- get-request-details– Returns full details for a specific request including headers, rules executed, and decision information.
- explain-decision– Explains why Arcjet allowed or denied a specific request. Returns a natural language summary, per-rule breakdown, and suggested next steps.
- get-site-quota– Returns quota usage and limits for a site in the current billing window.
- analyze-traffic– Analyzes request traffic over a time period. Returns total requests, denials, denial rate, top paths, top IPs, top denial reasons, and trend compared with the previous period.
- get-anomalies– Detects unusual security patterns by comparing current traffic to the previous period. Identifies traffic spikes, geographic shifts, new threat activities, new bot signatures, risk escalation, and suspicious IP patterns.
- investigate-ip– Investigates an IP address in the context of a site. Returns geo location, threat intelligence (network type, threat activities, entity classification, risk level), and the IP’s recent request activity (conclusion breakdown, denial reasons, targeted paths, daily timeline).
- get-dry-run-impact– Analyzes what would happen if dry-run rules were promoted to live. Shows how many currently-allowed requests would have been blocked by each rule type, which IPs would be most affected, and a false-positive estimate.
- get-security-briefing– Returns a comprehensive security briefing: active rules summary, traffic analysis, threat intelligence, anomaly detection, dry-run promotion readiness, quota status, and prioritized actionable recommendations. Designed for daily consumption.
- list-rules– Lists all remote rules configured for a site with their ID, type, mode, and configuration summary.
- create-rule– Creates a new remote rule for a site. Supports rate limit, bot, shield, and filter rule types.
- update-rule– Replaces an existing remote rule configuration. All fields must be provided (full replacement).
- delete-rule– Deletes a remote rule, immediately stopping it from being evaluated.
- promote-rule– Promotes a remote rule fromDRY_RUNtoLIVEmode after verification.

Remote rules are managed through the MCP server or the Arcjet dashboard – no code changes or redeployment needed. They apply globally to all requests for a site. Onlyrate_limit,bot,shield, andfilterrule types are supported as remote rules. Rules that need parsed request body content (email,sensitive_info,prompt_injection) require the SDK.

The most common use case for remote rules is responding to an active attack. For example, if you notice suspicious traffic from a specific country, VPN, or IP address, you can create a filter rule to block it immediately without deploying new code:
- Uselist-requeststo investigate the suspicious traffic and identify patterns (for example, a specific country, IP range, or VPN usage).
- Usecreate-ruleto add a filter rule inDRY_RUNmode to verify it matches the right traffic. For example, block a specific country:ip.src.country == "XX"(ISO 3166-1 alpha-2 country code, such asUS,CN, orRU), block VPN traffic:ip.src.vpn, or block an IP range:ip.src in { 1.2.3.0/24 }.
- Uselist-requestsagain to confirm the rule is matching the expected traffic without blocking legitimate users.
- Usepromote-ruleto switch the rule fromDRY_RUNtoLIVE, immediately blocking the attack traffic.
- Once the attack subsides, usedelete-ruleto remove the block.

Use the analysis tools to maintain ongoing security awareness:

- Daily briefing:Callget-security-briefingperiodically for a comprehensive overview of your site’s security posture in a single call. It covers traffic trends, threat landscape, anomalies, dry-run readiness, quota status, and prioritized recommendations.
- Traffic analysis:Useanalyze-trafficto understand request patterns, denial rates, top paths, and top IPs. This provides the same data as the Arcjet dashboard analytics.
- Anomaly detection:Useget-anomaliesto detect unusual patterns by comparing current traffic to the previous period – traffic spikes, geographic shifts, new threat activities, or suspicious IP behavior.
- IP investigation:When you identify a suspicious IP (fromanalyze-trafficorlist-requests), useinvestigate-ipto get full context: geo location, threat intelligence, and the IP’s complete request activity on your site.
- Dry-run validation:Before promoting a rule fromDRY_RUNtoLIVE, useget-dry-run-impactto see exactly how many currently-allowed requests would be blocked, which IPs are most affected, and a false-positive risk estimate.

Investigate and block suspicious traffic

“I’m seeing a spike in denied requests on my site. Can you investigate what’s happening and help me block the source?”

The assistant callsanalyze-trafficto identify the spike, thenlist-requestsfiltered toDENYto surface the top offending IPs. It usesinvestigate-ipto pull threat intelligence for each IP, then suggests a filter rule. Usingcreate-rule, it creates the rule inDRY_RUNmode so you can verify the match before callingpromote-ruleto go live.

“Give me a security briefing for my production site.”

The assistant callslist-teamsandlist-sitesto locate your production site, then callsget-security-briefing. It returns a summary covering active rules, traffic trends compared with the previous period, anomaly detection, threat intelligence highlights, dry-run promotion readiness, quota status, and prioritized recommendations you can act on immediately.

Set up bot protection without redeploying

“Add bot protection to my marketing site – start in dry-run mode so I can check it’s not blocking real users.”

The assistant callslist-teamsandlist-sitesto find the site, thencreate-ruleto add abotrule withmode: DRY_RUNconfigured to block automated traffic. After traffic flows through, ask the assistant to callget-dry-run-impactto see how many requests would have been blocked and to estimate false-positive risk. When you’re satisfied, ask it to callpromote-ruleto switch the rule toLIVE.

- Verify the endpoint– always confirm you are connecting tohttps://api.arcjet.com/mcp.
- Review tool calls– enable confirmation prompts in your AI client so you can review actions before they execute.
- Trusted clients only– only connect from AI clients you trust. Connecting grants the AI tool the same access as your Arcjet account.

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

Remote MCP server (Streamable HTTP) at https://mcp.agenticrail.nz/ — deterministic step-order enforcement for AI agents. evaluate_step returns ALLOW or DENY before a step runs; verify_receipt proves a sequence's Ed25519-signed, hash-chained receipt chain is intact. No auth required: omit the bearer token and calls run on the public demo key. That first clause matters — the form has no "remote/hosted" field, and putting the endpoint in the description is the convention on that list ("Fully REMOTE! Just use…"). The rest mirrors your own server card verbatim, so the listing and the card can't drift.

Deterministic security preflight for AI agents. Check URLs, files and shell commands before acting.

EU AI Act compliance scanner for Python AI agents — 10 tools for scanning, analysis, and remediation

Remediate vulnerabilities found by Contrast products using LLM and Coding Agent capabilities.

AES-256-GCM + Argon2id encrypted local vault that resolves {{PLACEHOLDER}} secrets for AI agent credentials.

MCP security scanner — finds tool poisoning, credential leaks, and insecure transports in AI agent configurations.

AMS – Deterministic Agent Pipeline with A2A‑style Orchestration and Cryptographic Audit

An AI penetration testing tool that uses natural language to operate various security tools like nmap, sqlmap, and metasploit.

Encrypted secrets vault for AI agents stores API keys in AES-256-GCM and resolves them at MCP runtime so plaintext never touches the LLM transcript.