evident
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | No | API key for Anthropic, required for extract() LLM-based schema extraction |
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 |
|---|---|
| fetchA | Fetch a URL through the resilience ladder (Tier 1 static -> Tier 2 rendered, escalating only when the failure mode suggests it'll help). |
| extractA | Fetch a URL and extract structured fields matching a caller-supplied
JSON schema, using an LLM — works on ANY site, not just ones with a
dedicated recipe. Use |
| list_recipesA | List every registered extraction recipe (platform-specific, verified
parsers — e.g. Greenhouse, Lever, Ashby job boards). Check this before
calling |
| use_recipeA | Invoke a specific recipe by id (see |
| health_checkB | Proactively verify a recipe or a raw URL is still working, rather than discovering breakage only when a real search silently returns zero results. Pass either a recipe id (checks with a known-good test slug isn't available generically, so this reports whether the endpoint itself is reachable and returning the expected top-level shape) or a plain URL (runs it through the ladder and reports the outcome). |
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/Kaushalendra-Marcus/evident'
If you have feedback or need assistance with the MCP directory API, please join our Discord server