VendorOps MCP
VendorOps MCP
VendorOps is a Model Context Protocol (MCP) server for a synthetic internal vendor-management workflow. It gives AI applications structured access to vendor records, contracts, spending, renewals, and security reviews.
The project is intentionally built in small, reviewable slices. Phase 1 uses Python, the official MCP Python SDK, SQLite, Pydantic, and pytest to expose read-only vendor data over a local stdio connection.
All vendor and contract data in this repository is synthetic.
Development
Install the locked dependencies:
uv syncRun the test suite:
uv run pytestRun the local stdio server:
uv run vendorops-mcpThe server waits for an MCP host to send protocol messages over stdin. It does not open a network port or print a user interface.
By default, VendorOps creates data/vendorops.db and seeds it with 30 synthetic
vendors. Set VENDOROPS_DB_PATH to use a different SQLite file.
Current MCP Capabilities
Tools
search_vendors: Search vendor records by name, category, or owner, with optional category and status filters.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jacwalste/vendorops-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server