YRB-HES Evidence MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YRB3_MCP_DATABASE_URL | No | Optional database URL. Defaults to a local Unix socket connection to dbname=rag_sag. |
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 |
|---|---|
| healthcheckB | Check PostgreSQL, yrb3_v3 tables, read-only identity and current row counts. |
| get_document_overviewB | Return metadata, abstract screening, heading, Subchunk, SAG and spatiotemporal counts for one document. |
| search_evidenceB | Search YRB3 evidence with exact if_yrbhg gate, lexical Subchunk recall, Event expansion and spatiotemporal attachment. |
| compare_evidenceA | Build bounded cross-paper comparison rows with claims, entities, spatiotemporal evidence and source locators. |
| get_subchunk_contextB | Return one Subchunk, its title path, adjacent context and linked Event/spatiotemporal evidence. |
| search_entityA | Search canonical SAG entities by name, alias key and optional entity type. |
| expand_entityC | Expand one canonical entity to linked Event, Subchunk, spatiotemporal evidence and verified edges. |
| get_spatiotemporal_evidenceB | Query structured spatial and temporal evidence with document, Subchunk and research-area filters. |
| trace_sourceB | Trace an Event, Subchunk or spatiotemporal evidence ID back to Markdown content and hashes. |
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/TIGERwu0118/yrb_hes_mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server