MCP servers › io.github.nubiia-dev › mcp-borme

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.nubiia-dev/mcp-borme

OpenMercantil (BORME): 37 read-only tools for Spanish company search, officers, sectors and tenders — the publisher's description

9 of 9 record checks metRead-only · tools listed 2026-10-23Topic: data-and-databases · AI-classifiedversion 1.0.2TypeScriptMITstandard input/output37 tools

Summary

io.github.nubiia-dev/mcp-borme is a local MCP server listed in the official MCP registry at version 1.0.2. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 37 tools, 0 resources and 0 prompts.

Record checks

9 of 9 record checks met

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
met: Repository publishes a security policy (SECURITY.md)
met: Package names its licence with a standard (SPDX) identifier
met: The version the registry lists can be installed and is not withdrawn
met: npm package carries build provenance (attestation)
met: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: no download figure available
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?

Key facts

Runs: local package
Transport: standard input/output
Package: npm · listed version current
License: MIT
Dependencies: no known high or critical advisories
Repository: public
Tools: 37
Described as changing data: 0 of 37 toolsAI-classified
Topic: data-and-databasesAI-classified
Last tested: 2026-10-23

Add to your client

Worth knowing before you connect it

Its package is signed and carries a build record naming its source.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-23

Mode

read-only (no tool calls)

Latest version

1.0.2, published 2026-10-22 (registry, as of the 2026-10-23 snapshot)

First listed version

2026-10-22 (earliest version still in the registry; older removed versions would be earlier)

Version history

3 versions listed, all on 2026-10-22; 3 in the 90 days before the 2026-10-23 snapshot.

Most recent 3 versions

1.0.2 · 2026-10-22
1.0.1 · 2026-10-22
1.0.0 · 2026-10-22

(versions still listed in the registry only)

Registry data

snapshot 2026-10-23

Package and repository

checked 2026-10-23

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.0.2 (published 2026-10-22).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

37tools

0resources

0prompts

None of its 37 tools are described as changing anything.

borme_search_companiesreads or searches
“Search Spanish companies (BORME / Registro Mercantil) by name, alias or exact CIF.”
Publisher declares: read-only yes · open-world yes
3 inputs, 1 required
- qstringrequired“Company name (or the start of it), alias or exact CIF, e.g.”
- limitinteger“Results to return, 1-100 (default 10).”
- offsetinteger“Pagination offset, 0-1000 (default 0).”
borme_get_companyreads or searches
“Get the BORME report of one company by slug: identity (name, CIF, legal form, status, aliases), KPIs (number of acts, first/last seen), activity timeline by period, top event types and provinces, the…”
Publisher declares: read-only yes · open-world yes
2 inputs, 1 required
- slugstringrequired“Company slug, e.g.”
- events_limitinteger“How many of the most recent BORME events to include, 0-200 (default 10; 0 = none).”
borme_compare_companiesreads or searches
“Compare exactly two companies side by side using the stable comparison projection (identity, province, CNAE, registry activity).”
Publisher declares: read-only yes · open-world yes
1 input, 1 required
- slugsarrayrequired“Exactly two distinct company slugs to compare, e.g.”
borme_get_company_eventsreads or searches
“List the BORME events (registry acts) of a company for one calendar year, paginated: date, section, province, act type (Nombramientos, Ceses, Ampliación de capital, Disolución...) and the act text.”
Publisher declares: read-only yes · open-world yes
4 inputs, 1 required
- slugstringrequired“Company slug, e.g.”
- yearinteger“Calendar year to list (1900 up to the current year).”
- pageinteger“Page number, starting at 1 (default 1).”
- page_sizeinteger“Events per page, 1-100 (default 20).”
borme_get_company_factsreads or searches
“Structured facts extracted from the BORME acts of a company, grouped by type (appointments, removals, capital changes, mergers, registered-office moves...) with person name and role when applicable, …”
Publisher declares: read-only yes · open-world yes
2 inputs, 1 required
- slugstringrequired“Company slug, e.g.”
- limitinteger“Facts to return, 1-200 (default 20).”
borme_get_company_timelinereads or searches
“Unified chronological timeline of a company combining BORME registry acts and public procurement awards (PLACSP), newest first, each entry with date, category, source, source URL and confidence.”
Publisher declares: read-only yes · open-world yes
2 inputs, 1 required
- slugstringrequired“Company slug, e.g.”
- limitinteger“Most recent timeline entries to return, 1-200 (default 30).”
borme_get_company_officersreads or searches
“Current and historical officers of a company as published in the BORME: administrators, attorneys (apoderados), auditors and similar roles with the date each was first seen.”
Publisher declares: read-only yes · open-world yes
1 input, 1 required
- slugstringrequired“Company slug, e.g.”
borme_get_company_relationshipsreads or searches
“Documented relationships between a company and other entities (officers, domicile, contracts, grants, IP assets, corporate links, mentions), each with source, date, confidence and evidence URL.”
Publisher declares: read-only yes · open-world yes
3 inputs, 1 required
- slugstringrequired“Company slug, e.g.”
- typestring“Only relationships of this type.”
- confidencestring“Only relationships with this confidence level.”
borme_get_company_graphreads or searches
“Corporate graph centred on a company: parents and children (group structure from GLEIF) with counts and coverage notes.”
Publisher declares: read-only yes · open-world yes
2 inputs, 1 required
- slugstringrequired“Company slug, e.g.”
- max_childreninteger“Maximum child entities returned, 1-100 (default 10).”
borme_get_company_activityreads or searches
“Monthly time series of BORME activity for a company (number of registry acts per month, `series: [{period: "2024-05", count: 2}]`).”
Publisher declares: read-only yes · open-world yes
1 input, 1 required
- slugstringrequired“Company slug, e.g.”
borme_get_similar_companiesreads or searches
“Companies in the same province and two-digit CNAE division, ranked by closeness of BORME act count.”
Publisher declares: read-only yes · open-world yes
2 inputs, 1 required
- slugstringrequired“Company slug, e.g.”
- limitinteger“Similar companies to return, 1-20 (default 8).”
borme_get_company_contractsreads or searches
“Public procurement notices (PLACSP, contrataciondelestado.es) linked to the company by CIF: object, buyer, supplier, CPV codes, procedure, typed amounts (budget, estimated, award) and phase.”
Publisher declares: read-only yes · open-world yes
2 inputs, 1 required
- slugstringrequired“Company slug, e.g.”
- limitinteger“Procurement notices to return, 1-100 (default 10).”

