io.github.kody-w/rapp-agent-builder
REMOTE · RAPP-AGENT-BUILDER.AZUREWEBSITES.NET
Turn an idea or meeting transcript into a working single-file AI agent, check it, use it right away.
Available components
Last scanned (7 hours ago)
Scores higher than 68% of remote servers
Reachable. Last reached 23 Oct 2026.
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 842 tokens (~105/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 27. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 7 to 17. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: rapp-agent-builder → agent-builder security
- Tool “check_agent” rewrote its description, which is the text the model reads security
- Tool “find_agents” rewrote its description, which is the text the model reads security
- Tool “get_agent_template” rewrote its description, which is the text the model reads security
- Tool “how_to_run_agent” rewrote its description, which is the text the model reads security
- Tool “share_agent” rewrote its description, which is the text the model reads security
- Schema quality: 718 → 842 ▼ functional
- Stability: unverified → 0.07 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://rapp-agent-builder.azurewebsites.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.azurewebsites.net,O=Microsoft Corporation,L=Redmond,ST=WA,C=US | CN=Microsoft TLS G2 RSA CA OCSP 02,O=Microsoft Corporation,C=US | 11 Oct 2026 | 19 Jan 2027 | RSA 2048 | SHA384-RSA | 41012e0d4dce49ebe46d640e900000012e0d4d |
| SANs: *.azurewebsites.net, *.scm.azurewebsites.net, *.sso.azurewebsites.net, *.eastus2-01.azurewebsites.net, *.scm.eastus2-01.azurewebsites.net, *.sso.eastus2-01.azurewebsites.net, *.eastus2.c.azurewebsites.net, *.scm.eastus2.c.azurewebsites.net, *.sso.eastus2.c.azurewebsites.net, *.02.eastus2.c.azurewebsites.net, *.scm.02.eastus2.c.azurewebsites.net, *.sso.02.eastus2.c.azurewebsites.net and 18 more | ||||||
| CN=Microsoft TLS G2 RSA CA OCSP 02,O=Microsoft Corporation,C=US (CA) | CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US | 1 Aug 2025 | 3 Jun 2029 | RSA 4096 | SHA384-RSA | 330000000c4964a16f44203b2200000000000c |
| CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 21 May 2025 | 19 Jun 2029 | RSA 4096 | SHA384-RSA | b0c6b2c466917b04773c647d4afc0c8 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of rapp-agent-builder.azurewebsites.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| azurewebsites.net. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://rapp-agent-builder.azurewebsites.net/mcp | Verified | 200 | |
| http (plaintext) | http://rapp-agent-builder.azurewebsites.net/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_agent Check an agent file ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The full Python source of the agent file |
| filename | string | yes | File name, must end with _agent.py, e.g. invoice_triage_agent.py |
No output schema declared.
No examples provided.
find_agents Find existing agents ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many results, default 5 |
| query | string | yes | Plain words describing the task, e.g. 'summarize sales calls' |
No output schema declared.
No examples provided.
get_agent_code Get an agent's code ~60
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Registry name, e.g. @kody/memory_agent |
No output schema declared.
No examples provided.
get_agent_template Get the agent template ~115
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
how_to_run_agent Keep an agent running on your computer ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | – | The agent file name, if known |
| os | string | – | The user's operating system |
No output schema declared.
No examples provided.
request_service Ask us to build something ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| request | string | yes | What they want, in a sentence, as they agreed to send it |
No output schema declared.
No examples provided.
share_agent Share an agent with everyone ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The full Python source of the agent |
| filename | string | yes | Agent file name, ending in _agent.py |
No output schema declared.
No examples provided.
use_agent_here Use the agent in this chat ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | – | The agent file name, e.g. invoice_triage_agent.py |
No output schema declared.
No examples provided.
How do I install the io.github.kody-w/rapp-agent-builder MCP server?
io.github.kody-w/rapp-agent-builder is a hosted endpoint at https://rapp-agent-builder.azurewebsites.net/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · rapp-agent-builder.azurewebsites.net
claude mcp add --transport http kody-w-rapp-agent-builder 'https://rapp-agent-builder.azurewebsites.net/mcp'
What is the io.github.kody-w/rapp-agent-builder MCP server?
io.github.kody-w/rapp-agent-builder is an MCP server listed in the public MCP registry as 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. This page covers its hosted endpoint (https://rapp-agent-builder.azurewebsites.net/mcp).
Is the io.github.kody-w/rapp-agent-builder MCP server safe to use?
io.github.kody-w/rapp-agent-builder scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.kody-w/rapp-agent-builder MCP server expose?
io.github.kody-w/rapp-agent-builder exposes 8 tools: get_agent_template, check_agent, find_agents, get_agent_code, use_agent_here, and 3 more. Their descriptions and schemas cost roughly 748 tokens of context every time the server is loaded.
Does the io.github.kody-w/rapp-agent-builder MCP server require authentication?
No. We connected to io.github.kody-w/rapp-agent-builder without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.kody-w/rapp-agent-builder MCP server still maintained?
io.github.kody-w/rapp-agent-builder is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.