FortiAnalyzer MCP Server
by forticrevs
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FAZ_HOST | Yes | HTTPS origin, optionally ending in /jsonrpc | |
| FAZ_API_KEY | No | Bearer API key (FAZ_API_TOKEN is an alias) | |
| FAZ_MCP_PORT | No | Network transport port | 8000 |
| FAZ_PASSWORD | No | Session password | |
| FAZ_USERNAME | No | Session username | |
| FAZ_AUTH_MODE | No | auto, api_key, or session | auto |
| FAZ_CA_BUNDLE | No | PEM bundle for a private CA | |
| FAZ_LOG_LEVEL | No | Server logging level | INFO |
| FAZ_ALLOW_HTTP | No | Explicit development-only HTTP opt-in | false |
| FAZ_VERIFY_SSL | No | Verify the appliance certificate | true |
| FAZ_MAX_RESULTS | No | Maximum rows accepted by bounded tools | 200 |
| FAZ_DEFAULT_ADOM | No | Default ADOM | root |
| FAZ_MCP_BIND_HOST | No | Network transport bind address | 127.0.0.1 |
| FAZ_MCP_STATELESS | No | Streamable HTTP stateless mode | false |
| FAZ_MCP_TRANSPORT | No | stdio, streamable-http, or sse | stdio |
| FAZ_TIMEOUT_SECONDS | No | Normal API timeout | 30 |
| FAZ_MCP_ALLOWED_HOSTS | No | Additional comma-separated Host header allowlist | |
| FAZ_MCP_JSON_RESPONSE | No | Use JSON rather than SSE response bodies | true |
| FAZ_ENABLE_WRITE_TOOLS | No | Register the guarded raw mutation tool | false |
| FAZ_MCP_ALLOWED_ORIGINS | No | Comma-separated browser-origin allowlist | |
| FAZ_MAX_LOG_SEARCH_HOURS | No | Specific-device search window | 24 |
| FAZ_MAX_ACTIVE_LOG_SEARCHES | No | Maximum active/starting LogView tasks | 8 |
| FAZ_LOG_SEARCH_TIMEOUT_SECONDS | No | Convenience search timeout | 30 |
| FAZ_MAX_ALL_DEVICES_SEARCH_HOURS | No | All-device search window | 1 |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/forticrevs/fortianalyzer-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server