mcp-registry/io.github.bitrix24/bitrix-mcp-rest · v0.2.0
As of 2026-10-18 02:31 UTC, the Bitrix24 Bitrix Mcp Rest MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 2 minutes.
MCP server that delivers up-to-date Bitrix24 REST API documentation.
Claude Code
claude mcp add --transport http bitrix24-bitrix-mcp-rest-mcp-server https://mcp-dev.bitrix24.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"bitrix24-bitrix-mcp-rest-mcp-server": {
"type": "http",
"url": "https://mcp-dev.bitrix24.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
9 parameter(s) across 5 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call.
5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones.
Handshake + tools/list takes ~1,831 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 5 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.bitrix24%2Fbitrix-mcp-rest/fixes
{
"name": "bitrix-search",
"description": "Search Bitrix24 REST docs by natural-language query and return a short plain-text list of matches (method/event/article/app doc) with name, type, and brief description. Use the exact name/title from results when calling details tools. Optional filters: `limit` and `doc_type` (method|event|other|app_development_docs).",
"inputSchema": {
"type": "object",
"required": [
"query"
],
"properties": {
"limit": {
"anyOf": [
{
"type": "integer"
},
{
"type": "null"
}
],
"default": null
},
"query": {
"type": "string"
},
"doc_type": {
"anyOf": [
{
"type": "array",
"items": {
"enum": [
"method",
"event",
"other",
"app_development_docs"
],
"type": "string"
}
},
{
"type": "null"
}
],
"default": null
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.bitrix24/bitrix-mcp-rest"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.bitrix24/bitrix-mcp-rest"}) over MCP.
bitrix-search ~189 tokensbitrix-method-details ~146 tokensbitrix-app-development-doc-details ~110 tokensbitrix-article-details ~99 tokensbitrix-event-details ~95 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.bitrix24%2Fbitrix-mcp-rest?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.bitrix24%2Fbitrix-mcp-rest?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.bitrix24%2Fbitrix-mcp-rest.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.bitrix24%2Fbitrix-mcp-rest.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.bitrix24%2Fbitrix-mcp-rest?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:d8dd6ba384fd6e5c…, first seen 2026-10-17, included at leaf 13918 of 19,761. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable other servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-18 02:31 UTC, the Bitrix24 Bitrix Mcp Rest MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 2 minutes.
Bitrix24 Bitrix Mcp Rest MCP server advertises 5 tools, including bitrix-app-development-doc-details, bitrix-article-details, bitrix-event-details, bitrix-method-details, bitrix-search.
Point your MCP client at this streamable-http endpoint: https://mcp-dev.bitrix24.com/mcp
Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.