Bollard MCP

io.github.ImDeepaksinghPublished by GitHub account ImDeepaksinghv0.1.4Updated Oct 24, 2026

An AI-powered, safe database access gateway built on the Model Context Protocol (MCP).

VerifiedSTDIODesktop onlyDatabases

Server details

Identifier: io.github.ImDeepaksingh/bollard-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account ImDeepaksingh for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.ImDeepaksingh%2Fbollard-mcp.svg)](https://sourceweft.com/mcp/io.github.ImDeepaksingh%2Fbollard-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Bollard MCP is a local, stdio-based gateway that gives an AI assistant safe, AI-mediated access to databases through the Model Context Protocol.

What you can do: Acts as a database access gateway for an assistant over MCP.
Described as providing safe, AI-powered access to databases.
Runs as a local process on the user's machine over stdio.
No tool list, instructions or README are published, so the exact operations (queries, schema inspection, writes) are not documented in the supplied material.
When to use it: Consider it when you want an assistant to reach a database through a local MCP gateway that emphasizes safe access, rather than connecting the assistant directly to a database client.
Requirements: A local Python environment able to install the bollard-mcp package from PyPI; it runs as a stdio process on the user's machine (desktop only). No authentication, environment variables or headers are declared, but database connection details are presumably needed and are not documented.

Before you install

The server is described as a database access gateway, so it may read or change data in connected databases; the published material does not state which operations are allowed or how they are restricted. No credentials are declared, but database connection details would still be sensitive. Tool behavior is undocumented, so review it before pointing it at production data.

Installation

In SourceWeft

Open Bollard MCP in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.1.4LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.