VISTA-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | bind host | 0.0.0.0 |
| MCP_PORT | No | bind port (served path is /mcp/) | 8100 |
| ORB_ASK_URL | No | ORB ask API queried after the analysis for troubleshooting steps | http://172.17.96.58:9345/orb/api/ask |
| ORB_ENABLED | No | set 0 to skip the ORB troubleshooting step (report is built without it) | 1 |
| ORB_TIMEOUT | No | ORB request timeout (s) — ORB is deep-research and slow (~45–140 s); fail-open on timeout | 180 |
| ORB_USERNAME | No | username sent to ORB | logV_mcp_call |
| LOGV_API_BASE | No | Log Visualizer AgentAssist base | http://127.0.0.1:8802/logVisualizer/api/agent_assist |
| MAX_LOG_BYTES | No | streaming fetch cap for the injected log | 52428800 |
| MCP_LOG_LEVEL | No | terminal flow-log verbosity (DEBUG previews the report text) | INFO |
| LOGV_VIEW_BASE | No | SPA base for the returned session links/iframe | https://vista.fortinet.com/logVisualizer |
| MCP_AUTH_TOKEN | No | shared bearer token the partner must send. The server refuses to start with an empty/default token unless MCP_ALLOW_INSECURE=1. Set a strong value in prod. | vista-dev-token |
| MCP_ALLOW_INSECURE | No | 1 permits the dev/empty token (local dev only) | |
| MCP_FETCH_CA_BUNDLE | No | PEM bundle of extra CAs to trust on outbound calls (internal PKI). Bad path ⇒ the server refuses to start | |
| MCP_FETCH_INSECURE_TLS | No | 1 skips TLS verification for every host (blunt; prefer the host list) | |
| MCP_ALLOW_PRIVATE_FETCH | No | 1 allows fetching private/loopback URLs (needed for the local test client; prod signed URLs are public) | |
| MCP_FETCH_INSECURE_TLS_HOSTS | No | comma-separated hosts to skip TLS verification for — a scoped curl -k, for hosts whose cert name doesn't match |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
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/ProjectVISTA-Kashcode/vista-agent-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server