IACR MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| search_papersC | Search for papers in the IACR Cryptology ePrint Archive |
| get_paper_detailsC | Retrieve details of a specific paper by its ID |
| download_paperC | Download a paper in PDF or TXT format |
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 3 tools
Each tool has a clearly distinct purpose: download_paper retrieves files, get_paper_details fetches metadata, and search_papers finds papers. There is no overlap in functionality, making it easy for an agent to select the correct tool without confusion.
All tool names follow a consistent verb_noun pattern (download_paper, get_paper_details, search_papers) with clear, descriptive verbs. There are no deviations in naming conventions, ensuring predictability and readability.
With only 3 tools, the server feels thin for a paper archive domain, as it lacks operations like filtering, listing categories, or updating metadata. While the core functions are covered, the count is borderline minimal for typical agent workflows.
The tools cover essential CRUD-like operations: search (read), get details (read), and download (retrieve). However, there are minor gaps, such as no ability to list papers by year or category, which agents might need to work around for more complex queries.