Show 25 more tools

borme_get_company_grantsreads or searches
“Public grants and subsidies (BDNS) awarded to the company, in integer cents of the awarded amount (never payments).”
Publisher declares: read-only yes · open-world yes
2 inputs, 1 required
- slugstringrequired“Company slug, e.g.”
- limitinteger“BDNS grants to return, 1-200 (default 20).”
borme_get_company_tedreads or searches
“European public procurement notices (TED) linked to the company NIF: publication number and date, buyer and the official notice URL.”
Publisher declares: read-only yes · open-world yes
2 inputs, 1 required
- slugstringrequired“Company slug, e.g.”
- limitinteger“TED notices to return, 1-100 (default 20).”
borme_get_company_cnmvreads or searches
“Stock-market (CNMV) listing tuple of the company and its most recent regulatory events.”
Publisher declares: read-only yes · open-world yes
2 inputs, 1 required
- slugstringrequired“Company slug, e.g.”
- limitinteger“CNMV events to return, 1-20 (default 5).”
borme_get_company_wikidatareads or searches
“Wikidata identifiers of the company: Q-id, entity URL, ticker and inception date (CC0 subset only; no labels, logos or websites).”
Publisher declares: read-only yes · open-world yes
1 input, 1 required
- slugstringrequired“Company slug, e.g.”
borme_get_company_bdereads or searches
“Banco de España (Central de Balances) sector ratios for the company’s two-digit CNAE: sector benchmarking such as net margin, ROA and ROE.”
Publisher declares: read-only yes · open-world yes
1 input, 1 required
- slugstringrequired“Company slug, e.g.”
borme_get_company_sourcesreads or searches
“Coverage of the four external integrations for a company (BDNS grants, CNMV, TED, Wikidata): which are available or empty, with licence metadata.”
Publisher declares: read-only yes · open-world yes
1 input, 1 required
- slugstringrequired“Company slug, e.g.”
borme_get_daily_summaryreads or searches
“What the BORME published on one date: every registry act grouped by BORME section and province (company, act type, company slug).”
Publisher declares: read-only yes · open-world yes
4 inputs, 1 required
- datestringrequired“Publication date, YYYY-MM-DD.”
- provincestring“Only this province, e.g.”
- sectionstring“BORME section: "1" = Sección Primera (registered acts: constitutions, appointments, capital...), "2" = Sección Segunda (announcements and notices).”
- limitinteger“Maximum acts returned per province, 1-200 (default 10).”
borme_search_personsreads or searches
“Search people mentioned in the BORME by name (usually as officers: administrators, attorneys, auditors).”
Publisher declares: read-only yes · open-world yes
2 inputs, 1 required
- qstringrequired“Person name as written in the BORME, e.g.”
- limitinteger“Results to return, 1-50 (default 10).”
borme_get_personreads or searches
“Documentary report of the BORME mentions of a person slug: the companies and roles where the name appears, with dates.”
Publisher declares: read-only yes · open-world yes
1 input, 1 required
- slugstringrequired“Person slug, e.g.”
borme_get_person_graphreads or searches
“Person-to-company graph built only from BORME mentions of a person slug: the companies connected to that name.”
Publisher declares: read-only yes · open-world yes
2 inputs, 1 required
- slugstringrequired“Person slug, e.g.”
- limitinteger“Companies to return, 1-50 (default 10).”
borme_list_sector_companiesreads or searches
“List companies of a CNAE sector (1-4 characters: section letter, 2-digit division such as "62" for IT programming/consulting, or a longer code), optionally within one province.”
Publisher declares: read-only yes · open-world yes
5 inputs, 1 required
- cnaestringrequired“CNAE-2009 code: a section letter (e.g.”
- limitinteger“Results to return, 1-100 (default 20).”
- offsetinteger“Pagination offset, 0-1000 (default 0).”
- sortstring“Order: acts (most BORME activity, default without province), recent, oldest, name.”
- provincestring“Restrict to a province, e.g.”
borme_get_sector_ratiosreads or searches
“Banco de España (Central de Balances) aggregate ratios for a two-digit CNAE division by year (net margin, ROA, ROE...).”
Publisher declares: read-only yes · open-world yes
1 input, 1 required
- cnaestringrequired“Two-digit CNAE division, e.g.”
borme_get_cnaereads or searches
“Metadata of a CNAE-2009 code: description, level, parent and number of companies.”
Publisher declares: read-only yes · open-world yes
1 input, 1 required
- codestringrequired“CNAE-2009 code: a section letter (e.g.”
borme_get_cnae_treereads or searches
“The CNAE-2009 hierarchy (sections and divisions) with company counts, to look up the right sector code for borme_list_sector_companies or borme_get_sector_ratios.”
Publisher declares: read-only yes · open-world yes
Takes no inputs.
borme_list_legal_normsreads or searches
“Catalogue of the core Spanish mercantile-law norms (Código de Comercio, Ley de Sociedades de Capital, Reglamento del Registro Mercantil, concursal law...) with slug, short name, type and whether in f…”
Publisher declares: read-only yes · open-world yes
Takes no inputs.
borme_get_legal_normreads or searches
“One norm: BOE/ELI identification, its key articles (with a flag for seeded consolidated text) and the BORME act types it governs.”
Publisher declares: read-only yes · open-world yes
1 input, 1 required
- slugstringrequired“Norm slug, e.g.”
borme_get_legal_articlereads or searches
“Consolidated text (`body_html`) of one article of a norm, with its ELI anchor and version date.”
Publisher declares: read-only yes · open-world yes
2 inputs, 2 required
- normstringrequired“Norm slug, e.g.”
- nstringrequired“Article number; a bis/ter suffix is joined with a hyphen, e.g.”
borme_get_act_mapreads or searches
“Which law governs which BORME act type: maps registry act types (constitución, nombramiento, ampliación de capital, disolución, concurso...) to the norm and articles that regulate them.”
Publisher declares: read-only yes · open-world yes
1 input
- actostring“BORME act-type slug to look up one mapping.”
borme_search_tendersreads or searches
“Search Spanish public procurement notices (PLACSP) by object/buyer text, CPV prefix, phase, province, buyer NIF, supplier CIF, open status, amount range (requires amount_kind) and publication dates.”
Publisher declares: read-only yes · open-world yes
14 inputs
- qstring“Terms in the notice object or buyer name (supplier names are NOT searched).”
- cpvstring“CPV code prefix, 2-8 digits (e.g.”
- phasestring“Notice phase: PUB published, PRE prior notice, EV evaluation, ADJ awarded, RES resolved, ANUL annulled.”
- provincestring“Province slug, e.g.”
- buyer_nifstring“NIF of the contracting body (corporate identifiers only).”
- supplier_cifstring“CIF of the awarded supplier (corporate identifiers only).”
- open_onlyboolean“Only notices still open for bids.”
- amount_kindstring“Which monetary concept min_amount_eur/max_amount_eur refer to.”
- min_amount_eurnumber“Minimum amount in EUR.”
- max_amount_eurnumber“Maximum amount in EUR.”
- published_fromstring“Earliest publication date, YYYY-MM-DD.”
- published_tostring“Latest publication date, YYYY-MM-DD.”
- limitinteger“Notices per page, 1-50 (default 10).”
- cursorstring“Opaque cursor from the previous response to get the next page.”
borme_get_tenderreads or searches
“One procurement notice by `key` (from borme_search_tenders): buyer, supplier, lots, CPV codes, procedure, typed amounts and results.”
Publisher declares: read-only yes · open-world yes
1 input, 1 required
- keystringrequired“Notice `key` (stable url_key) from borme_search_tenders, e.g.”
borme_get_tender_statsreads or searches
“Coverage and freshness metrics of the procurement dataset (record counts, geography, documents).”
Publisher declares: read-only yes · open-world yes
Takes no inputs.
borme_list_tender_suppliersreads or searches
“Corporate suppliers ranked by number of public contract awards (only suppliers matched to a company by CIF; natural persons omitted; no monetary totals).”
Publisher declares: read-only yes · open-world yes
1 input
- limitinteger“Suppliers to return, 1-50 (default 10).”
borme_get_healthreads or searches
“OpenMercantil service status and BORME freshness: `status` (ok/stale), `latest_borme_processed` (last bulletin date loaded), approximate company and event counts and degraded flags.”
Publisher declares: read-only yes · open-world yes
Takes no inputs.
borme_get_statsreads or searches
“Size of the public dataset: number of legal entities published and an approximate count of person mentions, with the build timestamp.”
Publisher declares: read-only yes · open-world yes
Takes no inputs.
borme_get_sources_freshnessreads or searches
“Per-source freshness map (BORME, PLACSP, BDNS, CNMV, annual accounts...): last update time and status of each public source behind the data, including a global label.”
Publisher declares: read-only yes · open-world yes
Takes no inputs.

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-10-23.

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

Says what the tool does: 100% of 37 tools
Says what it returns: 100% of 37 tools
States limits, defaults or errors: 100% of 18 tools
Says when to use it: 100% of 16 tools
Items covered per tool: 4.0 of 4 on average

Counted from the listing

Parameters with a description: 100% of 70
Tools with a description: 100% of 37
Typical description length: 287 characters

The tool set

Counted from the listing

Tools: 37
Size of the list: about 7,366 tokens for an agent to load (characters ÷ 4)
Naming: 37 of 37 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 37 of 37 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 npm package @nubiia/mcp-borme

Our sandbox started this package on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)

{
  "mcpServers": {
    "mcp-borme": {
      "command": "npx",
      "args": [
        "-y",
        "@nubiia/mcp-borme@1.0.2"
      ]
    }
  }
}

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "mcp-borme": {
      "command": "npx",
      "args": [
        "-y",
        "@nubiia/mcp-borme@1.0.2"
      ]
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "mcp-borme": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@nubiia/mcp-borme@1.0.2"
      ]
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"mcp-borme","type":"stdio","command":"npx","args":["-y","@nubiia/mcp-borme@1.0.2"]}'

Claude Code

claude mcp add --transport stdio mcp-borme -- npx -y @nubiia/mcp-borme@1.0.2

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 -- npx -y @nubiia/mcp-borme@1.0.2

Optional settings the entry also lists (left out above): OPENMERCANTIL_API_KEY, OPENMERCANTIL_MAX_REQUESTS_PER_MINUTE, OPENMERCANTIL_MAX_RESPONSE_CHARS.
This runs the publisher's code on your machine (npx). Read its README first.
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). 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.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists: 1.0.2
Latest stable: 1.0.2
Status: current
Withdrawn: no

