# agentdataboundary-mcp [Health: Active]

**Category:** 🔒 Security  
**Repository:** https://github.com/clauxel/agent-data-boundary-mcp  
**GitHub Stars:** 0  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/agentdataboundary-mcp

## Description
Permission boundary receipts for ChatGPT agents.

## Tools
Capabilities this server exposes over MCP:

- **map_permissions**
- **flag_sensitive_fields**
- **summarize_boundary**
- **export_remediation_plan**

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "agentdataboundary-mcp": {
    "url": "https://agentdataboundary.clauxel.com/mcp"
  }
}
```

## Documentation

## What agentdataboundary-mcp does

The agentdataboundary-mcp MCP server provides a hosted service for reviewing how an agent may access data. Its stated scope includes permission boundary receipts, permission scope evidence, notes about sensitive data, and governance receipts. The service is intended for workflows that need a record of access boundaries and follow-up actions rather than direct access to an application database or file system.

The repository is a public documentation and directory-submission reference. It does not contain the private production implementation. The production service is available through the AgentData Boundary website and its remote MCP endpoint.

## How it works

The service accepts MCP requests over Streamable HTTP at `https://agentdataboundary.clauxel.com/mcp`. Clients send JSON-RPC requests to that endpoint. Production requests must include a bearer token in the HTTP authorization header:

```http
Authorization: Bearer <token>
```

Unauthenticated browser requests to the MCP path return a JSON error rather than exposing internal details.

The agentdataboundary-mcp MCP server exposes four operations: `map_permissions`, `flag_sensitive_fields`, `summarize_boundary`, and `export_remediation_plan`.

## Setup and configuration

Start by opening the product website, selecting a plan, and creating or requesting an API token. Add the remote endpoint to an MCP client that supports Streamable HTTP remote servers, then send JSON-RPC requests with the token attached as a bearer authorization header.

The required credential is the product-issued API token. The published server card is available at `https://agentdataboundary.clauxel.com/server-card.json`, and the registry name is `com.clauxel.agentdataboundary/agentdataboundary-mcp`.

## Tools and capabilities

- `map_permissions` for permission mapping workflows.
- `flag_sensitive_fields` for identifying sensitive-field concerns.
- `summarize_boundary` for producing boundary summaries.
- `export_remediation_plan` for exporting remediation plans.

Together, these tools cover permission mapping, sensitive-data review, boundary summarization, and remediation output.

## Limitations and notes

The agentdataboundary-mcp MCP server requires a paid hosted service and a production bearer token. It depends on an MCP client with Streamable HTTP remote-server support.

That service is described as related workflow context, not as a dependency of the MCP endpoint.

_Full upstream README: https://allmcps.com/mcp/agentdataboundary-mcp/readme_