_ registry / mcp http-sse · checked 1h ago

b24-dev-mcp

https://mcp-dev.bitrix24.com

Registry code: 0aa5dd1d539355fe

api record

The official MCP server that gives AI assistants direct, up-to-date access to Bitrix24 REST API documentation.

endpoint
https://mcp-dev.bitrix24.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is b24-dev-mcp live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is b24-dev-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does b24-dev-mcp have?
5 tools: bitrix-event-details, bitrix-app-development-doc-details, bitrix-method-details, bitrix-article-details, bitrix-search.
Is b24-dev-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.9%

90 days 99.4%· all time 99.4%

latency
463ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 309 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
knowledge & reference documentation & docs search
used for
  • search bitrix24 rest api docs
  • get details of a bitrix24 method
  • read bitrix24 event docs
takes → gives
text → text
tools
5 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 5 tools
5 never probed 0 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • bitrix-event-details reads unknown never probed

    Fetch Bitrix24 event documentation by exact event name (use `bitrix-search` with doc_type event). Returns Markdown with title, metadata (URL/module/category), description, and content.

    mcp-tool

    {
  "type": "object",
  "required": [
    "title_or_hint"
  ],
  "properties": {
    "title_or_hint": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • bitrix-app-development-doc-details reads unknown never probed

    Fetch Bitrix24 app development documentation by exact title (use `bitrix-search` with doc_type app_development_docs). Returns plain text labeled fields (Title, URL, Module, Category, Description, Content) without Markdown.

    mcp-tool

    {
  "type": "object",
  "required": [
    "title_or_hint"
  ],
  "properties": {
    "title_or_hint": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • bitrix-method-details reads unknown never probed

    Get details for a Bitrix24 REST method by exact name (use `bitrix-search` first). Returns plain text with labeled sections including parameters, returns, errors, and examples. Optional `field` limits output; `filter` narrows params by entity or examples by language.

    mcp-tool

    {
  "type": "object",
  "required": [
    "method"
  ],
  "properties": {
    "field": {
      "type": "string",
      "default": "all"
    },
    "filter": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "method": {
      "type": "string"
    }
  }
}
    arguments 26 lines
  • bitrix-article-details reads unknown never probed

    Fetch a non-method Bitrix24 documentation article by exact title (use `bitrix-search` with doc_type other). Returns Markdown with title, metadata (URL/module/category), description, and content.

    mcp-tool

    {
  "type": "object",
  "required": [
    "title_or_hint"
  ],
  "properties": {
    "title_or_hint": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • bitrix-search reads unknown 4h ago

    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).

    mcp-tool

    {
  "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
    }
  }
}
    arguments 42 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 0aa5dd1d539355fe.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/0aa5dd1d539355fe/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/0aa5dd1d539355fe/badge.svg)](https://brick.blue/agent/0aa5dd1d539355fe?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on bitrix24.com 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.