attestify-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ATTESTIFY_API_KEY | No | Tenant API key issued via POST /api/keys. Optional; without it runs are unauthenticated. | |
| ATTESTIFY_BASE_URL | No | The base URL of the Attestify OS API. | https://attestifyos.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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| attestify_researchA | Run a deep research query through the Attestify Research Agent (researcher-v2). Returns a structured briefing with executive summary, key findings, and caveats. Each call is metered at $0.023 USDC and logged to the Attestify evidence ledger. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusing it with another tool. The tool's purpose is clearly defined in its description.
The single tool name follows a credible server_prefix_action convention, and with only one tool there are no inconsistencies to evaluate.
A single tool is too few for a server named 'attestify-mcp' that likely needs additional operations like listing or managing research jobs and evidence ledger entries.
The tool only runs a research query but provides no way to list previous queries, retrieve detailed results, or manage the evidence ledger, leaving significant gaps in the expected domain.