Frank Fiegel

Glama will always be a free and open directory of MCP servers. We’re not new to this space—our MCP directory was launched on November 25, 2024, just days after Anthropic’s public announcement. Since then, we’ve built the largest dataset of MCP servers, established the r/mcp Reddit community and a Discord server, and contributed open-source tools like FastMCP, awesome-mcp-servers, mcp-proxy, mcp-client, and more. As early pioneers of MCP, we anticipated many challenges in deploying this complex protocol at scale, such as discovery, security, and maintainer accountability. That experience lead us to develop glama.ai/mcp/servers. But Glama is far more than a list. We evaluate every MCP server using heuristics, manual review, community input, and AI automation. Our insights on security, licensing, and interoperability help guide the community toward a more stable, secure, and open ecosystem. Our mission is to provide the most comprehensive dataset on MCP server capabilities and security. All of our MCP data is openly available via API (glama.ai/mcp/reference). Our business offerings—including AI gateway and MCP server hosting—allow us to keep the MCP directory and its data free and open for everyone.

@sebastienlorber @mitchellh Prior art glama.ai/blog/2026-03-1… Since I've posted this, there have been more than 7,000 PRs github.com/punkpeye/aweso…

🤪 Great AI disclosure trick @mitchellh :D

Send me all product feedback. That's always helpful. I keep a constantly evolving backlog based on what users mention the most often. Things that I get tagged on Discord get prioritized the fastest b/c fastest feedback cycle.

Last year number 1 complaint was the stability of the platform. It took almost a year of iterative improvements, but we are now averaging 150ms response time across all of our endpoints

I have achieved 0-inbox in Sentry, and I still cannot believe it. My muscle memory at this point is to just refresh Sentry every couple of minutes.

Small trick to make the image loading feel better When an image finishes loading, fade it in through a brief blur.

In the next update, we will be dropping security grading from Glama directory. The problem is that grading server's security "A" just because we didn't find a clear malware pattern is providing false-safety to the consumers. We tried many things, and static code analyzes is simply not enough. The reality is that even if the server and its dependencies are perfectly fine, there is still a million ways that a 'perfectly secure' server can be used to exfiltrate data or cause harm by combining it with other servers. So far, we found that the best way to catch bad actors is by observing what the server is doing/how it is being used, rather than inspecting the codebase. That's where most of our research has been recently and will be the focus moving forward. Meanwhile, if we do detect definitively unsafe servers, they will be removed from the search index and the listing will be marked as unsafe.

More cool things are coming to Glama. Stay tuned

In the first 48 hours of DeepSeek v4 being available, I've already burned through just a little over USD 2k worth of tokens. The same workload would have easily cost me USD 20k just a few weeks ago using a different model (I wouldn't have done it). Decreased token cost increases token usage. The possibilities are endless.

@nilslice 100%

Every company will follow this path 💯

DeepSeek-V4-Pro-Max vs Frontier Models

Deepseek v4 is finally out!

@walterra It's been fixed. Just seeing the tweet. Accidentally deleted the repo using automated script. Waited for GitHub to restore it.

We just raised the bar for what counts as a quality MCP server. The evaluation framework now covers a lot more ground, which means many servers that previously scored an A will drop to a B or C. Some folks won't love that – but the ecosystem needed higher standards.

97% of #MCP tool descriptions have quality defects. We are developing Tool Description Quality Score (TDQS) framework to fix it. glama.ai/blog/2026-04-0…

This is one of the clearest write‑ups I’ve seen of “AI agents vs open source reality.” Awesome MPC Server Maintainer @punkpeye quietly prompt‑injected their CONTRIBUTING.md and 50–70% of incoming PRs self‑identified as bots. Some are helpful. Some lie about passing checks just to get merged. Worth your time if you care about OSS maintenance: glama.ai/blog/2026-03-1…

How prompt injecting our own CONTRIBUTING.md revealed that 50% of contributions are made by bots. glama.ai/blog/2026-03-1…

Entire X feed "MCP is dead". Meanwhile, MCP community –

@liran_tal glama.ai/blog/2025-12-0… Will do another one in June

@punkpeye I understand. Still would be interesting to see a "state of" report to help remove the cloudy weather from MCPs :)

Ironic to see "MCP is dead" threads all over X in a month when we are seeing all time high adoption. Just one data point: there are more PRs per day being made to github.com/punkpeye/aweso… than we saw during the peak hype cycle of MCP.

I for one am glad to see another loud voice of reason

This is so cool and ... it is an MCP App.