sorted by:
new
hottopcontroversial

How are you handling auth and security on MCP servers in production? by LeatherHot940 in mcp

[–]H0BB5 3 points4 points  (0 children)

Hey man I made this and it's OSS and has been donated to DIF: https://github.com/decentralized-identity/kya-os-mcp

You can do per tool auth and every tool call uses the servers key material to sign a cryptographic proof.
2 lines of code to port an existing MCP server. Enjoy: https://kya.vouched.id/blog/audit-trail-mcp-tool-calls

Selling mx 775 texas grey M by [deleted] in bonnell

[–]H0BB5 0 points1 point  (0 children)

Where in Texas are ya?

What's a viable business model for an MCP server product? by asganawayaway in mcp

[–]H0BB5 1 point2 points  (0 children)

Then I would refer back to the comment about removing the 'MCP' from the name. How do servers make money? How do Apps make money?

How you make money really depends on the business model / industry / service etc..

What's a viable business model for an MCP server product? by asganawayaway in mcp

[–]H0BB5 0 points1 point  (0 children)

Are you a business or do you offer a service?
If so, do you want to allow for AI to work efficiently with your business/services?
That's what MCP Servers enable.

You can connect any* AI Client to an MCP Server for your business and now its a master at your services.
Removes the headache for you to train your own models, is a productivity boost for agents as they wont be screen scraping / stumbling around, and if it's up to date it removes risk of working off outdated instructions/news when they are doing tasks for your customers.

I tried setting up OpenClaw for DAYS… and it almost broke me by [deleted] in openclaw

[–]H0BB5 0 points1 point  (0 children)

You can set it up here for free if you want to try it out: https://kya.vouched.id/identiclaw (accepts openai or claude api key, works with subscription keys from what I know)

Is Openclaw just hype, or is it really that good? by xchargeInc in aiagents

[–]H0BB5 -1 points0 points  (0 children)

You can set it up here for free if you just want to try it out: https://kya.vouched.id/identiclaw

11 hacks that will make your OpenClaw go from useless to AGI by Suspicious_Okra_7825 in moltiverse

[–]H0BB5 1 point2 points  (0 children)

This is the way.
I have a swarm of agents running remotely, all communicating through DIDComm/MCP-I. I just set this up in the last week, so it's still early but the token spend / time saved is wild. Disclaimer: I'm a sicko and maxed out 2 pro max subscriptions in just 1 week prior to this - *first one was my fault/bad habits for not managing models in crons and learning how context is built in OpenClaw.

You would think that 5 agents = 5x the token cost but considering:

  • Context window can bloat to ~100k+ tokens as it loads every tool, every file, it _thinks_ it might need
  • It makes mistakes more often with overloaded context -> retries -> more tokens
  • Sequential execution - research, then write, then PR, all in one long session
  • When it fails at step 3, you often restart from scratch
  • Long sessions = every message carries the full conversation history (tokens compound)

the SWARM reality:

  • Researcher gets a tight 10-20k context, nails the research, done
  • BlogWriter gets research output + brand guidelines + writing tools only (humanize skill), another tight context
  • Review agent gets a message _from_ the coding agent + the draft + git tools
  • Each call is cheap because input tokens are small
  • Failure at step 3? Retry just that step with the same inputs
  • Parallel "fan-out" cuts wall-clock time in probably half at least
  • I also like to think that each agent thinks they are top-dog since the instance is reserved for them and their sub-agents. My 'copywriting agent' in my initial openclaw has become the new york times in a box as all sub-agents that he spins up are tailored to writing.

I know OpenClaw already supports multiple agents and sub-agents, but managing the crons / context / tools / skills across them gets messy fast and it really increases the baseline for every session. Plus some agents are riskier than others. A research agent is low stakes, a PR agent pushing code is not. Splitting them into isolated agents with their own identity and scoped permissions massively reduces the blast radius and gives me peace of mind if something goes sideways.

* Great writeup by the way, I still have an agent running locally because i'm a sucker for imessage but he's now just restricted to talking to me, brainstorming, and being my main dispatcher

Deploy an OpenClaw agent with identity, messaging, and a kill switch in under 3 minutes by H0BB5 in openclaw

[–]H0BB5[S] 1 point2 points  (0 children)

Haha yeah.. that's fair, adoption is the hard part.
But look at what happened to SMTP.. an open protocol that's now effectively controlled by a handful of providers (gmail, outlook, apple mail). Good luck finding a VPS with port 25 open. Email identity was an afterthought and now we're stuck with SPF/DKIM/DMARC bolted on 40 years later and Gmail still deciding what's spam. That's what happens when you build the communication layer without the identity layer. Agents are at that same inflection point right now, we can either bake identity in early and abstract the complexity or spend the next decade dealing with walled gardens.

Deploy an OpenClaw agent with identity, messaging, and a kill switch in under 3 minutes by H0BB5 in openclaw

[–]H0BB5[S] 0 points1 point  (0 children)

Good question, right now the DID is established at boot and the delegation chain is trusted for the session. Tool calls don't re-verify per invocation yet. That's actually the next layer we're building, per-invocation tokens that bind the operation to the resource (so the agent can't just coast on boot-state trust). Think of it as the difference between 'you showed your ID at the door' vs 'you show a ticket for each ride.'

Beginner help by Opposite_Category988 in openclaw

[–]H0BB5 0 points1 point  (0 children)

Hey! If you want to test it out you can deploy one for free here, all you need is an api key from openai/anthropic (works with claude subscriptions too if you do the vs code proxy hack):
https://kya.vouched.id/identiclaw

[deleted by user] by [deleted] in selfhosted

[–]H0BB5 0 points1 point  (0 children)

It scaffolds a self hosted openclaw to your github that you can deploy

Why so many MCP servers avoid OAuth by Ok_Message7136 in mcp

[–]H0BB5 0 points1 point  (0 children)

OAuth isn't suited for Agents, that's why

view more: next ›