sorry for the issues you are facing. can you let me know what was the issue? the repo can scan github mcp server code posted in the repo like https://github.com/punkpeye/awesome-mcp-servers and provide a quick, deep, or deep with ai analysis. let us know if there is anything we can help with.
thanks for sharing this. did not know about them. from initial glances, there are a few things we are aiming to do on our roadmap that they have already working (inspiration). however, our goal is to add audits, database of scans, ability to contribute scans to a service that dev can look and avoid, and more.
you brought some great points. what we are hoping to do next iteration is to add audit logs of actions taken (of high risk actions) that way even if the user "accidentally" blank agrees their mcp service to take the rm action then at least they can see if the action was something they typed or suggested by the LLM.
if you have some improvements around this space love to chat and collaborate!
great question. the way we are thinking about it is keeping a list of endpoints that can aid in getting the latest vulnerabilities, keywords, and patterns to detect. we don't know when that is released but that is on our roadmap for sure.
I know right? I mean the timing is great. I love MCP but cant stand how unsafe it is. I think there are greatness ahead if we are able to fix this security issue. This was made around the idea to be as seamless as possible, as we built a dashboard, drop in a GH project MCP server link, and have a local DB to show what you ran. We have more great things ahead. But give it a try and let us know what you think!
Appreciate the interest and the first comments man. We like how fast Cerebras is and its importance to making the scanning fast! Yeah we have thought about this being part of dev workflow via Github Actions and locally for the dev environment too. Love to hear what you are building!
We are developing an agent authentication and policy engine for the modern era. Traditional human authentication via Rails is not scalable, and the agent authentication system that requires users to input passwords is not scalable either. We are working on a solution that improves this significantly without compromising security, compliance, ownership, or speed. We envision a future where agents interact directly with each other, and the current authentication and policy systems need to evolve to handle private data use cases while meeting compliance, security, control, and interoperability requirements. Our goal is to enable resource owners (entities with private data or sensitive materials) to set agentic policies for external parties who meet the necessary requirements to access the data without the need for a user interface or user experience. We combine agentic-ready authentication, policy, and encryption. We welcome your thoughts if you would like to test it out. Our target audience is the enterprise space.
I'm sorry, I wish there were! Unfortunately only Yahoo offers an API that lets my service directly interact with your team. Out of curiosity, which fantasy provider do you use? I think I can find a way to support ESPN but it will take some time.
reply