Skip to main content
Some tools come from external servers over the Model Context Protocol (MCP), an open standard for exposing tools to language models. Neo connects to these servers when a task starts and merges their tools into the agents that need them.

​
What it includes

  • Code search: search across open-source repositories to find real-world usage, vulnerable patterns, and reference implementations
  • OpenAPI tools: ingest and work with OpenAPI specifications tied to your ProjectDiscovery account, used by the API Security Agent

​
How it fits in

MCP tools are wrapped with the same safety guarantees as every other tool, including timeouts, output truncation, and secret redaction. They are loaded per task and given only to the agents that need them, so they stay out of the way of unrelated work. If an MCP server is unavailable, the agent continues to run with its remaining tools rather than failing. This keeps tasks resilient even when an external dependency is down.