Rose Bounty

org.agttglobalPublished by agttglobal.orgOfficial publisherv1.0.0Updated Oct 24, 2026

AI-agent trust infrastructure for discovery, authority, execution, verification, and receipts.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Connects an assistant to Rose Bounty, a remote AI-agent trust infrastructure service, using a member key for access.

What you can do
Rose Bounty is a remote MCP endpoint described as AI-agent trust infrastructure covering discovery, authority, execution, verification, and receipts. The manifest lists no tools, so the specific operations an assistant can call are not documented here. Access is gated by a required membership credential sent in a header.
When to use it
Consider it when you want an assistant to work with an agent trust layer that handles discovery, authority checks, execution, verification, and receipts, and you already hold an approved membership credential. Because no tools are listed, confirm the available capabilities before relying on it.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. A required Rose Passport membership credential must be supplied in the X-Rose-Member-Key header. Network access to the remote endpoint is required.
Before you install
The server requires a secret membership credential in the X-Rose-Member-Key header; keep it private and avoid exposing it in logs or shared configuration. The manifest lists no tools, so what the server reads, writes, or sends to third parties cannot be verified from this listing. Review the provider's terms before connecting.

Installation

In SourceWeft

  1. Open Rose Bounty in the dashboard and add it to a workspace.
  2. Connect X-Rose-Member-Key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/org.agttglobal%2Frose-bounty/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "rose-bounty": {
      "type": "http",
      "url": "https://rose.agttglobal.org/mcp",
      "headers": {
        "X-Rose-Member-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 27, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.