Private user • about 1 month ago
Request for Feedback on Our MCP Hackathon Submission
Dear Judges,
I hope you are doing well.
First of all, thank you for organizing this hackathon and creating an opportunity for developers to explore and build meaningful solutions using MCP architecture. Our team genuinely enjoyed participating and learned a lot throughout the process.
We are writing this email respectfully to understand where our project may have fallen short during evaluation.
Our team, S.H.I.E.L.D (Smart Health Intelligence & Evaluating Learning Diagnostics), focused on building a healthcare-oriented MCP ecosystem with interoperable AI diagnostic agents designed for practical real-world use cases. The project included 11 MCP-integrated tools and multiple machine learning/deep learning models working together through standardized MCP workflows.
The system was designed around:
- MCP-compliant tool orchestration
- Real-world healthcare screening workflows
- Explainable AI integration
- FHIR-based patient context handling
- Multi-model interoperability
- Clinical workflow automation
We have attached screenshots of the architecture, tools, implementation flow, and technical details for reference.
We completely respect the final results of the hackathon. However, we would sincerely appreciate feedback regarding the areas where our submission may have been weaker compared to selected projects.
We mainly want to understand:
- Was the issue related to our presentation/demo?
- Was the project too broad or complex?
- Did the MCP implementation not align with expectations?
- Was there any concern regarding practicality, scalability, innovation, or execution quality?
- Or were there specific aspects we could have communicated better?
Our intention is not to challenge the decision in any way. We simply want to learn from experienced judges so we can improve ourselves and build stronger projects in future hackathons.
We are highly motivated to continue working with MCP-based systems, and honest feedback from your side would genuinely help us improve both technically and professionally.
Thank you once again for your time, effort, and consideration.
Warm regards,
Team S.H.I.E.L.D
Devpost Project Link: https://devpost.com/software/s-h-i-e-l-d-7cw6il?ref_content=user-portfolio&ref_feature=in_progress
Log in or sign up for Devpost to join the conversation.
3 comments
Private user • about 1 month ago
please respond
Pawan Jindal Manager • about 1 month ago
Dear Team S.H.I.E.L.D,
Thank you for reaching out. First, we truly appreciate your participation in the hackathon. We want to thank you for the time, effort, and thought your team put into building your submission.
We received more than 300 projects, and our team and the judges spent significant time reviewing submissions across the requirements and evaluation criteria. While we are not able to share detailed individual scoring or judge-by-judge feedback, I did personally take another look at your submission and can share some high-level observations that may be helpful.
One of the key requirements and evaluation criteria was a clear demonstration of how the project integrated with the Prompt Opinion platform. This was especially important because one of the main goals of the hackathon was to see agents and tools that could be clearly integrated in real workflows, not only described conceptually.
Your project seemed technically interesting and ambitious, particularly in its multi-agent design and diagnostic workflow concept. However, in the submitted demo, the implementation and integration were not as clearly demonstrated as the description suggested. For example, while MCP was referenced as the standard in the description, the video actually discussed A2A when the Po platform was shown. While A2A was mentioned, there was no demonstration of the A2A consult feature. The actual demo did not make it sufficiently clear how MCP (or A2A) was being used end-to-end in the working system.
This does not take away from the effort or creativity behind your project. It appears to be a meaningful and promising idea, and we would encourage your team to continue developing it. You did a great job of defining the problem statement. IMHO, for future submissions, I suggest making the demo more focused and explicit, and making it very easy for judges to understand how the core technical requirement is being met.
I hope this provides helpful context. To be respectful of the judging process and consistency across all participants, we are not able to provide further individual feedback beyond what I have shared here, but we genuinely appreciate your effort and encourage you to keep building on the project
Again, thank you for participating and for your thoughtful message. We genuinely appreciate your professionalism and your interest in learning from the experience. We hope to see your team continue to build and participate in future opportunities.
Private user • about 1 month ago
Thank you so much for taking the time to review our project again and for providing such constructive feedback. We truly appreciate the clarity.
We completely understand your point regarding the demo presentation. To clarify briefly on the technical implementation: we actually fully built and integrated our MCP tools into the Prompt Opinion marketplace, which was running in the background of the video. Because the submission form required us to select a single track, we chose MCP, though we had also explored A2A concepts. Due to time constraints and compressed audio in the video, the end-to-end MCP workflow was only shown in detail during the final minute, which we now realize made it difficult to follow.
We accept that our presentation structure should have made this core integration much more explicit from the very beginning. Your advice on focusing the demo tightly around the primary technical requirement is incredibly valuable, and we will absolutely carry this lesson into our future hackathons. Is there any way to consider our project?