asqav-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASQAV_API_KEY | Yes | Your Asqav API key used for authentication. | |
| ASQAV_API_URL | No | The Asqav API URL (optional, defaults to https://api.asqav.com). | https://api.asqav.com |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_policyC | Check if an action is allowed by the organization's policies. |
| preflight_checkA | Combined agent-status + policy-allowed check; returns CLEARED / NOT CLEARED summary. |
| sign_actionB | Create a signed audit record for an AI agent action. |
| list_agentsA | List all registered AI agents in the organization. |
| get_agentB | Get details for a specific AI agent. |
| verify_signatureC | Verify an existing signature by signature_id. |
| verify_outputA | Verify a signature and confirm the signed payload's output_hash matches expected_output. |
| gate_actionA | Pre-execution gate; signs the decision and returns APPROVED, DENIED, or PENDING_APPROVAL. After an APPROVED gate, call complete_action(gate_id, result) to close the bilateral receipt. |
| complete_actionA | Sign the outcome of a gate-approved action and bind it to the approval signature as a bilateral receipt (approval + outcome linked by gate_id). |
| enforced_tool_callA | Strong-enforcement path: policy-check, optionally forward to |
| create_tool_policyA | Upsert a local tool enforcement policy used by gate_action and enforced_tool_call; evaluated in-process (no API hop) and tool_endpoint enables bilateral request+response signing. |
| list_tool_policiesA | List all active local tool enforcement policies. |
| delete_tool_policyB | Remove a local enforcement policy for a tool. |
| scan_tool_definitionA | Scan an MCP tool definition for prompt injection, hidden unicode, dangerous schema fields, typosquatting, and hardcoded secrets; returns a risk assessment. |
| scan_all_toolsA | Scan every registered tool policy for typosquatting and hidden unicode; returns a per-tool risk assessment summary. |
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/jagmarques/asqav-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server