Ctrl K
ComunidadGuías…

Ayuda y problemas de mcp-hangar

Pregunta a la comunidad o invita a KiBot con contexto del repositorio.

Publicar un problema

No publiques contraseñas, tokens ni claves privadas. HostingByte aplica una redacción básica de secretos evidentes antes de guardar el texto.

Problemas en HostingByte

Todavía no hay problemas publicados.

Issues abiertas upstream

#1768 epic: tool-contract integrity in its strong form · 3 comentarios#2173 test(tests): the projection metrics live test fails in a full tier 0 run · 3 comentarios#2208 interceptor pin drift: upstream moved to 07c89a2 · 0 comentarios#2178 feat(core): clearing a tool access policy applies without a restart · 1 comentarios#1783 chore(docs): one tagline across README, PyPI, docs, website, installer and charts · 1 comentarios#1767 epic: we can see who arrives, and people with the problem can find us · 0 comentarios#1762 epic: the documents agents read agree with the code · 0 comentarios#2171 fix(core): a server removed from the file does not leave its durable row · 1 comentarios#2162 test(core): the route guard authorizes on the target, and the remaining REST routes are probed · 0 comentarios#2012 feat(security): decide whether Hangar authenticates to upstreams as an OAuth client · 0 comentarios#2014 fix(core): honour SSE retry and Last-Event-ID when resuming an upstream stream · 0 comentarios#2013 fix(core): apply SEP-1034 schema defaults when Hangar answers an upstream elicitation · 0 comentarios#2011 feat(core): send the SEP-2243 standard and custom headers on requests to upstreams · 0 comentarios#2010 feat(core): carry SEP-2322 request state back to an upstream on a multi-round-trip call · 0 comentarios#2009 feat(core): speak the 2026-07-28 stateless lifecycle to upstreams · 0 comentarios