Skip to main content
Glama
enesjakozh
spences10

Jina.ai Grounding MCP Server

by spences10
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

mcp-jinaai-grounding

⚠️ Notice

This repository is no longer maintained.

The functionality of this tool is now available in mcp-omnisearch, which combines multiple MCP tools in one unified package.

Please use mcp-omnisearch instead.

A Model Context Protocol (MCP) server for integrating Jina.ai's Grounding API with LLMs. This server provides efficient and comprehensive web content grounding capabilities, optimized for enhancing LLM responses with factual, real-time web content.

Related MCP server: MCP JinaAI Search Server

Features

  • 🌐 Advanced web content grounding through Jina.ai Grounding API

  • 🚀 Real-time content verification and fact-checking

  • 📚 Comprehensive web content analysis

  • 🔄 Clean format optimized for LLMs

  • 🎯 Precise content relevance scoring

  • 🏗️ Built on the Model Context Protocol

Configuration

This server requires configuration through your MCP client. Here are examples for different environments:

Cline Configuration

Add this to your Cline MCP settings:

{
	"mcpServers": {
		"jinaai-grounding": {
			"command": "node",
			"args": ["-y", "mcp-jinaai-grounding"],
			"env": {
				"JINAAI_API_KEY": "your-jinaai-api-key"
			}
		}
	}
}

Claude Desktop with WSL Configuration

For WSL environments, add this to your Claude Desktop configuration:

{
	"mcpServers": {
		"jinaai-grounding": {
			"command": "wsl.exe",
			"args": [
				"bash",
				"-c",
				"JINAAI_API_KEY=your-jinaai-api-key npx mcp-jinaai-grounding"
			]
		}
	}
}

Environment Variables

The server requires the following environment variable:

  • JINAAI_API_KEY: Your Jina.ai API key (required)

API

The server implements MCP tools for grounding LLM responses with web content:

ground_content

Ground LLM responses with real-time web content using Jina.ai Grounding.

Parameters:

  • query (string, required): The text to ground with web content

  • no_cache (boolean, optional): Bypass cache for fresh results. Defaults to false

  • format (string, optional): Response format ("json" or "text"). Defaults to "text"

  • token_budget (number, optional): Maximum number of tokens for this request

  • browser_locale (string, optional): Browser locale for rendering content

  • stream (boolean, optional): Enable stream mode for large pages. Defaults to false

  • gather_links (boolean, optional): Gather all links at the end of response. Defaults to false

  • gather_images (boolean, optional): Gather all images at the end of response. Defaults to false

  • image_caption (boolean, optional): Caption images in the content. Defaults to false

  • enable_iframe (boolean, optional): Extract content from iframes. Defaults to false

  • enable_shadow_dom (boolean, optional): Extract content from shadow DOM. Defaults to false

  • resolve_redirects (boolean, optional): Follow redirect chains to final URL. Defaults to true

Development

Setup

  1. Clone the repository

  2. Install dependencies:

pnpm install

  1. Build the project:

pnpm run build

  1. Run in development mode:

pnpm run dev

Publishing

  1. Update version in package.json

  2. Build the project:

pnpm run build

  1. Publish to npm:

pnpm run release

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

MIT License - see the LICENSE file for details.

Acknowledgments

Available Tools

1 tool
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.

ParametersJSON Schema
NameRequiredDescriptionDefault
statementYesStatement to be grounded
referencesNoOptional list of URLs to restrict search to. Only provide URLs that are publicly accessible and contain information relevant to the statement. If the URLs do not contain the necessary information, the grounding will fail. For best results, either provide URLs you are certain contain the information, or omit this parameter to search the entire web.
no_cacheNoWhether to bypass cache for fresh results

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes key traits like using real-time web search, the impact of URL restrictions (grounding may fail if URLs lack info), and the option to bypass cache. However, it omits details such as rate limits, authentication needs, or specific error handling, leaving some behavioral aspects unclear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded, starting with the core purpose. Both sentences earn their place by adding useful context about URL handling, though it could be slightly more streamlined by avoiding minor redundancy with the schema (e.g., repeating URL accessibility advice).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (fact-checking with web search) and no annotations or output schema, the description is moderately complete. It covers the main purpose and parameter usage but lacks details on output format, error cases, or performance expectations, which are important for an agent to use it effectively without structured output guidance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds minimal value beyond the schema by reiterating guidance on the references parameter (e.g., ensuring URLs are accessible and relevant), but it doesn't provide additional semantic context or examples not covered in the schema, warranting a baseline score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('ground') and resource ('statement'), explaining it uses real-time web search to check factuality. It distinguishes the action from generic search by specifying the grounding objective, and with no sibling tools, this level of specificity is excellent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context on when to use the tool (for fact-checking statements) and includes guidance on the references parameter (e.g., ensure URLs are publicly accessible and relevant, or omit to search the entire web). However, it lacks explicit alternatives or exclusions, as there are no sibling tools, so it doesn't fully address when-not-to-use scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.7/5.0
Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness2/5

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.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • MCP JinaAI Search Server

    spences10
    A
    license
    B
    quality
    F
    maintenance
    Enables efficient web search integration with Jina.ai's Search API, offering clean, LLM-optimized content retrieval with support for various content types and configurable caching.
    1
    26
    3
    MIT

  • Jina Web Search MCP

    hypersniper05
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables web content retrieval and semantic search capabilities through the Jina AI API. Provides tools to fetch content from URLs and perform intelligent web searches with natural language queries.
    3
    MIT

  • Jina AI Remote MCP Server

    cedric448
    A
    license
    Not graded
    quality
    C
    maintenance
    Provides access to Jina AI's web reading, search, embeddings, and reranking capabilities. Enables URL content extraction, web/arXiv/image search, document deduplication, and relevance ranking through natural language.
    Apache 2.0

Appeared in Searches

Latest Blog Posts

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/spences10/mcp-jinaai-grounding'

If you have feedback or need assistance with the MCP directory API, please join our Discord server