90trust / 100

Raptr Agent Builder

by airaptr-api.azurewebsites.net in AI models & inference

MCP serverPassing, checked 3 h ago

Turn an idea or meeting transcript into a working single-file AI agent, check it, use it right away.

https://airaptr-api.azurewebsites.net/mcp

Last 30 days

All checks passedSome failedAll failedNot checked
Uptime
100%
Response time
132 ms typical, 132 ms slowest 5%
Last check
3 h ago
Next check
in 3 h

How to call it

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "raptr-agent-builder": {
      "type": "http",
      "url": "https://airaptr-api.azurewebsites.net/mcp"
    }
  }
}

8 tools

  • get_agent_template

    Use this when the user wants to build an AI agent, assistant, bot or automation from an idea, a repetitive task, a process description, or a meeting transcript (for example: automate invoices, triage support tickets, summarize meetings, follow up with leads). Returns the official

  • check_agent

    Checks a finished agent file against the template rules (manifest, naming, class, perform method, no hardcoded secrets). Call it on every agent you write, fix anything it reports, and call it again until it passes.

  • find_agents

    Searches the open agent registry (about 1,700 single-file agents) for agents that already do what the user wants, for example when they ask 'is there an AI tool for...' or want a ready-made automation instead of building one. Use it before building from scratch, or when the user

  • get_agent_code

    Returns the full source of one agent from the registry, by its name (e.g. @bill/neuron_agent), so it can be read or adapted.

  • use_agent_here

    Use this right after an agent passes check_agent, or whenever the user wants to try an agent. Returns a short Python runner so you can run the agent in this chat with your own Python tool on the user's own data (pasted text, an uploaded spreadsheet, a list). Nothing to install. I

  • how_to_run_agent

    Optional, for later: how to keep an agent running on the user's own computer with the free Brainstem. Only offer this after the user has used the agent in the chat and wants to keep it.

  • share_agent

    Use only when the user says they want to share an agent they built. Checks the agent and scans it for personal details (emails, phone numbers, secrets), then explains how to publish it to the free open agent registry under their own GitHub account. Nothing is published by this to

  • request_service

    Use when the person wants something none of these tools can do and says yes to passing the request on. Records only the request text they agree to send (no name or contact). Ask before calling it.

Security scan

  • No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTime
3 h agoPassed200132 ms