Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Forward-compatible discoverability profile + signed reference at getspeakable.ai

Abierto
#166 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
html, json

Línea de trabajo

Read the repository README and the linked WebMCP v1 specification, then compare the proposal with issues #131, #51, #88, and #105. The proposal identifies the /.well-known/webmcp.json manifest and <link rel="webmcp-manifest"> fallback, but does not identify an implementation file or agreed change for this repository. Completion would require the maintainers to decide whether this belongs in the CG roadmap and, if so, specify the normative text or implementation work.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

The README lists "Enable/influence discoverability of sites to agents" as a non-goal, and issue #131 addressed local auto-registration rather than cross-origin pre-flight discoverability. In the meantime, production deployments building for agentic-commerce workloads — especially transact-class tools — are hitting a concrete operational gap: agents can't plan before loading the page, and there's no cryptographic way to verify that a registered tool came from the domain operator rather than a third-party script (tag manager compromise, supply-chain injection).

We've published a forward-compatible profile and a live signed reference implementation that may be useful input if / when the CG decides to revisit this as a goal:

Design choices aimed at round-tripping cleanly into whatever the CG eventually adopts:

Concern Approach
Location /.well-known/webmcp.json + <link rel="webmcp-manifest"> fallback
Integrity JCS (RFC 8785) canonical body, Ed25519 signature with signature removed from payload
Key reuse Same key chain as Web Bot Auth (RFC 9421 / IETF HTTP Message Signatures) and JWK Thumbprint (RFC 7638) — origins signing for WebMCP don't need a new key
Risk taxonomy riskClass: read / mutate / transact / escalate — maps onto where agent.requestUserInteraction() should gate
Drift Runtime tool inventory from provideContext() / registerTool() reconciled against manifest; mismatch on transact / escalate halves trust weight
Forward compat Field names + JSON shapes chosen so a v1.1 alignment to CG-adopted discoverability is losslessly migratable

Happy to contribute normative spec text or implementation reports if any of this maps to where the CG is heading. Either way, the reference is available to point at from discoverability-adjacent threads (#51, #88, #105) so there's a concrete working example on the table.

—

Disclosure: I'm shipping this through https://getspeakable.ai — a certification platform scoring businesses for AI commerce readiness. The manifest is open-spec; anyone can implement and verify without us.

Lenguaje dominante
Bikeshed
Estrellas
4.7k
Forks
328
Merge medio
2 d 15 h
PR fusionados (30 d)
16

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de webmachinelearning/webmcp

Todos los issues de webmachinelearning/webmcp

Issues similares

Más issues de Backend & API Design

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.