mcp-entrascopes
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ENTRASCOPES_CACHE_DIR | No | Override the cache directory. | |
| ENTRASCOPES_SCOPES_URL | No | Override the required scope dataset URL. | |
| ENTRASCOPES_RESOURCES_URL | No | Override the optional resource-name dataset URL. | |
| ENTRASCOPES_CACHE_TTL_MINUTES | No | Cache freshness interval; 0 refreshes on each request. | 60 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_entra_applicationsA | Search Microsoft first-party applications by app name/ID, published scope, resource name/ID, FOCI status, or public-client status. This is not tenant consent state. |
| get_entra_applicationA | Get published scope metadata for one exact Microsoft first-party application ID, optionally narrowed to a resource. |
| get_entrascopes_data_statusA | Report dataset provenance, refresh time, cache origin, and record counts. Set refresh to bypass the normal cache TTL. |
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
Search, exact lookup by application ID, and dataset status are clearly distinct operations with no meaningful overlap. The descriptions make it easy to select the right tool.
All tools use a verb_noun pattern and snake_case. The only minor inconsistency is 'get_entrascopes_data_status' using the server name prefix instead of following the 'entra_application(s)' noun pattern used by the other two tools.
Three tools is well-scoped for a read-only reference dataset: search, exact lookup, and data status. Each tool earns its place without redundancy.
For the stated purpose of exploring Microsoft first-party application scope metadata, the surface covers search, precise retrieval, and dataset freshness/provenance. No CRUD operations are needed since this is a read-only metadata source.