Live and recent posts from across the Fediverse tagged #model-context-protocol, aggregated by home.social.
Building an MCP server? A model reads your error messages, and it'll act on whatever they say.
A 429 from PageSpeed with no key is the shared anonymous pool, routinely spent by midday, and says nothing about the page. With a key it's your own quota. A 403 is usually a referrer-restricted key, refused every time because a program has no referring page.
Hand a model a bare status code and it can go off changing a site that was fine all along.
Shield hires ex-HSBC surveillance chief to shape AI strategy
RegTech firm Shield has appointed Michelle Clark, formerly global head of communications surveillance capability at HSBC, as global…
#EuropeSays #Britain #Europe #EU #HSBC #agenticAI #ai #bankingtechnology #communicationssurveillance #compliance #DCGA #EranNoam #financialcrime #MichelleClark #ModelContextProtocol #RegTech #riskgovernance #sHIELD
https://www.europesays.com/britain/143947/
https://www.europesays.com/britain/143947/ Shield hires ex-HSBC surveillance chief to shape AI strategy #AgenticAI #ai #BankingTechnology #CommunicationsSurveillance #compliance #DCGA #EranNoam #FinancialCrime #HSBC #MichelleClark #ModelContextProtocol #RegTech #RiskGovernance #sHIELD
CVE Alert: CVE-2026-108714 - modelcontextprotocol - kotlin-sdk - https://www.redpacketsecurity.com/cve-alert-cve-2026-108714-modelcontextprotocol-kotlin-sdk/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-108714 #modelcontextprotocol #kotlin-sdk
#AWS open-sourced Pizza Bot - a self-hosted app for running AI agents in the background.
Agents can schedule tasks, delegate work, respond to webhooks, and pause for human approval.
🔗 Details here: https://www.infoq.com/news/2026/10/pizza-bot-ai-agents/
#InfoQ #AI #AIAgents #AIcodingAgents #ModelContextProtocol #opensource
----------------
🎯 AI
===================
OX Security published a research report covering 15,465 published MCP servers and 5,095 unique hostnames. The short version: the Model Context Protocol ecosystem has no native governance for data residency, domain lifecycle, or permission persistence, and a prompt injection test against Claude Code succeeded under one specific model configuration.
🔹 Research Scope
The team enumerated 15,465 published MCP servers and resolved 5,095 unique hostnames behind them. Coverage falls into three buckets: geolocation of resolved infrastructure, domain registration and resolution state, and servers sitting on consumer-grade network paths. A separate test checked whether a granted permission in Claude Code survives a subsequent prompt injection.
🔹 Key Findings
• Data residency: 15.6% of analyzed hostnames resolved to infrastructure outside the US, including infrastructure in China and Russia. MCP currently provides no native protocol mechanism to enforce where connected tools run or where data is processed, so residency enforcement is left entirely to the deploying side.
• Consumer infrastructure: 0.45% of hostnames were associated with home networks or consumer tunneling tools. Agent workflows can therefore reach endpoints that never crossed corporate network controls, which breaks standard visibility assumptions.
• Domain takeover: 2.3% of hostnames failed to resolve. Six of the underlying domains are unregistered and available for around $4 per year. If MCP clients or workflows keep trusting and calling those names, whoever registers them can stand up a matching server and inherit the traffic. It is the classic dead-domain takeover problem, showing up one layer above the web.
• Permission persistence: In testing against Claude Code with Haiku 3.5, a single 'Always-Allow' grant was enough for a malicious MCP server to follow up with prompt injection and execute privileged file access without another user confirmation. The same attack did not succeed against Opus 4.6 or 4.7, so the result appears model-dependent, and it comes from the vendor's own testing.
🔹 Analysis
The takeover finding is the mechanically simplest one. Published MCP server listings operate as a de facto trust directory, but nothing in the protocol verifies that a hostname still belongs to its original operator. A handful of $4 registrations is close to the cheapest infrastructure acquisition available, and the public summary describes no pinning or allowlist control that would stop it.
The residency numbers matter mostly because agent workflows call these hostnames automatically. If a connected tool resolves to infrastructure in a jurisdiction the organization never approved, nothing in MCP surfaces that to the user or the admin at connection time.
The Claude Code result deserves the most caution. Permission scoping, exact prompts, and injection payloads are not described in the public summary, and the gap between Haiku 3.5 and Opus 4.6/4.7 has no published root cause. It is a reasonable hypothesis that smaller models tolerate injected instructions over an existing allow, but that is a hypothesis, not a confirmed mechanism.
🔹 Operational Notes
Translating findings into checks: inventory which MCP hostnames your clients actually resolve, geolocate them, flag anything dead or sitting on consumer tunneling, and review how client-side 'Always-Allow' grants are scoped. None of that is enforced by MCP itself today. The report does not publish a defense list in the summary, so these are the checks its own findings point at.
🔹 Limitations
This is vendor research from OX Security. The public summary omits the full methodology, the hostname list, and any detection coverage. The percentages should be treated as indicative until reproduced, and the prompt injection result has not been independently tested.
🔹 MCP #AISecurity #PromptInjection #ModelContextProtocol #SupplyChain
🔗 Source: https://www.ox.security/ebooks/15465-mcp-servers-0-governance/
MCP Servers Expose Enterprises to Unvetted Risks
Thousands of enterprises are unknowingly rolling out MCP servers without proper oversight, leaving them vulnerable to unchecked risks. A recent analysis of 15,465 publicly indexed MCP servers revealed a staggering lack of centralized governance, with many deployments happening fast but without any policing.
#McpServers #EmergingThreats #AiSecurity #ModelContextProtocol #SupplyChain
https://www.europesays.com/britain/136151/ Barclays expands Anthropic’s Claude Code to support software development and legacy modernisation #AgentPay #AgentSafety #AgentInitiatedPayments #AgenticAI #AIGovernance #Barclays #ClaudeCode #CloudMigration #ConsumerProtection #CoreBankingMigration #CostToIncomeRatio #LegacyModernisation #ModelContextProtocol #OperationalRiskFramework #ReconciliationAutomation #TraderCommunications
CVE Alert: CVE-2026-104120 - modelcontextprotocol - mcp-server-fetch - https://www.redpacketsecurity.com/cve-alert-cve-2026-104120-modelcontextprotocol-mcp-server-fetch/
#OSINT #ThreatIntel #CyberSecurity #cve-2026-104120 #modelcontextprotocol #mcp-server-fetch
The latest #ModelContextProtocol spec removes protocol-level sessions, sticky sessions, and session storage for remote MCP servers.
The result? Independent request routing and simpler horizontal scaling - with state, retries, observability, and idempotency pushed to other layers.
Read more: https://www.infoq.com/news/2026/09/aws-stateless-mcp/
HSBC unveils new digital solution to simplify transaction banking
Source: HSBC HSBC has today announced the next phase of its digital banking transformation with the launch of…
#EuropeSays #Britain #Europe #EU #HSBC #ai #aisolutions #API #APIs #banking #Data #DigitalBanking #ModelContextProtocol #technology #transactionbanking
https://www.europesays.com/britain/133675/
https://www.europesays.com/britain/133675/ HSBC unveils new digital solution to simplify transaction banking #ai #AiSolutions #API #APIs #banking #Data #DigitalBanking #HSBC #ModelContextProtocol #technology #TransactionBanking
AI Deployments Expose Governance Gaps via MCP Servers
A recent analysis of 5,095 unique MCP hostnames revealed a staggering 16% were accessible outside the US, including in high-risk countries like Russia and China, highlighting a glaring governance gap in AI deployments. This oversight allows AI integrations to bypass enterprise controls, creating a silent security risk.
#AiGovernance #McpServers #EmergingThreats #ModelContextProtocol #ArtificialIntelligence
https://www.tkhunt.com/2570860/ エージェント型AIとMCP ── ツール利用・メモリ・マルチエージェント【AWS AI Practitioner（AIF-C01）対策】｜ #ひとりLT #052 #AgentCoreGateway #AgenticAi #AI #AIPractitioner #AIF #AIFC01 #AIエージェント #AmazonBedrockAgentCore #ArtificialIntelligence #AWS #AWSCertifiedAIPractitioner #AWS認定 #AWS資格 #IT #LT #MCP #ModelContextProtocol #エージェント型AI #ツール利用 #ひとりLT #プログラミング #マルチエージェント #人工知能 #生成AI #試験対策
https://www.europesays.com/ie/705804/ Stateless MCP Removes Session Affinity Requirements for AWS Server Deployments #AI #AIArchitecture #Architecture&Design #aws #AWSLambda #AwsStatelessMcp #Deployment #Development #DistributedSystems #Éire #Frameworks #IE #Ireland #LoadBalancing #Microservices #ML&DataEngineering #ModelContextProtocol(MCP) #Observability #OpenTelemetry #scaling #Serverless #Technology #W3C
En Tributi hemos estado construyendo un servidor MCP remoto para elaborar la declaración de renta de persona natural (Colombia, año gravable 2025) desde un agente conversacional.
Se agrega como conector personalizado en Claude (recomendado), en ChatGPT o en clientes MCP como Gemini / Antigravity. Autorizas con tu cuenta de Tributi y el agente, Clara, guía el proceso.
reimbursement.INFO öffnet Fachdaten für ChatGPT und weitere KI-Assistenten
Neue MCP-Schnittstelle soll Erstattungs-, Fall- und Strukturdaten direkt mit internen Klinikdaten verknüpfen – Beta-Phase startet für Premium-Nutzer
#ChatGPT #Erstattungsdaten #KrankenhausIT #Krankenhausdaten #KünstlicheIntelligenz #MCP #Medizincontrolling #ModelContextProtocol
#Google :google: warnt: KI-Agenten im #SmartHome können sich unerwünscht verhalten | heise online https://www.heise.de/news/Google-Home-KI-Agenten-wie-Claude-duerfen-jetzt-das-Smart-Home-steuern-11456074.html #ArtificialIntelligence #AI #MCP #ModelContextProtocol #IoT #InternetOfThings #InternetDerDinge #Datenschutz #privacy #AIagent #AIagents
Infinito.Nexus 14.0: Turn Local AI into a Secure Digital Workforce
In Short Infinito.Nexus 14.0 enables companies to operate AI on their own infrastructure, connect it securely to existing business applications and deploy AI agents such as Hermes and OpenClaw as virtual employees. Sensitive information can be processed by local models, while optional connections to OpenAI, Anthropic and OpenRouter provide access to external frontier models when greater capabilities are needed. Companies decide which data may leave their infrastructure, which tools an agent can use and which actions remain restricted. Infinito.Nexus 14.0 brings models, enterprise applications and autonomous agents together in one controlled infrastructure. Organizations can now combine local AI for sensitive data with external frontier models and deploy agents such as Hermes and OpenClaw as isolated virtual employees. Generative AI has already changed how employees search, write, analyze and develop. But most organizations still face an uncomfortable choice: either send business data to an external AI provider or accept the operational complexity of building a local AI platform from scratch. Infinito.Nexus 14.0 introduces a third option: a hybrid AI architecture in which organizations decide where every workload runs. Sensitive prompts can be processed by local models through Ollama or LM Studio. Tasks that require the capabilities of frontier models can be routed to OpenAI, Anthropic or OpenRouter. Applications and agents use one centrally managed gateway instead of implementing separate provider integrations. The result is not merely another enterprise chatbot. Version 14.0 provides the foundation for a secure digital workforce. […]
https://www.europesays.com/ie/694614/ Splunk Open Sources Token Meter Tool for Application Developers #AgentMonitoring #AgenticAi #AIBudgets #AICodingAgents #AICostManagement #AICosts #AIDevelopment #AIFinOps #AIObservability #ClaudeCode #Codex #CodingAssistants #cursor #DeveloperProductivity #DeveloperTools #devops #Éire #IE #Ireland #Kiro #mcp #ModelContextProtocol #ModelCosts #OpenCode #pi #Splunk #Technology #TokenConsumption #TokenMeter #TokenUsage
https://www.europesays.com/ro/303130/ Google abia a înlocuit Assistant cu Gemini, iar acum lasă Claude și alți agenți AI să-ți controleze casa #ai #Antigravity #CasaInteligenta #claude #gemini #google #GoogleAssistant #GoogleHome #HomeMCP #ModelContextProtocol #OpenClaw #RO #Română #Romania #Romanian #Technology #tehnologie
Google Home Opens Up to External AI Agents via the Model Context Protocol
Google is introducing an MCP server for Google Home, enabling AI assistants such as Claude or ChatGPT to control connected smart home devices and analyze event data.
#SmartHome #ArtificialIntelligence #GoogleHome #Matter #ModelContextProtocol
Google Home öffnet sich für externe KI-Agenten über das Model Context Protocol
Google stellt einen MCP-Server für Google Home bereit. Damit können KI-Assistenten wie Claude oder ChatGPT vernetzte Haushaltsgeräte steuern und Ereignisdaten auswerten.
#SmartHome #GoogleHome #GoogleNest #KnstlicheIntelligenz #Matter #ModelContextProtocol
FYI: Explaining MCP: MCP, the Model Context Protocol, is the open standard letting AI agents discover and call external tools. Mechanics, origins, and its spread across ad tech. https://ppc.land/mcp/ #MCP #ModelContextProtocol #AI #AdTech #TechInnovation
The 2026-07-28 spec - now the current official version, released on July 28, 2026, and superseding 2025-11-25 - throws that model out. https://hackernoon.com/mcp-just-went-stateless-what-the-2026-spec-actually-changes-for-your-servers #modelcontextprotocol
ReleasePad Launches MCP Server So AI Agents Can Draft, Publish and Measure Product Changelogs
ReleasePad ReleasePad MIAMI, Sept. 14, 2026 (GLOBE NEWSWIRE) — ReleasePad, a Changelog Tool, today launched a Model Context…
#NewsBeep #News #Technology #AIassistants #CA #Canada #ModelContextProtocol #releasenote #Releasenotes
https://www.newsbeep.com/ca/895735/
https://www.europesays.com/ie/688451/ ReleasePad Launches MCP Server So AI Agents Can Draft, Publish and Measure Product Changelogs #AIAssistants #Éire #IE #Ireland #ModelContextProtocol #ReleaseNote #ReleaseNotes #Technology
ICYMI: Explaining MCP: MCP, the Model Context Protocol, is the open standard letting AI agents discover and call external tools. Mechanics, origins, and its spread across ad tech. https://ppc.land/mcp/ #AI #MachineLearning #AdTech #ModelContextProtocol #Innovation
Shinhan Card Launches Industry-First AI Chat Service
[Shinhan Card] Shinhan Card is launching a service that lets users get card recommendations and apply for cards…
#EuropeSays #Korea #KR #Kakao #AIfinancialservices #cardrecommendation #ChatGPTforKakao #KakaoTools #Koreancardissuers #ModelContextProtocol #ShinhanCard
https://www.europesays.com/korea/152599/
Probing a random sample of 400 npm/stdio servers from the 24,135 in the MCP registry over the wire showed only 48.8% even complete basic initialization. Tool-use benchmarks routinely repair broken servers before testing. Production deployments do not get that luxury.
Today is all about MCP Live! 🚀
The MCP 2.0 changes bring a major shift toward a stateless protocol, improved extensibility, and new patterns for agent interactions. Really excited to see how the growing extensions ecosystem will shape the next generation of AI-powered applications.
More details: https://modelcontextprotocol.io/
#MCPLive #ModelContextProtocol #MCP #AzureTracks #AgenticAI #AIEngineering
Reminder that #modelcontextprotocol is just http and json in a trenchcoat.. and they are still messing with it. Remembering the dark ages (months) between 2025-11-25 and 2026-07-08 when we were in the wilderness..
curlhub Now Speaks MCP: Correctly Quoted curl for AI Agents
Models write curl constantly and get the quoting wrong, and it fails silently. curlhub is now an MCP server that builds the command by construction instead of by guesswork.
https://curlhub.sh/news/curlhub-mcp-server-correct-curl-for-ai-agents
Webshot Now Speaks MCP: Screenshots as a Tool for AI Agents
Webshot is now an MCP server. An AI assistant can render any public URL and inspect the result without you pasting anything — and the same JSON is available over plain HTTP with one extra parameter.
https://webshot.site/blog/webshot-mcp-server-screenshots-for-ai-agents
https://www.europesays.com/ro/283412/ Sonos își deschide boxele către ChatGPT și alți asistenți AI, fără să aleagă un ecosistem anume #BoxeInteligente #ChatGPT #InteligentaArtificiala #MCP #ModelContextProtocol #RO #Română #Romania #Romanian #SmartHome #sonos #Sonos27 #SonosAce #SonosMove2 #Technology #tehnologie
I made a simple #ModelContextProtocol server that contains an offline copy of the #Debian Policy with a search tool and a standards upgrade checklist tool that both help to maintain Debian packages, remove the need for web searches and non-authorative text as well as run locally on the maintainer's computer of choice.
You can grab ready to use snap at http://snapcraft.io/debot or build from source.
From the .NET blog...
In case you missed it earlier...
How Uno Platform uses .NET, MCP, and AI to build high quality apps
https://devblogs.microsoft.com/dotnet/how-uno-platform-uses-dotnet-mcp-ai-to-build-high-quality-apps/ #dotnet #AI #DeveloperStories #XAML #AIagents #GitHubCopilot #MCP #ModelContextProtocol #SkiaSharp #UnoPlatform
From the .NET blog...
How Uno Platform uses .NET, MCP, and AI to build high quality apps
https://devblogs.microsoft.com/dotnet/how-uno-platform-uses-dotnet-mcp-ai-to-build-high-quality-apps/ #dotnet #AI #DeveloperStories #XAML #AIagents #GitHubCopilot #MCP #ModelContextProtocol #SkiaSharp #UnoPlatform
https://www.tkhunt.com/2519087/ 【概要】Snowflake CoWork｜UI開発なしで動く対話型AIエージェント #AgenticAi #AI #AIエージェント #AIデータクラウド #ArtificialIntelligence #ModelContextProtocol #snowflake #エージェント型AI #データエンジニアリング #データ活用 #人工知能 #生成AI #自律型AI
Status Report 2026-08-29 and Outlook for September\October 2026
Today we released Infinito.Nexus 13.0.0 with integrated Tor and .onion support. The release notes you will find here and the blog article about the functionality here.
https://www.youtube.com/watch?v=6czcc1gZ7Ak
This feature didn’t have a high business value, anyhow it allowed to clean up the architectural base for everything what comes now.
Anyhow here I want to give you insights into the Infinito.Nexus project and what’s planed.
Infinito.Nexus Core >= 14.0.0a
Email Software Replacement
From the current point of view at least 2 Major releases will arrive in the next month. The first one is the substitution of Mailu by Stalwart, implemented by Alejandro. This is necessary due to the deprecation of Mailu itself.
https://www.youtube.com/watch?v=lJqtQG6lmc4&t=24s
The release state and the related discussion you can follow here .
AI Integration
The other release is, let’s call it the “AI” release. Long story short:
Infinito.Nexus will allow the use and the integration of AI, local and external models in almost all SaaS applications. It will also allow the Integration in Software via MCP.
Lite LLM
All applications which support AI like OpenWebUI, WordPress, Nextcloud, Matrix etc. will have an inteface which connects to an Lite LLM Gateway. The Lite LLM Gateway will allow the use of local models like Qwen, Gema etc. Besides this it’s possible to integrate OpenRouter or e.g. Anthropic or OpenAI etc.
https://www.youtube.com/watch?v=nQCOTzS5oU0
So enterprises which use Infinito.Nexus can decide by themself if they prefer to use their local AI and models and keep everything on their infrastructure or if they prefer to use external proprietary models.
The customer has the choice about the level of data sovereignty they want to keep and the infrastructure which they want to setup.
MCP
https://youtu.be/eur8dUO9mvE?si=vTJW30tCZz2ZdUD6
The second AI related topic is the integration of MCP into all kind of applications.
It’s already in progress since a few weeks and my agents are working on this 24h. Relevant in this context is the security aspect.
Similar to the Infinito.Nexus 13.0.0 TOR Release, the MCP Release will have a high impact on security and MUST due to this reason be declared as PoC. Why?
In my understanding you can’t easily implement RBAC into MCP clients.
So my current implementation works like this;
You have per Infinito.Nexus application two MCP RBAC groups:
If one is part of the reader group they can read all of the application data via Open WebUI and if one is part of the Writer group they can modify all of the data via Open WebUI.
https://www.youtube.com/watch?v=VNPMl8oOzHU
This is off course highly dangerous. It may makes sense to give people reading rights, but in consequence this means that they can access and utilize all of the users data via an AI.
We don’t have to talk about that this goes against any kind of data protection regulations and is a hard invasion into the privacy of your platform users.
Anyhow there are scenarios in which it may makes sense.
E.g. let’s assume you’re fully virtual organisation and you don’t have humans employed, but instead on your Infinito.Nexus platform just bot and agents account exist;
In this scenario if you have reading and writing rights you’re de facto in the “God Mode” in which you can instantly see what your agents are doing.
An example is if you use it e.g. with AgentCrew (WiP). You can orchestrate Agents and AI on a way you can’t imagine. AgentCrew I will explain in the next paragraphs.
Also if it’s in the current state absolutely not recommended to activate the MCP functionality, it doesn’t mean it must be like this in the future. Like I said currently it’s seen as PoC and the full MCP compatible RBAC implementation isn’t impossible, it just will take a lot of human resources, because for every part of the Infinito.Nexus software we need humans which take responsibility for the code.
“We stay in the loop” – We aren’t controlled by AI, instead we’re the masters. In consequenz this means that the full RBAC MCP will be implemented as soon as we have sufficient customers which request it and developers which can manage it intellectually to implement a clean architectural solution.
i18n
Besides the AI topic there is one key thing missing in the Infinito.Nexus Core Repository, but also in the Store and this is the implementation of the 184 ISO 639-1 into our software solution.
The software was primarily designed with German customers and the debate about digital sovereignty of European and especially German enterprises from American Big Tech in mind. Still some frontend elements like the dashboard just supported English as language.
The implementation of German is off course an hard requirement before it can be distributed and promoted on the DACH market. Actually I figured out that there is a easy design pattern to implement this, so part of the 14/15th major release will also be the support of all 184 ISO 639-1 languages.
Infinito.Nexus Store
Besides the Core development the AI Agents of course worked in the last weeks on implementing the store.
Theoretically the store is ready. Off course there are a few issues but overall I think it’s heading in the right direction.
Somewhere in the next weeks I will release a beta version of the store, but before we use it in production there needs to be a deeper security audit.
The store itself is from my point of view at the current situation the weakest part in the security chain and could be used by attackers as entry point into our system. So I don’t feel confident yet to release it, but I have some ideas in my mind how I can use AI supported attacks against the store to penetrate the system and to find all loopholes.
Besides this the API’s for auto-provisioning of enterprise infrastructure are currently just implemented as mocks.
The reason therefore is again a resource issue on my side. To implement them, do the billing etc. I need people in the back office which take care about the bureaucracy and right now we’re just a bunch of programmers.
So the bottleneck since the start of this project is still to have people in the back office, administration and on the business side which could take over tasks like this. Currently we don’t have anybody for this tasks.
Agentic Projects
Besides Core and Store there are two other IT projects which I want to mention.
AgentBox
The first one is AgentBox. The idea behind AgentBox is to encapsulate the agents which work on your code in an highly isolated environment.
This is necessary due to the reason that the agents are currently working in sandboxes like the one which Claude ships onboard, but they can easily break out. It’s just a question of will.
If the agent decides that they want to break out they can break out and can take control over your system. Due to this reason I’m working on a better cage to keep them isolated. I first will use this as part of the Store aka. GUI repo and as soon as I feel confident I will also “box” all of my other repos.
It will be part of PKGMGR so that I can setup and develop new solutions much faster and much safer then ever before.
AgentCrew
The second one is AgentCrew. AgentCrew addresses the problem, that this project requires a lot of people to run and set up a business.
A few weeks ago, during a chat with Amadeus, we talked about that there are existing frameworks like ITIL, SAFe, etc. which describe in detail how to set up an Enterprise Organisation.
With AgentCrew you decide for a framework, define framework roles, characters and the related LLM to use. All people which are normally human beings are replaced by an agent and they will take over the roles.
Due to the reason that not all of the roles need the same capabilities it’s possible to give some agents lower models and other agents better models. In kombination with OpenRouter and local LLM’s you can scale up an organisation for very low costs.
The advantage for us as Infinito.Nexus team is, that we developed the infrastructure tool to give every agent their own account with all tools which they need. Let it be developing tools like gitea\GitLab\jenkins, project management tools like Taiga\OpenProject, cloud access via Nextcloud etc.
Infinito.Nexus can be the base to setup fully autonom working agentic teams.
I will focus on AgentCrew as soon as the store is ready, because then we need urgently agents in the back office, distribution etc.
Business Strategy
The strategy stays the following; The focus is on finishing the core like mentioned above.
Parallel the development of the store continous.
As soon as the store is ready I will contact all people in our CRM system.
Besides this is would be good to get some low level investment. We have now a ready product. A little money as an catalyst to enlighten the engine for digital sovereignty would make our life much easier, but it will also work without it.
The advantage which we have is that as soon as the store is standing and the API’s are integrated we have an scalable product with almost non fix costs, so we can beat all of our competitors by price.
Besides this it’s almost impossible that a real competitor raises.
And now you ask me the question:
Why? Kevin hadn’t you been an hypocrat? Didn’t you tough in your position as agile coach that you find customers and develop a project dependent on their needs and scale up your business by realizing what your customer needs from you?
I can tell you it would had been impossible.
If we would have customers already, we couldn’t had developed an clean architectural solution. We would had acquired a huge amount of technical debt due to the reason that we would had been required to maintain outdated infrastructure and couldn’t implement the radical architectural design which was necessary to implement a tool which can compete in the times of AI with the other companies.
A lot of businesses will fail in the next month and years. The reason therefore is that they vibe coded bad software which is unmaintainable. Our solution is as well designed as as Rolex and usable like a Swiss Pocket Knife.
I don’t know any other software company which delivers such an high quality like we’re doing and we can dump the price almost as low as we like.
Vibe Coding and Agentic Engineering
https://www.youtube.com/watch?v=PbsocBPkoUc
One last sentence I would like to mention concerning vibe coding and agentic engineering and how I apply both practices. So you have an idea how I could realize such an project.
I would say in general I use classical software engineering practices.
The AI works in general autonomously. I inspect the code before commiting and steer the AI in the right direction.
With a lot of the implementations I don’t have any glue at the beginning of the feature how to realize this exactly. This counts e.g. for the docker swarm implementation, the tor implementation, but also the current MCP implementation.
So I let the AI turn wild but I question critically the output and the modifications. The most of the time I have at least 3 agents parallel running which are working on different topics.
Still I need to review all of the code and I feel responsible to understand what the agents are doing. I have the final say about the best approach.
This means that in the last month I still had my 16 hour days just reviewing, deciding and understanding what’s going on, besides that the AI is working parallel 24/7.
I really look forward to the point when this isn’t my daily business anymore.
I hope anybody who is interested in it has now a betting understanding where the project stands, what final challenges have to be tackled and where we will stand in approx. 2 month.
#AcceptanceCriteria #ADR #agentIsolation #AgentBox #AgentCrew #agenticEngineering #agenticTeams #AIAgents #AIGovernance #AIOrchestration #AIPenetrationTesting #AISecurity #AIWorkforce #AIAssistedSoftwareDevelopment #AINativeCompany #AINativeSoftwareDevelopment #architectureDecisionRecords #automatedProvisioning #autonomousAgents #autonomousEnterprise #autonomousOrganizations #cleanArchitecture #Cybersecurity #DACH #DevOps #digitalInfrastructure #DigitalSovereignty #digitalSovereigntyPlatform #DockerSwarm #enterpriseAutomation #enterpriseInfrastructure #EuropeanDigitalSovereignty #futureOfWork #Gitea #Gitlab #heterogeneousLLMs #humanInTheLoop #humanOversight #i18n #InfinitoNexus #InfinitoNexusStore #InfrastructureAsCode #infrastructureAutomation #internationalization #ISO6391 #ITIL #Jenkins #LLMOrchestration #localLLMs #localization #lowCostInfrastructure #MCP #MCPRBAC #MCPSecurity #ModelContextProtocol #multiAgentSystems #multilingualSoftware #Nextcloud #OpenSource #openSourceBusiness #OpenProject #OpenRouter #penetrationTesting #PKGMGR #platformEngineering #privateCloud #roleBasedAccessControl #SaaS #SAFe #sandboxing #scalableBusiness #scalableInfrastructure #secureAIAgents #securityAudit #SelfHosting #softwareArchitecture #softwareEngineering #softwareMarketplace #Taiga #TDD #technicalDebt #TestDrivenDevelopment #Tor #vibeCoding #virtualOrganizations #zeroTrust
Marimo Notebook Flaw Exposes Users to Pre-Execution Code Injection
A high-severity flaw in Marimo Notebook software, tracked as CVE-2026-75149, could allow attackers to inject malicious code on a user's machine simply by opening a specially crafted notebook in edit mode. This vulnerability, rated 8.7 out of 10 in severity, requires no authentication - just a click.
#MarimoNotebook #CodeInjection #Cve202675149 #ModelContextProtocol #Preexecution
The common cause of AI-generated bugs isn't faulty logic, but rather a complete lack of infrastructure context.
By tunneling an MCP server into your Upsun environment through the CLI, your AI assistants can finally see database schemas and live configurations instead of guessing.
This secure connection lets tools like Cursor check their suggestions against a replica of your production data without risking your live site.
MCP im Planungsbüro: Wie KI-Chatbots direkten Zugriff auf Ihre Programme bekommen
→ https://internet-fuer-architekten.de/mcp-ki-chatbot-cad-bim-buerosoftware/
#BuildingInformationModeling #CADSoftware #Chatbots #KIAgenten #KünstlicheIntelligenz #ModelContextProtocol
𝗕𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝗠𝗲𝗺𝗣𝗮𝗹𝗮𝗰𝗲: 𝗦𝗲𝗰𝘂𝗿𝗲 𝗟𝗼𝗰𝗮𝗹 𝗔𝗜 𝗠𝗲𝗺𝗼𝗿𝘆 𝘄𝗶𝘁𝗵 𝗖𝗹𝗼𝘂𝗱𝗳𝗹𝗮𝗿𝗲 𝗭𝗲𝗿𝗼 𝗧𝗿𝘂𝘀𝘁 𝗮𝗻𝗱 𝗔𝗻𝘁𝗶𝗴𝗿𝗮𝘃𝗶𝘁𝘆 𝗜𝗗𝗘
Build a private long-term AI memory system. Step-by-step guide to self-hosting MemPalace on a homelab, securing remote access with Cloudflare Zero Trust, and integrating Model Context Protocol (MCP) in Antigravity IDE for automated code context.
#mempalace #aimemory #antigravity #antigravityIDE #mcp #modelcontextprotocol #cloudflare #docker #homelab
https://dariusz.wieckiewicz.org/en/mempalace-local-ai-memory-cloudflare-antigravity/
From the Leanpub Blog: The Leanpub Podcast 🎙 Feat. Ediz Najim, Author of Systems Thinking for Agentic AI: A Software Architect’s Guide to Building Reliable LLM and Agent Systems
#books #leanpublishing #selfpublishing #AgenticAI #SystemsThinking #SoftwareArchitecture #LLMEngineering #AIReliability #RAG #ModelContextProtocol #BackendDevelopment #AIObservability #Leanpub
NEW! The Leanpub Podcast 🎙 Feat. Ediz Najim, Author of Systems Thinking for Agentic AI: A Software Architect’s Guide to Building Reliable LLM and Agent Systems
#books #leanpublishing #selfpublishing #AgenticAI #SystemsThinking #SoftwareArchitecture #LLMEngineering #AIReliability #RAG #ModelContextProtocol #BackendDevelopment #AIObservability #Leanpub
In the March issue I tried to capture the anti-MCP sentiment and hype around CLIs. Of course, pronouncing MCP dead turned out to be quite premature… https://www.bitoff.org/the-api-dispatch-11/
Production security for #ModelContextProtocol (MCP) requires more than gateway enforcement.
In this #InfoQ article, Nik Kale outlines a defense-in-depth approach built on 4 architectural control layers:
🔹 Safe Execution
🔹 Management Infrastructure
🔹 Outbound Trust
🔹 Semantic Integrity
Learn why security must be enforced at the earliest trustworthy control points.
🔗 Read now: https://bit.ly/45tPB6P
Announcing v2.0 of the official MCP C# SDK
https://devblogs.microsoft.com/dotnet/announcing-v20-of-the-official-mcp-csharp-sdk/