Agentdataboundary MCP

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:

Authorization: Bearer <token>

Unauthenticated browser requests to the MCP path return a JSON error rather than exposing internal details. This service is hosted remotely and paid; it is not presented as a locally installed server in the provided material.

The agentdataboundary-mcp MCP server exposes four operations: map_permissions, flag_sensitive_fields, summarize_boundary, and export_remediation_plan. The README lists their names but does not specify their request schemas, response formats, or detailed behavior, so integrations should consult the service documentation or server card before implementing against them.

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.

No environment variable names or local configuration files are documented in the supplied material. 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. The supplied README does not document field-level semantics or whether the tools connect to a particular third-party data system.

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. The repository itself is not the production implementation, and the available material does not provide tool schemas, pricing details, token lifetime information, rate limits, or client-specific setup instructions.

The README also mentions OpenHuman Online as a related option when a rollout needs human-readable source memory, meeting notes, or approval context outside this server. That service is described as related workflow context, not as a dependency of the MCP endpoint.