THE TOOLS AND UTILITIES ECOSYSTEM
A place to discover useful WebMCP capabilities, share what you have built, and make practical tools available to other people and organisations.
Wasame and Zkuh are complementary parts of that journey: connecting people to useful services, and checking that what is shared is understood and trustworthy.
Share something with us →
DISCOVERBUILDSHARETHREE CONNECTED PARTS
These are distinct roles in an emerging ecosystem, not claims that every feature is already a live storefront or certified service.
01 / WASAME
Wasame is the service-broker concept: a clear way to ask “do you have it?”, “can you build it?” or “can I sell it?”. It connects a need with an existing service, a creator or a build pathway.
For visitors, that means discovering useful services. For makers, it means presenting capabilities and finding people who need them.
Useful for: service discovery, creator profiles, requests, commissions and routes to market.
02 / ZKUH
Zkuh is the checking and assurance layer for utilities shared through the ecosystem. The intention is to make provenance, permissions, behaviour and evidence easier to understand before someone relies on a tool.
It supports a more responsible path from “someone published this” to “I understand what it does and what I am authorising”.
Useful for: utility checks, capability descriptions, permission boundaries, evidence and receipts.
03 / WEBMCP AND EDGE UTILITIES
WebMCP gives a website a structured way to expose actions to an AI agent in the browser. Around that, there are opportunities for focused utilities, widgets, connectors and services that solve one useful problem well.
We want to surface demonstrators, working examples, browser-side tools, MCP-connected services and creator-built utilities that can be explained, tested and responsibly shared.
Useful for: demonstrations, reusable widgets, browser interactions, MCP tools and practical integrations.
SHARE · BUILD · SELL
A clear use case, not just a feature list.
Document permissions, limits and dependencies.
Separate a demo from a tested implementation.
Explore a listing, collaboration or paid engagement.
Tell us what it does, who it helps, what it needs access to and whether it is a demo, pilot or production-ready. We can help work out the right way to present it.
Submit an idea or capability →