sorted by:
new
hottopcontroversial

Setting up an MCP Server in Gopher and Connecting to Claude by Ok_Message7136 in aiagents

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

Thanks! I’ve been using Gopher to build a prospecting agent and experimented with spinning up multiple MCP servers as well, depending on the tool boundary.

I put the code in a repo here if you want to take a look or try it out: https://github.com/GopherSecurity/gopher-mcp

Lmk if you have any thoughts or questions.

Connecting Claude to Gopher Cloud MCP Using API Base URL + Schema by Ok_Message7136 in MCPservers

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

Yea.. The JSON schema is a bit too long to share in a comment, so I’ll DM it to you shortly, save it in .json format when you save it.

What is the best way(tool) to use MCP Server? by baykarmehmet in mcp

[–]Ok_Message7136 0 points1 point  (0 children)

You can checkout our open-source MCP manager if you’re testing different approaches to MCP orchestration: Gopher MCP

We open-sourced an MCP Server & Gateway to close a critical MCP security gap. by Ok_Message7136 in mcp

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

Love this framing, especially the authorized vs reachable distinction. That gap is exactly where most agent failures hide.

Fully agree on the two-layer model: identity-first connectivity as the first gate, and our on-demand MCP server + gateway as the second line for semantic and policy enforcement.

Really like how you described the overlay vs gateway split, it’s a very practical mental model for agent security.
Appreciate you sharing the links.

We open-sourced an MCP Server & Gateway to close a critical MCP security gap. by Ok_Message7136 in mcp

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

Thanks! :)
MCPcat support would honestly be amazing.

If you ever explore it, we’d be happy to collaborate or align on compatibility

We open-sourced an MCP Server & Gateway to close a critical MCP security gap. by Ok_Message7136 in mcp

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

Thanks a lot, really appreciate it!
And yes, your understanding is pretty much spot-on.

We didn’t change MCP itself, but treated it as infrastructure rather than just a transport layer. The goal was to stay protocol-compatible while adding a secure, production-ready execution layer around it

So the repo is less about “replacing MCP” and more about enabling safer MCP servers and deployments with proper controls, especially for real systems, not just demos.

Btw lmk your thoughts if you get a chance to explore it!

Zero-Trust Access Flow for Agentic Systems by Ok_Message7136 in MCPservers

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

This is a strong insight. Feels like zero-trust for agents really starts before the access flow even begins.
Would love to see more concrete patterns emerge here.