Jina.ai Grounding MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JINAAI_API_KEY | Yes | Your Jina.ai API key |
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 |
|---|---|
| ground_statementA | Ground a statement using real-time web search results to check factuality. When providing URLs via the references parameter, ensure they are publicly accessible and contain relevant information about the statement. If the URLs do not contain the necessary information, try removing the URL restrictions to search the entire web. |
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
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'ground_statement' has a clearly defined and distinct purpose: fact-checking statements using web search.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'ground_statement' follows a clear verb_noun pattern, which would be consistent if more tools were added.
A single tool is too few for a server that appears to handle grounding/verification tasks, as it suggests an incomplete or minimal surface. Typically, such a domain might include tools for different grounding methods, batch processing, or related operations.
The server is severely incomplete for its apparent grounding/fact-checking domain. It lacks essential operations like grounding multiple statements, verifying against specific sources, or handling different input formats, which limits agent workflows.