verify_contract — New MCP Server Directory (Agent Tools Index) MCP Tool
verify_contract
(verify contract) is one of 16 tools on the
New MCP Server Directory (Agent Tools Index)
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call verify_contract from your client
- Claude Code New MCP Server Directory (Agent Tools Index) verify_contract run in your project directory
- Claude Desktop New MCP Server Directory (Agent Tools Index) verify_contract ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor New MCP Server Directory (Agent Tools Index) verify_contract ~/.cursor/mcp.json
- VS Code New MCP Server Directory (Agent Tools Index) verify_contract .vscode/mcp.json
- Zed New MCP Server Directory (Agent Tools Index) verify_contract ~/.config/zed/settings.json
- Windsurf New MCP Server Directory (Agent Tools Index) verify_contract ~/.codeium/windsurf/mcp_config.json
- Cline New MCP Server Directory (Agent Tools Index) verify_contract ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI New MCP Server Directory (Agent Tools Index) verify_contract ~/.gemini/settings.json
- Grok New MCP Server Directory (Agent Tools Index) verify_contract .mcp.json (in your project root)
- ChatGPT New MCP Server Directory (Agent Tools Index) verify_contract Settings → Connectors → Advanced → Developer mode
- Claude.ai New MCP Server Directory (Agent Tools Index) verify_contract Settings → Connectors → Add custom connector
- LangChain New MCP Server Directory (Agent Tools Index) verify_contract pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http data-new-mcp-server-agent-tools-index https://a2awire.com/mcp/data/new-mcp-server-directory-agent-tools-index-8f68ac/http
Other tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.