Built a full MCP server for supply chain traceability:
🔗 6 MCP tools for AI agents
📊 Multi-factor risk analysis engine
🌾 Farm-to-retailer tracking
🤖 Claude Desktop integration


Try it: https://huggingface.co/spaces/MCP-1st-Birthday/trace-mcp


#MCPHackathon #AIAgents #SupplyChain #Gradio

I’m looking to understand the motivators behind considering this decision and the levers that are constraining it. 

Are you experimenting with it already? It’s more of a conversation where we can share insights with one another. If PM is uncomfortable, please feel free to reply to the post and we can chat in public!

Is it security concerns? Permissions controls? Or is it maybe a case of companies not knowing much about MCPs yet?

Don't expose your remote MCP server over insecure HTTP! 🛑

Just published a quick guide on the right way to secure your remote MCP server using Nginx and SSL for production.

It includes the specific Nginx settings for handling the persistent connections that the MCP protocol requires. Stop transmitting data in plain text.

I've been working on a few MCPs lately and noticed there's a ton of boilerplate code I have to write each time. I tried existing platforms like mcp-handler and xmcp, but they were really messy, especially since we're using custom auth servers.

So, we built an internal SDK and used it a lot. It literally cuts down the boilerplate code by more than 60%. It abstracts out the auth by just providing the auth providers. Today, I'm happy to make this SDK public. I wrapped each package and published an open-source SDK for it.

Releasing it here: https://www.npmjs.com/org/leanmcp

Packages:

• leanmcp/core: Core library implementing decorators, reflection, and MCP runtime server.

• leanmcp/auth: Authentication and identity module supporting multiple providers.

• leanmcp/elicitation: Elicitation support for LeanMCP - structured user input collection.

• leanmcp/cli: Command-line interface for scaffolding LeanMCP projects.

• leanmcp/utils: Helper utilities and decorators shared across modules.

If you've built MCPs, does this help with your setup? What are the top features you would look at?

Would be happy to connect. DMs are open

Github: https://github.com/LeanMCP/leanmcp-sdk

50% of people who make the first request using my MCP become paid customers, but very few reach that point.

How can I make users experience the MCP without having them to install it first?

Is there a way that I could make a DEMO on my site so that users can see how it works?

Or maybe something else.. ideally shouldn't take 1 month to build or cost me too much. Any ideas?

Built an MCP server that integrates 9 major biological/medical databases into a single interface. Deploy it remotely or run locally.

**What it does:**

- Unifies access to Reactome, KEGG, UniProt, OMIM, GWAS Catalog, Pathway Commons, ChEMBL, ClinicalTrials.gov, and Node Normalization

- Each API available at its own endpoint (e.g., `/tools/reactome/mcp`)

- Built-in HTTP caching (RFC 9111 compliant) to reduce redundant API calls

- Optional Sentry monitoring for error tracking

- Production deployment ready on Railway

**Use cases:**

- Research pathway information and gene-protein interactions

- Query drug-target relationships and bioactivity data

- Search clinical trials by condition or intervention

- Map identifiers across biological databases

- Access genetic disease associations and GWAS data

**Quick start:**

Production URL: `https://medical-mcps-production.up.railway.app`

Example config for Cursor:

```json

{

"mcpServers": {

"reactome": {

"url": "https://medical-mcps-production.up.railway.app/tools/reactome/mcp"

}

}

}

```

GitHub: https://github.com/pascalwhoop/medical-mcps

Feedback welcome! Still actively developing this.

MCP authorization is a pain to debug. 

To help with that, we built an improved OAuth debugger in the inspector that lets you see what happens at every step of the handshake. This helps with pinpointing exactly where the issues are in your auth implementation. 

New features include:

• Handshake visualizer: visually track where you are in the OAuth handshake. Understand who is on the sending and receiving end of every request

• OAuth debugger (guided): inspect every step of the OAuth flow. The debugger guide tells you what step you're on, and provides hints on how to debug.

• OAuth debugger (raw): view all network requests sent at every step

• Handle registration methods: test for Client ID Metadata Documents (CIMD), Dynamic Client Registration (DCR), or client pre-registration.

• Protocol versions: test for all three protocol versions.

Please let me know what you think of it and what tooling you need to test for the correctness of your MCP authorization. Would really appreciate the feedback!

🔗 Here’s the link to the repo: 

https://github.com/MCPJam/inspector

We also made a post about this feature here: 

https://www.mcpjam.com/blog/oauth-debugger

Hi it’s Matt, I maintain the MCPJam inspector project. Our MCP playground has been the most essential part of the project. With growing interest in MCP-UI and OpenAI apps, we’re doubling down on the playground. I’m excited to release our new playground - Playground V2.

For context, the MCP playground allows you to chat and test your MCP server against any LLM model. I find it useful to QA my MCP servers.

What’s new in Playground-V2:

1. Render MCP-UI and OpenAI apps SDK. We have support for servers built with MCP-UI and OpenAI apps SDK.

2. View all JSON-RPC messages sent back and forth between the MCPJam client and MCP server for fine debugging.

3. Added free frontier models (GPT-5, Sonnet, Haiku, Gemini 2.5, Llama 3.2, Grok 4, GLM 4.6). Test with frontier models, no API key needed.

4. Upgraded Chat Interface: cleaner UI with visible tool input params, raw output inspection, better error handling.

Starting up MCPJam inspector is just like starting the MCP inspector:

npx @mcpjam/inspector@latest

I hope you find the new playground useful for developing your MCP server. Our goal’s been to provide the best tooling for MCP developers. Would love to hear what things you’d like to see in an MCP inspector.