Source: registry.npmjs.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

Counted in the full dependency tree as resolved on 2026-10-23 (npm audit). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity: sha512-XjPgYbaYA6zI3MArh…
Signature: signed and attested
License: MIT

Source: the package registry · 2026-10-23.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Published package can be started	Started and answered	matches	our test · 2026-10-23
Version 1.0.2 on npm	Exists and can be installed	matches	npm · 2026-10-23
Repository github.com/nubiia-dev/mcp-borme	Opens publicly	matches	api.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

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

Namespace: io.github.nubiia-dev · 6 servers
GitHub owner: an organization (nubiia-dev)
Build record: signed and attested

Repository: github.com/nubiia-dev/mcp-borme
Stars: 0
Repository age: 0–30 days
Last push: 0–30 days ago
Archived: no
Security policy: SECURITY.md

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

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

9 of 9 record checks met

Not ranked by downloads: no download figure available
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.
MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
MetPackage names its licence with a standard (SPDX) identifierMIT
MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
Metnpm package carries build provenance (attestation)Signed, with a build attestation naming the source and workflow.
MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. 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. How each check works · Leaderboards

Common questions about io.github.nubiia-dev/mcp-borme

Answered from the data above

Is io.github.nubiia-dev/mcp-borme safe to install?

We do not rate servers as safe or unsafe. 9 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its npm package carries a build-provenance attestation that names its source repository and build workflow. Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.nubiia-dev/mcp-borme been security tested?

