Alternatives
Products that do what OQP – A verification protocol for AI agents does
As AI agents autonomously write and deploy code, there's no standard for verifying that what they shipped actually satisfies business requirements. OQP is an attempt to define that standard. It's MCP-compatible and defines four core endpoints: - GET /capabilities — what can this agent verify? - GET /context/workflows — what are the business rules for this workflow? - POST /verification/execute — run a verification workflow - POST /verification/assess-risk — what is the risk of this change? The analogy we keep coming back to: what OpenAPI did for REST APIs,…
- 1
- 2
- 3
Author here! Agents are applying to jobs for people right now, with progressively more volume, and there's nothing built for it. So they scrape career pages and fight ATS forms with Playwright/Browser Use, which breaks constantly (or they get bot blocked). Employers get buried in applications that don't fit, candidates hear nothing back, and the resume is now an AI-written thing that another AI scores (which breaks the existing model entirely, btw). OJCP is MCP tools for search and apply, a manifest at /.well-known/ojcp.json so agents can find providers, and schemas that…
25d ago · ojcp.dev
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19IB
TLDR: OpenAPI-MCP is a Dockerized server that dynamically generates Model Context Protocol (MCP) tool definitions directly from your Swagger/OpenAPI documentation. It allows your AI agent to seamlessly access any API without additional coding, streamlining development and eliminating repetitive manual setup. For more details, code updates-----: GitHub: ckanthony/openapi-mcp Docker Hub: ckanthony/openapi-mcp
2025 · github.com
- 20CD
Hey folks, I've been building AI agents that need to talk to various APIs, and I got tired of writing custom integrations for every service. So I built the MCP-OpenAPI Server to solve this problem! It's a simple bridge that lets AI agents discover and use our existing OpenAPI endpoints through the Model Context Protocol. No need to write custom code for each service - just point it at the OpenAPI specs, choose which endpoints to expose, and you're good to go. What makes this different from other MCP servers is that it uses SSE transport instead of stdio, making it work well for multi-tenant…
2025 · github.com
- 21MC
Hey HN, OpenAI released the Agents SDK yesterday, which is great because of its simplicity. I just added MCP support for it, which is currently available as a fork here: https://github.com/lastmile-ai/openai-agents-mcp (and on pypi as the openai-agents-mcp package). You can specify the names of MCP servers to give an Agent access to by setting its `mcp_servers` property. The Agent will then automatically aggregate tools from the MCP servers, as well as any `tools` specified, and create a single extended list of tools. This means you can seamlessly use MCP servers, local…
2025
- 22
- 23
- 24MM
Hey HN! I’m Gui from deco (decocms.com). We’ve been using this tool internally as the foundation for a few customer AI platforms, and today we’re open-sourcing it as MCP Mesh. MCP is quickly becoming the standard for agentic systems, but… once you go past a couple servers it turns into the same problems for every team: - M×N config sprawl (every client wired to every server, each with its own JSON + ports + retries) - Token + tool bloat (dumping tool definitions into every prompt doesn’t scale) - Credentials + blast radius (tokens scattered across clients, hard to audit, hard to revoke) - No…
Dec 2025 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →