Back to the tool index

create_api_key

13 servers reported a tool by this name when we called them. Names are chosen by whoever wrote the server, so two tools sharing a name do not have to do the same thing. We record what was reported, not what it does.

serverresult when we called ittools
BorealHost
https://borealhost.ai/mcp/
answers-mcp 152
redu-cloud-mcp
https://mcp.redu.cloud/mcp
answers-mcp 81
echorelay-mcp
https://mcp.echorelay.dev
answers-mcp 79
agentView MCP
https://agentview.de/mcp
answers-mcp 57
PredMCP
https://predmcp.com/mcp
answers-mcp 52
keywordise
https://keywordise.com/mcp
answers-mcp 49
com.scriptivox.www/transcription
https://platform.scriptivox.com/mcp
answers-mcp 39
lastping-mcp
https://mcp.lastping.dev
answers-mcp 36
squirrelscan
https://mcp.squirrelscan.com/mcp
answers-mcp 20
recall-kitchen-mcp
https://app.recallkitchen.com/mcp
answers-mcp 19
ai-cortex-storage
https://memory.aic0rt3x.dev/mcp
answers-mcp 15
watchtower-sanctions-screening
https://watchtower-api.com/mcp
answers-mcp 13
auto-reader-ocr
https://api.auto-reader.com/mcp
answers-mcp 7

13 of these answered an MCP handshake on the day we checked. That is not a promise the tool works, only that the server was running and told us the tool existed.