The Jina AI MCP, built by community, provides access Jina AI services — Reader API for web content extraction, Embeddings API for semantic search, Reranker for relevance scoring, and Classifier for zero-shot categorization tasks. It is community-built and best for ai-ml.
Its repository has had no commits since December 2024 (20 months ago).
by community
No commits in 20 months
The last commit GitHub reports for this project is from December 2024. The repository is not archived and the maintainer may return. Treat it as feature-frozen and check the alternatives below before you depend on it.
About
Access Jina AI services — Reader API for web content extraction, Embeddings API for semantic search, Reranker for relevance scoring, and Classifier for zero-shot categorization tasks.
Trust verdict
How grades are computed →Grade C (66/100, mixed) from 1 measured signal, based on repository evidence. Only one signal stands behind it, so treat the grade as provisional.
What was measured
- Repository maintenance15/100 · weight 20
No push or release in over eighteen months. Nobody is patching this if the upstream API it wraps changes. — last push 2024-12-11.
- Source verification100/100 · weight 25
The repository URL was confirmed to resolve against the live GitHub API and is not archived.
- Provenance65/100 · weight 10
Community-built. That is not a mark against it — most of the ecosystem is community-built — but there is no vendor accountable for keeping it working.
- Listing ↔ repository match100/100 · weight 5
The listing name lines up with the linked repository wong2/mcp-jina-reader.
What could not be measured
These contributed nothing to the score — not a penalty, not a zero. They are why the confidence reads the way it does.
- Live MCP handshakeunknown
No remote endpoint to handshake — this server installs and runs locally over stdio, so there is nothing to probe from the outside.
- Measured uptimeunknown
No probe history recorded for this server yet.
- Tool-schema stabilityunknown
Drift is a difference between two successive checks, and this server has none recorded.
Categories
Works With
Frequently Asked Questions
What is Jina AI MCP?
Who built Jina AI MCP?
Is Jina AI MCP free?
How do I install Jina AI MCP?
What does Jina AI MCP integrate with?
Repo Health
Local/stdio install — runs on your machine, so there is no remote endpoint to verify live. Trust signal below is from the source repo.
- Last commit
- 2y ago
- Install
- npm
Quick Info
- Install Type
- npm
- Author
- community
- Categories
- 2
- Integrations
- 3
Related Servers
DeepSeek MCP
Integrate DeepSeek API for cost-effective reasoning and code generation — access DeepSeek-V3 and DeepSeek-R1 models for complex problem solving, mathematical reasoning, and code synthesis.
Qwen (Alibaba Cloud) MCP
Access Alibaba Cloud Qwen LLM family via API — long-context processing with Qwen-Long, multimodal with Qwen-VL, and code generation with Qwen-Coder for multilingual AI workflows.
Moonshot AI (Kimi) MCP
Connect to Moonshot AI Kimi API for long-context document analysis up to 200K tokens, Chinese-English bilingual processing, web search-augmented generation, and multimodal understanding.
MCP Jenkins
a Python MCP server for Jenkins (lanbaoshen/mcp-jenkins, published to PyPI as mcp-jenkins) and the alternative to the official Jenkins MCP plugin: where the plugin has to be installed into the controller from the update centre, this one runs beside Jenkins and talks to it over the ordinary REST API, so you can point it at a Jenkins you do not administer. Install it with uvx mcp-jenkins, pip install mcp-jenkins, or the ghcr.io/lanbaoshen/mcp-jenkins container. Credentials go in as --jenkins-url, --jenkins-username and --jenkins-password (an API token works in place of the password), and on the HTTP transport the same three can be supplied per-connection as the x-jenkins-url, x-jenkins-username and x-jenkins-password headers, which is what lets one running instance serve several Jenkins controllers. Three transports are available via --transport: stdio (the default), sse, and streamable-http, which listens on 0.0.0.0:9887 unless --host and --port say otherwise. The tool set is wider than most Jenkins integrations. Jobs and pipelines: get_item, get_item_config, get_item_parameters, get_all_items, query_items for pattern search, and build_item to trigger. Builds: get_build, get_build_console_output, get_build_parameters, get_build_test_report, get_build_scripts, get_running_builds and stop_build, plus get_all_build_artifacts, get_build_artifact and get_build_artifact_url for pulling artifacts out of a finished run. Queue: get_all_queue_items, get_queue_item, cancel_queue_item. Agents: get_all_nodes, get_node, get_node_config. The plugin tools are the part with no equivalent elsewhere — get_all_plugins, get_plugin, get_plugins_with_updates, get_plugins_with_backup, get_plugin_dependency_graph (Graphviz output), and get_plugins_with_problems, which reports missing dependencies and version mismatches and turns a plugin upgrade audit into one question. Two flags matter for safety. run_groovy_script executes arbitrary Groovy on the controller, which is full remote code execution against your CI; --read-only disables it along with every other mutating tool and is the right default for an agent that only needs to read build state. --jenkins-timeout defaults to 5 seconds, which is often too short for a large get_all_items on a busy controller.
TeamCity MCP
Connect to JetBrains TeamCity CI/CD via REST API — trigger build configurations, monitor build queues, inspect test results, manage agents, and query build artifacts for developer workflow automation.
Sponsored
Better Stack
Free PlanGet alerted when your APIs, browser tests, payment pipelines, or MCP server dependencies go down. Used by 100K+ developers.
Start monitoring free →