Schema | axur-mcp

axur-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
`AXUR_API_TOKEN`	Yes	Your Axur API token for authentication.

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
ticketsC	Search, retrieve, and inspect Axur platform tickets. Actions: list (filter/search tickets), get (single ticket), bulk_get (multiple tickets by keys), history (ticket change history), types (list supported ticket types).
ticket_detailsA	Retrieve detailed ticket information from Axur: field values, texts/comments, detection snapshots, attachments, lifecycle transitions, takedown options, and timeline.
ticket_statsA	Retrieve Axur ticket statistics: counts by status, incidents by threat type, takedown/treatment metrics and uptime, global and market-segment incident medians/means. Note: from/to date range must not exceed 90 days.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/just5ky/axur-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server