Skip to content

raptr-agent-builder MCP server

io.github.kody-w/raptr-agent-builderkody-wstreamable-httpv1.0.0Scanned

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

9 tools: 5 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 5 write, 4 read.
  • Reads private data · 3
  • Reads text others write · 4
  • Can send data out · 0
  • 3 findings

Tools listed without sign-in. Remote posture

With Anlyon

5 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the raptr-agent-builder MCP server can do

The raptr-agent-builder MCP server is published by the GitHub account kody-w. It has 9 tools. It can create or change data (5 tools: check_agent, use_agent_here, how_to_run_agent, share_agent and 1 more), but cannot delete data. 4 tools only read.

3 tools read private data (get_agent_template, find_agents and rejection_rescue_preview); 4 tools bring in text other people can write (get_agent_template, find_agents, get_agent_code and 1 more).

The fixed checks matched 3 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Changes things 5Claude Code: ask
  • check_agentChecks a finished agent file against the template rules (manifest, naming, class, perform method, no hardcoded secrets).1 finding

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "check_agent" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • how_to_run_agentOptional, for later: how to keep an agent running on the user's own computer with the free Brainstem.1 finding

    Why it is in this group

    • The name "how_to_run_agent" says "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "how_to_run_agent" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "how_to_run_agent" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • request_serviceUse when the person wants something none of these tools can do and says yes to passing the request on.No findings

    Why it is in this group

    • The name "request_service" says "request": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • share_agentUse only when the user says they want to share an agent they built.1 finding

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "share_agent" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.

      What this check looks for
    Description, as the server wrote it
    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 tool.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • use_agent_hereUse this right after an agent passes check_agent, or whenever the user wants to try an agent.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
Only reads 4Show 4 read-only tools
  • find_agentsSearches 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 r…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "find_agents" says "find": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "search" and "file": it reads files.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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 asks whether an agent exists for a task.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • get_agent_codeReturns the full source of one agent from the registry, by its name (e.g.Reads text others writeNo findings

    Why it is in this group

    • The name "get_agent_code" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • get_agent_templateUse 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: automa…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_agent_template" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "meeting": it reads calendars.
    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • rejection_rescue_previewUse when the user pastes a rejection message from Apple App Review (it cites guidelines such as "Guideline 5.1.1(i)").Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "rejection_rescue_preview" says "preview": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "message": it reads messages.
    • untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
    Description, as the server wrote it
    Use when the user pastes a rejection message from Apple App Review (it cites guidelines such as "Guideline 5.1.1(i)"). Free. Returns each cited guideline section it recognizes, with its title and what Apple means by it, and lists sections it does not know. The full version (likely causes, a fix list and a reply draft to App Review) is a separate paid HTTP call; the result says its price and route.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:07 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://airaptr-api.azurewebsites.net/mcp: tools/list returned 9 tools to an anonymous client, including check_agent (write), use_agent_here (write), how_to_run_agent (write), share_agent (write), request_service (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

3 warn
  • The server marks "check_agent" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.

    What this check looks for
  • The server marks "how_to_run_agent" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "how_to_run_agent" says "run": a word for a change.

    What this check looks for
  • The server marks "share_agent" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The input takes a statement or command to run (input.code), which can change anything it can reach.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http raptr-agent-builder https://airaptr-api.azurewebsites.net/mcp
claude mcp add --transport http raptr-agent-builder https://airaptr-api.azurewebsites.net/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__raptr-agent-builder__get_agent_template",
      "mcp__raptr-agent-builder__find_agents",
      "mcp__raptr-agent-builder__get_agent_code",
      "mcp__raptr-agent-builder__rejection_rescue_preview"
    ],
    "ask": [
      "mcp__raptr-agent-builder__check_agent",
      "mcp__raptr-agent-builder__use_agent_here",
      "mcp__raptr-agent-builder__how_to_run_agent",
      "mcp__raptr-agent-builder__share_agent",
      "mcp__raptr-agent-builder__request_service"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as raptr-agent-builder. Review it before you use it.

Capability tags behind 4 rules
  • mcp__raptr-agent-builder__get_agent_template private-data, untrusted-input
  • mcp__raptr-agent-builder__find_agents private-data, untrusted-input
  • mcp__raptr-agent-builder__get_agent_code untrusted-input
  • mcp__raptr-agent-builder__rejection_rescue_preview private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.kody-w/raptr-agent-builder/verify?hash=d22bcd1936fee00a6c3c9adbd3004b867b553d7237831eb4b7b9818134bb8c25" | jq -e '.changed == false'

Pinned hash d22bcd1936fe, from Nov 20, 2026, 01:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.kody-w/raptr-agent-builder/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.kody-w/raptr-agent-builder
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.kody-w/raptr-agent-builder.svg)](https://radar.anlyon.com/servers/io.github.kody-w/raptr-agent-builder)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:37 UTC.

raptr-agent-builder MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the raptr-agent-builder MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 5 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the raptr-agent-builder MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the raptr-agent-builder MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the raptr-agent-builder MCP server have?

9 tools: 5 write, 4 read. check_agent, use_agent_here, how_to_run_agent, share_agent, request_service, get_agent_template, find_agents, get_agent_code and 1 more.

Does the raptr-agent-builder MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the raptr-agent-builder MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the raptr-agent-builder MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.