Skip to content

MCP servers › com.itbisp › itbisp

MCP server · registry snapshot 2026-11-06 · last tested 2026-11-06

itbisp MCP server

Registry name com.itbisp/itbisp

ITBI SP · São Paulo real estate prices — the publisher's title

by itbisp.com · domain (the registry's namespace rule)repository owner on GitHub: itbisp (organization)Source ↗Website ↗

Real sale prices (ITBI) for every building, street and district in São Paulo, plus homes for sale. — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-11-06version 0.3.0streamable HTTP10 tools

Summary

com.itbisp/itbisp is a remote MCP server listed in the official MCP registry at version 0.3.0, under the namespace of the domain itbisp.com. Its linked repository is github.com/itbisp/itbisp-plugin; GitHub reports its owner as itbisp, an organization. On 2026-11-06 ProtocolProbe connected to it in read-only mode and read its inventory: 10 tools, 0 resources and 0 prompts.

Record checks

4 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Repository
public
Tools
10
Last tested
2026-11-06

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-06 (itbisp.com), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (0.3.0).

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-06
Mode
read-only (no tool calls)
Latest version
0.3.0, published 2026-11-05 (registry, as of the 2026-11-06 snapshot)
First listed version
2026-11-05 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-11-06
Package and repository
checked 2026-11-06
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-05, listed on 2026-11-06 with version 0.3.0 (published 2026-11-05).

Source: the official MCP Registry list on 2026-11-05 and on 2026-11-06.

What it is

What does this server offer?

Observed inventory
10tools
0resources
0prompts

None of its 10 tools are described as changing anything. For 10 the reading was uncertain, so no mark is shown.

  • buscar_imoveison 1 other server

    “Busca imóveis à venda na cidade de São Paulo (apartamentos, casas, salas comerciais, terrenos) em anúncios de imobiliárias, deduplicados: cada resultado é um imóvel com o menor preço pedido, o link d…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    28 inputs
    • qstring“Pedido em linguagem natural, em português: '3 quartos perto do metrô em Pinheiros até 1,8 mi com varanda', 'studio até 500 mil perto da estação Faria Lima', 'c…”
    • bairroarray“Um ou mais bairros, como as pessoas escrevem: ["Pinheiros", "Vila Madalena"].”
    • ruastring“Nome da rua, com ou sem 'Rua'/'Av.': "Rua dos Pinheiros".”
    • estacaostring“Estação de metrô/trem/monotrilho mais próxima do imóvel: "Fradique Coutinho", "Faria Lima".”
    • metro_max_minteger“Distância máxima (metros, em linha reta) até a estação mais próxima.”
    • latnumber“Latitude do ponto de referência (use com lon e raio_m).”
    • lonnumber“Longitude do ponto de referência.”
    • raio_minteger“Raio em metros em torno de lat/lon.”
    • bboxarray“Caixa [oeste, sul, leste, norte] em graus.”
    • poligonoarray“Anel do polígono como lista de [lon, lat] (GeoJSON).”
    • tipoarray“Tipos aceitos.”
    • preco_minnumber“Preço mínimo em reais.”
    • preco_maxnumber“Preço máximo em reais: 1,5 milhão = 1500000.”
    • area_minnumber“Área mínima em m² (privativa/útil do anúncio).”
    • area_maxnumber“Área máxima em m².”
    • quartos_mininteger“Quartos (dormitórios), no mínimo.”
    • suites_mininteger“Suítes, no mínimo.”
    • vagas_mininteger“Vagas de garagem, no mínimo.”
    • so_preco_bomboolean“Só imóveis com pedido abaixo do mercado (comparados ao mesmo prédio, rua ou bairro e ao pago no ITBI).”
    • ordemstring“Ordem.”
    • limiteinteger“Quantos imóveis devolver (1-20).”
    • paginainteger“Página de resultados.”
    • caracteristicasarray“Características que o imóvel precisa ter, lidas do texto e da lista de características dos anúncios (todas valem): vista, varanda, varanda_gourmet, churrasquei…”
    • visaoarray“Etiquetas estimadas pela foto principal do anúncio (todas valem).”
    • faixa_avaliacaostring“Corta pelo selo de preço: so_abaixo (só abaixo do mercado), ate_mercado (tira os acima do mercado), sem_muito_caros (tira só os 30%+ acima).”

    and 3 more not listed here.

  • ficha_imovelon 1 other server

    “Ficha completa de um imóvel devolvido por buscar_imoveis: todos os anúncios ativos (imobiliária, preço pedido, link, código), histórico de preço, fotos, descrição, características, condomínio e IPTU,…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“id do imóvel devolvido por buscar_imoveis (ex.: im_1217cd8f3590).”
  • comparaveis_enderecoon 1 other server

    “Para um endereço da cidade de São Paulo (rua e número) ou um ponto lat/lon: imóveis à venda no mesmo prédio e ao redor parecidos com o informado, R$/m² pedido mediano, uma estimativa de preço pedido …”

    Publisher declares: read-only yes · idempotent yes · open-world no

    8 inputs
    • enderecostring“Rua e número: "Rua Fradique Coutinho, 1000".”
    • latnumber“Latitude, se não houver endereço.”
    • lonnumber“Longitude.”
    • tipostring“Tipo do imóvel avaliado (padrão: o mais comum no prédio, ou apartamento).”
    • areanumber“Área do imóvel avaliado em m²; filtra comparáveis de tamanho parecido e gera a estimativa.”
    • quartosinteger“Quartos do imóvel avaliado.”
    • raio_minteger“Raio dos comparáveis ao redor, em metros.”
    • limiteinteger“Quantos comparáveis listar.”
  • resumo_bairroon 1 other server

    “Resumo de um bairro de São Paulo: quantos imóveis estão à venda, preço pedido mediano e R$/m² pedido (no total e por número de quartos), quantos estão abaixo do mercado, perto do metrô, e o preço rea…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    2 inputs, 1 required
    • bairrostringrequired“Nome do bairro: "Moema", "Vila Madalena".”
    • tipostring“Tipo de imóvel.”
  • comparaveis_imovelon 1 other server

    “Mostra a evidência do selo de preço de um imóvel: os imóveis parecidos (mesmo prédio, rua ou bairro, tamanho próximo) que entraram na conta, com preço, área e R$/m², a mediana usada, e as vendas regi…”

    2 inputs, 1 required
    • idstringrequired“id do imóvel (campo id de buscar_imoveis), ex.”
    • limiteinteger“Quantos comparáveis mostrar.”
  • “Ordena imóveis à venda pelo que importa para a pessoa: tempo de trajeto até o trabalho (transporte, carro, bike ou a pé), distância de pessoas importantes (pais, escola), metrô a pé, preço contra par…”

    15 inputs
    • qstring“Pedido em linguagem natural: 'casal com bebê, trabalho na Faria Lima, sogros na Rua Cardeal Arcoverde, até 1,8 mi, 3 quartos, metrô perto, com varanda'.”
    • trabalhostring“Endereço ou lugar do trabalho/estudo: 'Av.”
    • pessoasarray“Pessoas ou lugares para ficar perto: [{quem:'pais', onde:'Santana'}, {quem:'escola', onde:'Rua X, 100'}].”
    • modostring“Como vai ao trabalho.”
    • tempo_maxinteger“Minutos aceitáveis até o trabalho.”
    • objetivostring
    • preco_maxnumber
    • quartos_mininteger
    • vagas_mininteger
    • area_minnumber
    • tipostring
    • bairrosarray“Bairros preferidos.”
    • metrostring“'sim' quando metrô perto é importante.”
    • essenciaisarray“O que não abre mão.”
    • limiteinteger
  • vendas_predio

    “Preço pago de verdade num prédio ou casa de São Paulo, pelas vendas registradas no ITBI da Prefeitura desde 2019: m² mediano (corrigido pelo IPCA), número de vendas, faixa de preço das vendas recente…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    3 inputs
    • enderecostring“Rua e número: "Rua Capote Valente, 1307", "Av.”
    • areanumber“Área do imóvel em m² (área construída do IPTU, se souber) para a estimativa.”
    • slugstring“Alternativa ao endereço: o final da URL itbisp.com/predio/<slug>.”
  • vendas_rua

    “Vendas registradas no ITBI numa rua de São Paulo: m² mediano e valor mediano desde 2024, por tipo (apartamento, casa), série por ano desde 2006 (com correção pelo IPCA), bairros por onde passa e os p…”

    Publisher declares: read-only yes · idempotent yes · open-world no

    2 inputs, 1 required
    • ruastringrequired“Nome da rua: "Rua Oscar Freire", "Alameda Olga".”
    • bairrostring“Opcional: bairro, para ruas com nome repetido.”
  • vendas_bairro

    “Preço realmente pago num bairro (distrito) de São Paulo nos últimos 12 meses, pelas vendas registradas no ITBI: m² mediano, variação em 12 meses, valor e área medianos, apartamento e casa separados, …”

    Publisher declares: read-only yes · idempotent yes · open-world no

    1 input, 1 required
    • bairrostringrequired“Bairro ou distrito: "Moema", "Vila Olímpia", "Tatuapé"; "São Paulo" para a cidade.”
  • ranking_bairroson 2 other servers

    “Ranking dos 96 distritos de São Paulo pelo m² realmente pago nos últimos 12 meses (ITBI): mais caros, mais baratos, maior alta ou maior queda em 12 meses, por zona (centro, norte, sul, leste, oeste) …”

    Publisher declares: read-only yes · idempotent yes · open-world no

    4 inputs
    • ordemstring“Ordem.”
    • zonastring“Opcional: zona da cidade.”
    • tipostring“Opcional: só apartamentos ou só casas.”
    • limiteinteger“Quantos bairros (1–96).”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-06.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
89% of 66
Tools with a description
100% of 10
Typical description length
767 characters

The tool set

Counted from the listing

Tools
10
Size of the list
about 5,050 tokens for an agent to load (characters ÷ 4)
Naming
10 of 10 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 10 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-06 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://itbisp.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "itbisp": {
      "url": "https://itbisp.com/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "itbisp": {
      "type": "http",
      "url": "https://itbisp.com/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"itbisp","type":"http","url":"https://itbisp.com/mcp"}'
Claude Code
claude mcp add --transport http itbisp https://itbisp.com/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "itbisp": {
      "type": "streamableHttp",
      "url": "https://itbisp.com/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "itbisp": {
      "httpUrl": "https://itbisp.com/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.itbisp]
url = "https://itbisp.com/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "itbisp": {
      "url": "https://itbisp.com/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://itbisp.com/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint itbisp.com/mcpSession openedmatchesour test · 2026-11-06
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-06
Repository github.com/itbisp/itbisp-pluginOpens publiclymatchesapi.github.com · 2026-11-06

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
com.itbisp · 2 servers
GitHub owner
an organization (itbisp)
Repository
github.com/itbisp/itbisp-plugin
Stars
0
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-11-06; security policy read from GitHub · 2026-11-06.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-06 (security policy 2026-11-06). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about com.itbisp/itbisp

Answered from the data above

Who publishes com.itbisp/itbisp?

The registry ties the namespace com.itbisp to the domain itbisp.com; only its owner can publish under it. Its linked repository is github.com/itbisp/itbisp-plugin; GitHub reports its owner as itbisp, an organization. These are facts from the registry and GitHub, not a rating.

Is com.itbisp/itbisp safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does com.itbisp/itbisp need an API key or sign-in?

It opened a session without any credential on 2026-11-06. The registry entry declares no required credential; no declaration is not a guarantee.

Has com.itbisp/itbisp been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.

Does com.itbisp/itbisp publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of com.itbisp/itbisp?

In github.com/itbisp/itbisp-plugin, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-06
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-11-06, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 922 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 10 tools, 0 resources, 0 prompts.
  4. 3,857 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added in a later update
listed 2026-11-06; not classified yet
Pricing modelAI-classified
pending: added in a later update
the website is not read yet
Programming language
not stated
GitHub detects no source language in this repository (docs-only or empty)
Hosting type
registry · 2026-11-06
MCP capability
tools
our test · 2026-11-06
Transport
streamable HTTP
registry · 2026-11-06
Required credentials
none declared
registry · 2026-11-06 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-06
Lifecycle status
registry · 2026-11-06
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: an organization · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-11-06
Maintenance
api.github.com · 2026-11-06
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-06

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “com.itbisp/itbisp: MCP server record.” Data checked 2026-11-06. https://protocolprobe.com/mcp/servers/com.itbisp/itbisp

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.itbisp/itbisp)](https://protocolprobe.com/mcp/servers/com.itbisp/itbisp)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology