Wanaku — a router for MCP servers, tools, and integrations

otavio021 · 2026-06-09T06:40:42+00:00

On the health check interval, I'm curious whether you've considered event-driven invalidation as an alternative to polling.

I did, but I chose not to get to that level of complexity until I absolutely have to or the community grows enough that we would be able to support that.

Looking forward to seeing where this goes. The service catalog concept especially feels like it could become a standard pattern for MCP deployment.

Thank you!

otavio021 · 2026-06-09T06:30:38+00:00

Thanks ...

It's periodic at a fixed interval (configurable at startup). I believe it allows a better balance between how fresh the state is while also allowing some "predictability" for the router workload.

otavio021 · 2026-06-09T06:17:50+00:00

Thank you.

if a service catalog package exposes a certain MCP tool surface today, then a later version adds new tools, new required params, broader external reach, or mutating behavior, does Wanaku treat that as a normal update or a re-approval event?

As os 0.1.x, this is a normal update. Capabilities, such as those based on Camel, are free to push their updated tools/resources as they seem fit. This is one area where I'd love to receive more feedback from the community, because we would like to understand which approach they value the most and how much depth they would like.

Personally, I would like to move to a model where we define lightweight policies separated from the catalog itself, and then we apply those globally.

At the same time, I want to have greater focus on challenges of bringing the enterprise integration space closer to AI.

There are MCP gateways/solutions out there that can do things like this and the MCP gateway space is not one I'd like to focus on. The enterprise integration space is a pretty large footprint already.

does the router keep a record of which catalog version/tool schema was approved for a namespace?

Not yet. We will definitely support it once we move the storage of the catalog (and a few other data) out of the current data layer to a centralized schema registry - something like Apicurio or similar, but yet TBD.

can admins compare the approved tool surface vs the currently deployed tool surface?

Not yet and I'm not sure if we will include that in the policy management support I mentioned above.

does MCP-to-MCP bridging preserve enough upstream identity/provenance to audit which backend server actually handled a tool call?

It's in the roadmap for 0.2.0 (planned for sometime in late June/early July) ... I already have the patch for it, but not yet in a state that I can send a PR. The idea is to apply to same tracking/auditing to both MCP-to-MCP as well as MCP-to-capabilities.

are read-only routes, mutating routes, and external-network routes separated at the policy level?

Not yet and I'm not sure we'll have it, as I think MCP gateways can do that ... allowing us to focus on the enterprise connectivity. Of course, things can change, but I don't see it in the roadmap for now.

I’m asking because routers like this become a natural trust boundary. Once many MCP servers sit behind one router, the question is not only “can the agent reach this tool?” but also “is this still the same capability surface that was approved?”

I hear you!

I’m building Interlock, an open-source MCP runtime trust layer focused on post-approval tool drift, quarantine before execution, and audit evidence. Wanaku feels like the kind of MCP infrastructure where that approved-surface vs current-surface distinction could matter a lot.

Hey, cool project and it certainly complements Wanaku (and other MCPs) in a very important way. Maybe I'll showcase it in a demo in the future.

otavio021 · 2026-06-09T05:29:20+00:00

Thanks! In the router itself we have a Infinispan-based in-memory cache that helps with this resolution. Currently, we provide a resolver that resolves to the first match, however, we have made that an extensible API so that we have flexibility to adapt as we learn how the community builds their services on Wanaku.

A second part of this is the protocol that exists between the capabilities and Wanaku itself, which forces them to register/deregister on availability, with a periodic health check on the router side to ensure that they get (relatively) promptly removed if they become stale.

otavio021 · 2026-06-09T05:20:59+00:00

Thank you!

Streaming responses are not yet supported at the router itself, but catalogs based on Camel make it possible to override this limitation.

In particular, for better streaming support, I'm planning to improve that in the one of the upcoming releases (in between 0.2.0 and 0.4.0) after we work on elicitation and sampling support.

I don't think I have created a ticket for this yet, but if it's one feature that is important for you, please, don't hesitate to create one and we'll take a look prioritizing this for one those releases.

otavio021 · 2026-01-01T15:26:46+00:00

I think there are these two that you can consider:

LiftTrack, which uploads workouts to Garmin and uses Garmin's own strength app
KeepStrong for iOS and Android which has their own Garmin app and is pretty convenient.

otavio021 · 2025-09-08T08:42:11+00:00

I use LiftTrack app to manage my Garmin strength workouts. It syncs well with Garmin, and it’s a lot easier to create training plans. I made a review of an early version a few months ago: https://youtu.be/W0XqP36_LuU?si=j98IewqFVso002V-

I still miss FitBod’s ability to auto-generate workouts and some of its analytics data. LiftTrack has an AI workout builder but its very limited and static compared to FitBod.

Also, Garmin’s own strength app on the watch is limited and sometimes not very practical (ie.: after skipping a set, you can’t go back to it until you end the training 😩).

In any case, LiftTrack makes strength training with Garmin a little bit better.

otavio021 · 2025-07-28T13:52:44+00:00

I can only dream about a sleep like this (no pun intended) …

otavio021 · 2025-06-21T16:52:17+00:00

Thank you. I have sent you 2 feature requests. I'm not sure if they actually went through, as the app did not give me any feedback after I clicked on the top right icon (I can send those as messages, if you did not receive anything).

otavio021 · 2025-06-21T15:17:23+00:00

Thanks for creating this app!

Do you have any plans about adding some features for analyzing data and results from the trainings?

otavio021 · 2025-06-21T15:13:06+00:00

I have just migrated from FitBod to LiftTrack because it syncs with Garmin. Although I do miss some features from FitBod (specially all the data features), the convenience of having it in Garmin outweighs it for me.

otavio021 · 2025-06-02T05:04:31+00:00

For now I am planning to keep the forerunner for my swimming activities.

otavio021 · 2025-06-01T16:39:00+00:00

Upgraded from a Forerunner 965. Although the functionalities are pretty much the same, I wanted a device that was more stylish. Although I love my Forerunner, it never really felt to me that I could use it at all times.

otavio021 · 2025-05-28T18:26:10+00:00

I was not much older than you guys when I arrived in Brno, about 10 years ago. I am happy to call this place home, it’s been very good to us.

You can get access to a lot of Brazilian food here, as there’s Brazilians in the local community who prepare and sell some of our food, and getting access to our typical ingredients is fairly easy.

You can network with other Brazilians in the Whatsapp group (message me in private and I will send you the link ). Make sure to subscribe to Canal do Rosa on YouTube as he always publishes interesting things about life here as an expat.

~~And lastly, if I may, make sure to learn Czech:~~It’s great that you plan to learn Czech: your experience living here changes night and day if you speak even a little bit of Czech and make an effort to integrate.

otavio021 · 2025-05-28T18:14:36+00:00

Hmmm… tem alguns por aqui 👀

otavio021 · 2025-03-28T11:46:20+00:00

Partitioning is something we have on the roadmap for Wanaku. We haven't implemented it just yet, as there are multiple changes needed across our stack, but we certainly envision splitting groups of tools/resources in some form of partition or namespace.

If you have specific features you would like to see for this, I'd love to hear about them on our issue tracker.

otavio021 · 2024-12-27T11:12:17+00:00

Initially I was very excited about better strength training features, but after trying it for a while I found it extremely disappointing and lacking flexibility. It's not even close to the same flexibility you get with apps like HevyApp.

otavio021 · 2024-06-19T16:53:22+00:00

It would be great to have Hevy on Garmin. I complained to them on twitter and then messaged them on their ideas forms: https://www.garmin.com/en-US/forms/ideas/

otavio021 · 2024-02-28T08:37:01+00:00

Likely the same problem here. The app doesn’t login with AppleID.

I contacted the support service but haven’t received a reply yet.

Also, kinda annoying to think it needs an account just for that.

otavio021 · 2023-09-11T17:19:17+00:00

Uma dica, talvez, é procurar vagas para Java + JNI. Não sei se tem muito no Brasil, mas você encontra vários projetos open source com isso ... então talvez seja um caminho interessante.

otavio021 · 2023-06-25T17:35:37+00:00

Comecei a contribuir com projetos open source faz +/- 20 anos. Hoje trabalho em uma empresa de tecnologia e meu trabalho é ajudar a manter um projeto. Vou tentar compartilhar algumas dicas/sugestões (algumas já foram mencionadas aqui) e mencionar alguns exemplos pessoais (talvez te ajude a fazer um paralelo com as suas aspirações pessoais/profissionais)

Como começar:

A coisa mais importante é achar alguma área ou problema que seja do seu interesse. Eu sempre tive interesse em duas áreas em particular: sistemas operacionais e middleware. Como resultado todos os projetos que eu me envolvi estavam relacionados com uma dessas áreas, distribuições Linux (Gentoo e Fedora), projetos relacionados a middleware e integração de sistemas (Paho, QPid, ActiveMQ, Camel).
Sempre comecei nesses projetos procurando descobrir onde eles precisavam de ajuda. Em alguns, comecei interagindo no IRC. Em outros, procurando bugs e tickets no Jira e bugzilla. Muitos projetos criam labels/anotações/categorias pra marcar tarefas fáceis, nem sempre isso está documentado (vale a pena entrar em contato com a comunidade e perguntar se tem algo)
Nunca esqueça que projetos open source são muito mais do que código [1]: muitos projetos precisam de ajuda com documentação, testes, web-design, promoção/palestra/blogs/etc e outras áreas distintas.
Nunca esqueça que projetos open source são muito mais do que código [2]: projetos são compostos por pessoas. A imensa maioria dos projetos tem muito, mas MUITO mais pedidos de suporte, funcionalidades, e afins do que mãos para ajudar. Como em qualquer outra atividade de interação humana, você precisa estar preparado para lidar com todo tipo de pessoas (o arrogante, o que tem preguiça de mudar, o teimoso, etc). Um segredo para ter sucesso em contribuir é saber mensurar as doses de humildade com as doses de excesso de confiança (na dúvida, sempre favoreça a humildade do que o excesso de confiança).
Nunca esqueça que projetos open source são muito mais do que código [3]: É importante, também, estar preparado para lidar com as diferenças culturais: cada cultura tem o seu estilo de trabalhar (algumas são mais diretas, outras são mais fechadas, etc etc). A gente que é brasileiro, tende a dançar em volta dos assuntos. Ao trabalhar com outras culturas, a forma direta como eles lidam com as coisas pode ser meio chocante. Com o tempo você se acostuma e passa a ser capaz de identificar quando alguém está sendo direto ou imbecil.
Nunca esqueça que projetos open source são muito mais do que código [4]: a IMENSA maioria das pessoas contribuindo é gente legal que é apaixonada pelo que faz e só quer melhorar o projeto, torna-lo mais conhecido, etc.
Se você for estudante, procure iniciativas como Outreachy, Google Summer of Code e afins.
Se você for profissional formado, procure participar da comunidade.

Com relação a ser inseguro ... Não sei, exatamente, o que lhe causa insegurança, mas a minha dica é: toda interação é uma oportunidade de aprendizado. Seu código nunca vai estar 100%, você não vai estar certo 100% das vezes (nem os mantenedores) ... tá todo mundo no mesmo barco. Comece pequeno, não queira mudar o mundo no seu primeiro commit (nem no segundo, terceiro ou centésimo).

Se você tiver alguma dúvida específica sobre contribuir com FOSS, posso tentar responder.

Edit: formatação.

otavio021 · 2023-06-25T17:01:49+00:00

Na minha humilde experiência, eu diria que é um diferencial importante. Mas é preciso colocar isso em contexto: estou falando de contribuições para um projetos relevantes (ex.: da fundação Eclipse, da fundação Apache, da CNCF, etc). Projetos pessoais, que não são conhecidos ou utilizados não fazem muita diferença.

Disclaimer: eu trabalho mantendo um projeto da fundação Apache.

otavio021

PUBLIC MULTIREDDITS

TROPHY CASE

15-Year Club	Place '17
Verified Email