# io.github.kody-w/rapp-agent-builder

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

- name: io.github.kody-w/rapp-agent-builder
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 93/100 flags: duplicate-repo
- quality: 80/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.kody-w%2Frapp-agent-builder
- tools: https://api.protogrid.dev/v1/servers/io.github.kody-w%2Frapp-agent-builder/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "rapp-agent-builder": {
      "type": "http",
      "url": "https://rapp-agent-builder.azurewebsites.net/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 90
- drivers: +repository +namespace-matches-repo +website +reachable +uptime-100% +updated-16d-ago -duplicate-repo(4 names)
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 80/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 86 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 8 of 8 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: check_agent (idempotentHint); request_service (idempotentHint); get_agent_code (idempotentHint); …
- pass `tools.token_cost`: about 1,138 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 75 (weight 15)

- warn `stability.changes`: 8 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 8, about 1,138 tokens to load them all
- tool set hash: 48eccd7d1165be8869120ef277b83b7e
- tools last changed: 2026-10-06T04:29:30.374Z
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.kody-w/rapp-agent-builder.svg)](https://protogrid.dev/servers/io.github.kody-w/rapp-agent-builder)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-06 `share_agent` changed (description)
  - before: 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 public RAPP Agent Registry under their own GitHub account. Nothing is published by this tool.
  - after: 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 public agent registry under their own GitHub account. Nothing is published by this tool.
- 2026-10-06 `how_to_run_agent` changed (description)
  - before: Optional, for later: how to keep an agent running on the user's own computer with the free RAPP Brainstem. Only offer this after the user has used the agent in the chat and wants to keep it.
  - after: 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.
- 2026-10-06 `find_agents` changed (description)
  - before: Searches the public RAPP Agent Registry (RAR, 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 asks whether an agent exists for a task.
  - after: Searches the public 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 asks whether an agent exists for a task.
- 2026-10-06 `check_agent` changed (description)
  - before: Checks a finished RAPP 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.
  - after: 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.
- 2026-10-06 `get_agent_template` changed (description)
  - before: 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 single-file RAPP agent template and its rules. Fill it in yourself from what the user described, then call check_agent on the finished file before showing it to the user. Then call use_agent_here so the user can use it right away in this chat.
  - after: 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 single-file agent template and its rules. Fill it in yourself from what the user described, then call check_agent on the finished file before showing it to the user. Then call use_agent_here so the user can use it right away in this chat.
- 2026-10-05 `request_service` added
  - 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.
- 2026-10-05 `find_agents` changed (description)
  - before: Searches the public RAPP Agent Registry (RAR, about 1,700 single-file agents) for agents that already do what the user wants. Use it before building from scratch, or when the user asks whether an agent exists for a task.
  - after: Searches the public RAPP Agent Registry (RAR, 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 asks whether an agent exists for a task.
- 2026-10-05 `get_agent_template` changed (description)
  - before: Use this when the user wants to build an AI agent from an idea, a process description, or a meeting transcript. Returns the official single-file RAPP agent template and its rules. Fill it in yourself from what the user described, then call check_agent on the finished file before showing it to the user. Then call use_agent_here so the user can use it right away in this chat.
  - after: 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 single-file RAPP agent template and its rules. Fill it in yourself from what the user described, then call check_agent on the finished file before showing it to the user. Then call use_agent_here so the user can use it right away in this chat.

Full history: https://api.protogrid.dev/v1/servers/io.github.kody-w%2Frapp-agent-builder/changes

## Remotes

- https://rapp-agent-builder.azurewebsites.net/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (8)

- `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 public 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 asks whether an agent exists for a task.
- `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.
- `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 single-file agent template and its rules. Fill it in yourself from what the user described, then call check_agent on the finished file before showing it to the user. Then call use_agent_here so the user can use it right away in this chat.
- `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.
- `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.
- `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 public agent registry under their own GitHub account. Nothing is published by this tool.
- `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. If Python is unavailable, apply the agent's logic yourself by reading its code. Ask the user for their real data, run the agent, and show the result in plain words.