Prioritize an existing Italian B2B lead list into up to 250 explained JSON decisions.
Use this profile to copy client config, check auth requirements, review tools and resources, and compare related MCP servers before adding it to an AI client.
Get practical integration notes and launch examples for MCP servers like Italian B2B Lead List Scoring, Ranking & JSON Decisions.
https://mcp.machinesignal.it/mcpAdd this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"it-machinesignal-discovery": {
"url": "https://mcp.machinesignal.it/mcp"
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
Italian B2B Lead List Scoring, Ranking & JSON Decisions is an MCP server for Prioritize an existing Italian B2B lead list into up to 250 explained JSON decisions.. It supports HTTP transport.
Use the generated config in Install. It points your client at the advertised remote endpoint shown on this page.
Choose the Claude Desktop tab in Install, copy the config, and add it to Claude Desktop's MCP server settings. Endpoint: https://mcp.machinesignal.it/mcp.
Choose the Claude Code tab in Install, copy the config, and add it to Claude Code's MCP server settings. Endpoint: https://mcp.machinesignal.it/mcp.
Choose the Codex tab in Install, copy the config, and add it to Codex's MCP server settings. Endpoint: https://mcp.machinesignal.it/mcp.
Choose the Cursor or VS Code tab in Install, copy the config, and add it to Cursor or VS Code's MCP server settings. Endpoint: https://mcp.machinesignal.it/mcp.
Italian B2B Lead List Scoring, Ranking & JSON Decisions uses HTTP transport. Endpoint: https://mcp.machinesignal.it/mcp.
Italian B2B Lead List Scoring, Ranking & JSON Decisions inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
Italian B2B Lead List Scoring, Ranking & JSON Decisions does not advertise a verified auth requirement. If discovery fails, it may still need provider login, an API key, a bearer token, or a session header.