UniFound MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@UniFound MCP ServerFind potential matches for my lost item"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
UniFound ā AI-Powered Lost & Found Management System
UniFound is a full-stack, AI-powered lost and found management platform built for modern campuses and organizations. The system streamlines reporting, intelligent matching, and verified claiming of lost and found items using intelligent multi-factor matching, a dedicated Model Context Protocol (MCP) server, and an Agentic AI Orchestrator.
š Key Features Roadmap
Core Lifecycle: User accounts, lost & found item reporting with image upload, category tagging, search, and claim workflows.
Role-Based Access: Granular permissions distinguishing campus community members (
USER) from campus security/administrators (ADMIN).AI Matching Engine: Explainable similarity scoring across categories, semantic descriptions, campus locations, timestamps, and item visual features.
Dedicated MCP Server: Standardized MCP tools decoupled from the database layer, allowing secure tool execution by AI agents.
Agentic AI Orchestrator: Multi-agent ReAct workflow incorporating dynamic tool discovery, multi-step execution, and reflection/validation before responses.
Security: JWT authentication, hashed credentials, input validation with Pydantic, CORS protections, and audit logging.
Related MCP server: Enterprise MCP Gateway and Tool Registry
š Project Structure
unifound/
āāā backend/ # FastAPI REST API, SQLAlchemy ORM, JWT Auth, Alembic
āāā frontend/ # React, Vite, TypeScript, modern responsive UI
āāā ai/ # AI/ML matching engine and Agentic ReAct orchestrator
āāā mcp_server/ # Model Context Protocol server exposing UniFound tools
āāā tests/ # End-to-end and integration test suites
āāā docs/ # Architectural specifications, API specs, and diagrams
āāā .env.example # Example environment variables
āāā .gitignore # Git ignore rules
āāā README.md # Master project documentationš ļø Tech Stack
Frontend: React 19, TypeScript, Vite, Modern Vanilla CSS Design System with Glassmorphism
Backend: Python 3.11+, FastAPI, SQLAlchemy 2.0, Pydantic v2, Alembic
Database: PostgreSQL (Production) / SQLite (Development & Testing)
Security: OAuth2 with JWT (HS256), Password hashing with Passlib/Bcrypt
Protocol & Agents: Model Context Protocol (MCP), Agentic ReAct Multi-Agent System
š¦ Phase Status
Phase 1: Project Foundation, Architecture, & Authentication System
Phase 2: Production Database Layer (SQLAlchemy 2.0, Alembic, 5 Core Models)
Phase 3: Production Authentication & Authorization (Hardened JWT, RBAC Guards, /users/me)
Phase 4: Lost & Found Core Module (Reporting, My Reports, Image Upload, Audit Logging)
Phase 5: Search & Filtering Engine (Database-level, Pagination, Full Faceting)
Phase 6: Ownership Claims & Admin Management (Claim Lifecycle, Notifications, Admin Queue)
Phase 7: React Frontend Completion & UX (User Dashboard, Admin Stats, Notifications Hub)
Phase 8: AI/ML Item Matching (Deterministic Multi-Factor Scoring, 0-100 Confidence, Potential Matches UI)
Phase 9: AI Image Analysis (Local Vision Provider, Visual Attributes, 10% Visual Match Boost)
Phase 10: Dedicated UniFound MCP Server & Client Integration (Official Python MCP SDK, 6 Tools, Dynamic Discovery, Auth Context)
Phase 11: Agentic AI ReAct Orchestrator (ReAct Loop, LLM Gateway, Reflection Agent, Multi-Step Tool Execution)
Phase 12: Notifications & Admin Analytics (Event-Driven Alerts, Match Alerts, Parameterized SQL Aggregation, Deep Horizon Analytics)
Phase 13: Security & Production Hardening (Fail-Fast Secrets, Rate Limiting, HTTP Security Headers, Pillow Verification, Prompt Injection Defense, 158/158 Passing Tests)
Phase 14: Comprehensive QA, Reliability & End-to-End Validation (17-Step User Flow, 12-Step Admin Flow, Authorization Matrix, State Transitions, 168/168 Passing Tests, QA Report)
Phase 15: Deployment & Final Validation (Production Configuration, PostgreSQL DDL Verification, Live ASGI & Frontend Deployment, 14-Step Live Smoke Test, Final Deployment Report)
š Production Deployment (Phase 15)
1. Environment & Database Configuration
Copy the production configuration template:
cp .env.production.example .envEnsure strong values are configured:
DATABASE_URL:postgresql://user:password@host:5432/unifound_productionSECRET_KEY: Cryptographically secure secret (minimum 32 characters)ENVIRONMENT:productionDEBUG:False
2. Run Database Migrations (PostgreSQL)
cd backend
alembic upgrade head3. Launch Backend (ASGI Production Server)
cd backend
uvicorn app.main:app --host 0.0.0.0 --port 8000 --workers 4 --log-level infoHealth check is available at GET /health or GET /api/v1/health.
4. Build and Serve Frontend
cd frontend
npm run build
# Serve dist/ using Nginx, Caddy, or static hostFor detailed validation metrics and audit results, see docs/PHASE_15_DEPLOYMENT_REPORT.md.
ā” Getting Started (Local Development)
1. Backend Setup
cd backend
python -m venv venv
# On Windows:
.\venv\Scripts\activate
# On Linux/macOS:
source venv/bin/activate
pip install -r requirements.txt
uvicorn app.main:app --reload --port 8000API docs will be available at http://localhost:8000/docs.
2. Frontend Setup
cd frontend
npm install
npm run devFrontend application will be accessible at http://localhost:5173.
This server cannot be deployed
Maintenance
Related MCP Connectors
Find, vet, and run MCP tools through a secure audited gateway with prompt-injection risk scoring
Pay-per-use tool marketplace for AI agents. Search, price-check, and call APIs via MCP.
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
Give AI agents identity, scoped access, trusted context, and verifiable actions through MCP.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables file system operations, web scraping, and AI-powered search through MCP tools for use by LLM agents.1-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to discover and execute tools via a secure MCP server with JWT authentication, RBAC, rate limiting, and audit logging.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to access a unified catalog of tools from various APIs (OpenAPI, GraphQL, MCP, Google Discovery) through the MCP protocol.173 npmMIT
- AlicenseAqualityDmaintenanceExposes Azure AI Foundry agents, workflows, and AI Search vector-database capabilities as MCP tools, enabling natural language interaction with agents, semantic search, and index management.102MIT