buc.ci is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.

This server runs the snac software and there is no automatic sign-up process.

Admin email
abucci@bucci.onl
Admin account
@abucci@buc.ci

Search results for tag #mcp

AodeRelay boosted

[?]RelayShieldAdmin Β» 🌐
@relayshieldadmin@infosec.exchange

New reference implementation shipped today: middleware that gates AI agents from connecting to unfamiliar MCP servers behind a mandatory security check. It is not an optional tool call the agent is free to skip.

github.com/nzdsf2-gif/relayshi

    AodeRelay boosted

    [?]CyberSecureFox :loading: Β» 🤖 🌐
    @cybersecurefox@infosec.exchange

    AodeRelay boosted

    [?]Daily CyberSecurity Β» 🌐
    @DailyCyberSecurity@infosec.exchange

    New research on AI connector risk: 37% of Claude and ChatGPT connectors changed in six weeks, quietly gaining write access and new tools.

    meterpreter.org/ai-connector-r

      AodeRelay boosted

      [?]Ric Harvey πŸ‡ͺπŸ‡ΊπŸŒπŸ’š Β» 🌐
      @Ric@mastodon.squarecows.com

      Friends, Romans and Country-folk, lend me your stars.

      I’m trying to get my open source project picked up by more and more folks, a bigger community more testing and commits which in turn means a better product, its a great flywheel effect. One way to help me is to star the repository and you have two options:

      - codeberg where the source lives: codeberg.org/ric_harvey/omnimem
      - GitHub to help discoverability: github.com/richarvey/OmniMem

        AodeRelay boosted

        [?]Ric Harvey πŸ‡ͺπŸ‡ΊπŸŒπŸ’š Β» 🌐
        @Ric@mastodon.squarecows.com

        OmniMem v5 is out 🧠

        Self-hosted persistent memory for any AI agent.

        Big jump from v3, tested hard internally:

        πŸ”— Connect claude.ai from the browser (OAuth 2.1, no proxy)
        ⚑ Non-blocking ingest + faster recall
        πŸ”’ Security pass: constant-time tokens, fail-closed, DoS caps, brute-force protection
        🧩 Smarter recall: fact extraction, temporal queries, preferences

        Compose πŸ‘‡

        omnimem.org

          AodeRelay boosted

          [?]Self-Hosted Feed Β» 🤖 🌐
          @selfhosted_bot@fd.mrmave.work

          🌐 mcpjungle/MCPJungle

          One place to manage & connect to all your MCP servers

          Unifies and manages multiple MCP servers behind a single endpoint for AI clients like Claude or Cursor

          ⭐ Stars: 1129
          πŸ“… Last Update: Jun 30, 2026

          github.com/mcpjungle/MCPJungle

            AodeRelay boosted

            [?]Ric Harvey πŸ‡ͺπŸ‡ΊπŸŒπŸ’š Β» 🌐
            @Ric@mastodon.squarecows.com

            πŸš€ forgejo-mcp v0.1.7 is out!

            It's an MCP server that lets Claude (and any MCP client) drive your Forgejo/Gitea instance β€” 100+ tools for repos, issues, PRs, orgs & users.

            This release squashes a sneaky bug class: merging PRs, updating branches & rendering markdown all *worked* but reported errors. Plus create_team fixes & runtime version reporting.

            πŸ“¦ npm: @ric_/forgejo-mcp

            πŸ’» Source: code.squarecows.com/SquareCows

            conceptual image showing AI and human brain working together on a coding and git workflow

            Alt...conceptual image showing AI and human brain working together on a coding and git workflow

              AodeRelay boosted

              [?]Dan ⁂ Β» 🌐
              @FRYTG@beoriginal.social

              how long until they put ads in servers?

                AodeRelay boosted

                [?]Self-Hosted Feed Β» 🤖 🌐
                @selfhosted_bot@fd.mrmave.work

                πŸš€ metatool-ai/metamcp

                MCP Aggregator, Orchestrator, Middleware, Gateway in one docker

                Unifies multiple MCP servers into a single endpoint with dynamic aggregation, middleware support and namespace-based tool management via Docker

                ⭐ Stars: 2390
                πŸ“… Last Update: Jun 08, 2026

                github.com/metatool-ai/metamcp

                  AodeRelay boosted

                  [?]Kettwachsler Β» 🌐
                  @phpmacher@sueden.social

                  hat jetzt also einen Server an den Start gebracht.

                  Und damit der Sinn ergibt, hat man gleichzeitig 3rd Party Tools den -Zugriff entzogen.

                  Vielleicht sollte Strava die Sinnhaftigkeit des Plans neu bewerten.

                    8 ★ 6 ↺

                    [?]Anthony Β» 🌐
                    @abucci@buc.ci

                    This is a bit niche, but today I noticed the "Local REST API" plugin for Obsidian is now the "Local REST API with MCP" plugin. MCP, short for Model Context Protocol, is an LLM coding agent thing. "Local REST API" previously served a REST endpoint that let other apps, notably browser plugins, interact with your Obsidian vault. It's useful: for instance, there's a browser plugin that allows you to download a copy of any web page and stash it in your vault using the REST API this plugin serves.

                    I created an issue on the plugin's GitHub about removing the MCP functionality into a separate plugin, and the maintainer immediately converted it into a discussion, which is here: https://github.com/coddingtonbear/obsidian-local-rest-api/discussions/272

                    I'm getting the impression from all the LLM-related discussions and commits that this is a lost cause and I'll probably have to fork this plugin if I want an MCP-free version of it. Looks like they took up slop coding earlier this year too, which is another area of concern.


                      [?]Bill Β» 🌐
                      @Sempf@infosec.exchange

                      El Reg picked this OX story up. They have some pretty good plain-english examples of why this is considered by many a bad thing.

                      theregister.com/2026/04/16/ant

                        [?]Bill Β» 🌐
                        @Sempf@infosec.exchange

                        A design flaw in the MCP protocol. Whoda thunk. Honestly even back when they were first discussing MCP in 2024 I worried about that. Supply chain is enough of a mess, now this?

                        securityweek.com/by-design-fla