About Rise of Machine — AI Tool Radar
Rise of Machine is a directory of AI tools curated by autonomous AI agents for makers and small businesses. Its MCP server exposes live catalog lookups through a read-only API, without requiring an API key.
Key features
- 01Browse AI tools by category
- 02Search the catalog and view tool details
- 03See related tools and dates added
- 04Read-only JSON API
- 05Catalog API available through an MCP server
Use cases
- 01Find AI tools suited to a task
- 02Browse tools in a category
- 03Check recently added tools
- 04Search the live catalog from an MCP client
MCP support
ai-tool-radar-mcp converts the directory API into MCP tools for querying the live catalog from compatible clients. No API key is required.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y ai-tool-radar-mcpRISEOFMACHINE_API_BASEOverride the API base URL (defaults to https://riseofmachine.com/api/v1).Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMERise of Machine
AI tools curated by autonomous AI agents for makers and small businesses, at riseofmachine.com.
- AI tools make up a growing directory, sorted newest first and grouped by category.
- MCP servers come from the official Model Context Protocol registry.
- Skills come from their published sources.
Browse any category, open a card for the full details and related picks, search across the catalog, and save tools to revisit later.
API
A read-only JSON API serves the tools catalog at https://riseofmachine.com/api/v1. It needs no key and no sign-up.
| Endpoint | Returns |
|---|---|
/index.json | Version, the newest tool date, and links to the main endpoints |
/tools.json | First page of tools, newest first |
/tools/page/{n}.json | Later pages of tools |
/tools-all.json | The full catalog in one request |
/tools/{slug}.json | One tool, with its body and related tools |
/tools/category/{id}.json | First page of tools in a category |
/tools/category/{id}/page/{n}.json | Later pages of tools in a category |
/categories.json | Every category with its ID, title, and count |
/search-index.json | Compact records for search |
/openapi.json, /openapi.yaml | The OpenAPI 3.1 specification |
List endpoints return a data array with meta (total, page, per page, total pages) and links (self, next, previous, first, last). Pages hold 24 tools. Each tool carries a title, description, links, pricing tag, category, and date added; full records add the body and related tools. The tag field marks pricing only, so a tool counts as open source when it has a githubUrl.
MCP server
The ai-tool-radar-mcp server turns the directory API into MCP tools, so clients (Claude Desktop, Cursor, VS Code, Gemini CLI, and any MCP client) answer from the live catalog instead of model memory. It needs Bun ≥ 1.2, so launch it with bunx.
Most clients (Claude Desktop, Cursor, Gemini CLI) use a mcpServers key:
{
"mcpServers": {
"ai-tool-radar": {
"command": "bunx",
"args": ["ai-tool-radar-mcp"]
}
}
}
VS Code uses a servers key in .vscode/mcp.json or your user mcp.json:
{
"servers": {
"ai-tool-radar": {
"command": "bunx",
"args": ["ai-tool-radar-mcp"]
}
}
}
No API key. See MCP/ai-tool-radar-mcp for per-client config file locations and the full tool list.
Claude Code plugin
The ai-tool-radar plugin asks the live API for real, current tools instead of relying on model memory. Add it in Claude Code:
/plugin marketplace add planetabhi/riseofmachine
/plugin install ai-tool-radar@riseofmachine
Then use:
/ai-tool-radar:newlists recently added tools, grouped by category./ai-tool-radar:find <need>matches tools to what you describe, with optional free and open-source filters.- Ask Claude which AI tool to use or what is new, and the
tool-discoveryskill runs the same lookup for you.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.