Partly. 2 of the 12 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.github.nubiia-dev/mcp-borme do?

It lists 37 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.nubiia-dev/mcp-borme change or delete data?

None of its 37 tools is described as changing anything (our AI model's reading of the descriptions; nobody checked it by hand). We did not call any tool.

Does io.github.nubiia-dev/mcp-borme publish a security policy?

Yes: its repository has a public security policy (github.com/nubiia-dev/mcp-borme/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Is the listed version current?

Yes. The registry lists 1.0.2, the latest stable release on npm.

Where is the source code of io.github.nubiia-dev/mcp-borme?

In github.com/nubiia-dev/mcp-borme, 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.

Similar servers

Same topic · AI-read

io.github.t8y2/dbxalso has tools that reads or searchescompare with this one
agency.ottobot/contractor-license-changesContractor Licence Changesalso has tools that reads or searchescompare with this one
agency.ottobot/licensed-house-paintersLicensed House Paintersalso has tools that reads or searchescompare with this one
io.github.revolist/revogrid-mcpRevoGrid DataGrid MCPalso has tools that reads or searchescompare with this one
io.github.chrisryugj/korean-law-mcpKorean Law MCPalso has tools that reads or searchescompare with this one
io.github.timescale/pg-aiguidealso has tools that reads or searchescompare with this one

Active servers whose topic is also “data-and-databases” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

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 (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not applicable
Consent handling: not applicable
Sign-in metadata: not applicable

2 exercised10 not run (reason given)6 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 12 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised

Not run, with the reason · 10

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
4Secret leak
canary-leakPlants 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
ssrfChecks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
8Model requests
samplingChecks 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-dataChecks 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-boundaryChecks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
11Log leaks
logging-side-channelChecks 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-hidingChecks 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

Does not apply to this server · 6

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, 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.

0 msStarted the published package in an isolated sandbox (read-only mode)
2,989 msConnected after 0 redirects.
Read the inventory: 37 tools, 0 resources, 0 prompts.
13,604 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

data-and-databases

AI-classified · 2026-10-23

Pricing modelAI-classified

not checked

no website in the registry entry

Programming language

TypeScript

api.github.com · 2026-10-23

Hosting type

local package

registry · 2026-10-23

MCP capability

tools

our test · 2026-10-23

Transport

standard input/output

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

npm

registry · 2026-10-23

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

permissive

package registry · 2026-10-23

Integrity hash

declared (sri)

package registry · 2026-10-23

Signature / provenance

signed and attested

package registry · 2026-10-23

Dependency advisories

none known

npm audit · 2026-10-23

Popularity

not known (our limit)

Our lookup failed (network error, timeout or rate limit). This is our limit, not the server's.

Publisher signals

owner: an organization · repository age: 0–30 days · stars: 0–9 · build record: signed and attested

api.github.com · 2026-10-23

Maintenance

active

api.github.com · 2026-10-23

Environment

your machine

where it runs, from the hosting type

“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. “io.github.nubiia-dev/mcp-borme: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.nubiia-dev/mcp-borme

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](https://protocolprobe.com/api/v1/badge/io.github.nubiia-dev/mcp-borme)](https://protocolprobe.com/mcp/servers/io.github.nubiia-dev/mcp-borme)

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