Eustore

io.github.AIBOLLINGMOPublished by GitHub account AIBOLLINGMOv0.2.2Updated Oct 24, 2026

S3-compatible European object storage for AI agents. GDPR-compliant, EU-hosted, crypto payments.

VerifiedSTDIODesktop onlyFiles & Storage

Overview

AI-generated overview

Eustore is a local MCP server that gives an AI assistant S3-compatible European object storage, described as GDPR-compliant, EU-hosted and payable in crypto.

What you can do
Connect an assistant to S3-compatible object storage hosted in the EU, aimed at AI agent workloads. The listing describes the service as GDPR-compliant and EU-hosted, with crypto payments. No individual tools are listed, so the exact operations an assistant can perform are not documented here.
When to use it
Consider it when you want an assistant to work with object storage that stays in the EU and you care about GDPR compliance or crypto payment. Because no tools are listed, confirm the available operations before relying on it.
Requirements
Runs as a local process installed from the PyPI package eustore over stdio, so a Python environment is needed. The manifest declares no authentication, environment variables or headers, but an S3-compatible storage account and credentials are likely needed in practice; verify this with the provider.
Before you install
The listing mentions crypto payments, so using the service may involve spending money and handling wallet or payment details. No credentials are declared in the manifest, yet storage access normally requires keys; check how they are supplied. Data is stored with a third-party EU host, so review where it goes and under what terms.

Installation

In SourceWeft

  1. Open Eustore in the dashboard and add it to a workspace.
  2. 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.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

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

Version history

1
  1. v0.2.2LatestSep 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.