LAST UPDATED JUNE 20, 2026 · ANTHROPIC CONNECTOR DIRECTORY
Connector Directory Compliance
This page documents how Exigyn meets the requirements of Anthropic's Software Directory Policy for our remote MCP connector. It is intended for Anthropic reviewers and users evaluating the Exigyn connector for Claude.
1. Safety and Security
The Exigyn connector complies with Anthropic's Usage Policy and does not facilitate violations of it. The connector does not circumvent Claude's safety guardrails, system instructions, or sandbox environments. All behavioral instructions are human-readable and transparently defined — there are no hidden, obfuscated, or encoded instructions. The connector does not dynamically pull behavioral instructions from external sources.
Data minimization: The connector accesses only the Exigyn organization data required to fulfill each user request. It does not collect extraneous conversation data and does not read Claude memory, chat history, conversation summaries, or user-uploaded files. All data is scoped to the authenticated user's organization via row-level security.
The connector does not infringe intellectual property rights, does not serve advertisements or sponsored content, and does not execute financial transactions on behalf of users.
2. Compatibility
Each tool exposed by the Exigyn connector is defined with a narrow, unambiguous description specifying exactly what it does and when it should be invoked. Tool descriptions precisely match actual functionality — there are no promised features that are undelivered and no unexpected side effects.
The connector does not intentionally call or coerce Claude into invoking other external software, databases, or resources beyond what a user explicitly requests. It does not interfere with Claude's ability to call tools from other connectors and does not redirect Claude's behavior through external instruction sources.
3. Developer Requirements
Privacy policy: Exigyn maintains a public privacy policy at exigyn.com/privacy covering what data the connector collects, how it is used, where it is stored, how long it is retained, and how users can exercise their rights. The policy is presented during the OAuth authorization flow.
Support contact: Users with product or security concerns can reach Exigyn at support@exigyn.com. Security researchers may use security@exigyn.com. Response SLAs are documented on our Support page at exigyn.com/support.
Documentation: Exigyn maintains setup and usage documentation at exigyn.com/docs, including how the connector authenticates, which tools are available, what each tool does, and how to troubleshoot common issues.
Testing account: A standard testing account with sample data has been provided to Anthropic reviewers to verify full connector functionality end to end. Reviewer credentials and step-by-step access instructions are included in the submission form.
Working examples: Three representative prompts demonstrating core connector functionality are provided in the submission and documented at exigyn.com/docs: (1) "What is our current cash runway across scenarios?" — (2) "Generate a budget vs. actuals variance report for Q2" — (3) "Show me the workforce GL forecast for our base-case scenario."
Ownership: Exigyn, LLC owns and controls all API endpoints, domains, and interfaces the connector connects to, including the MCP server at mcp-sandbox.exigyn.com and the Exigyn platform at start.exigyn.com.
Maintenance: Exigyn commits to maintaining the connector and addressing issues within commercially reasonable timeframes. Exigyn has agreed to the Anthropic Software Directory Terms.
4. MCP Server Technical Requirements
Error handling: All tools return structured, actionable error messages with context. Generic errors are caught and surfaced with user-facing guidance rather than raw stack traces.
Token frugality: Tool responses are scoped and paginated. The connector returns only the data necessary to fulfill each request and does not return unfiltered database contents. Tools accept filtering parameters to limit response size where appropriate.
Tool name length: All tool names are under 64 characters.
Authentication: The connector uses secure OAuth 2.0 over HTTPS with certificates from a recognized certificate authority. Each user completes a consent flow. The authorization server supports Dynamic Client Registration and Client ID Metadata Document flows.
Tool annotations: All tools include a title and the applicable readOnlyHint or destructiveHint annotation per the MCP specification (2025-11-25 schema). Read-only tools carry readOnlyHint: true. Tools that write, create, or update data carry destructiveHint with appropriate user-facing warnings.
Transport: The connector supports Streamable HTTP as the primary transport, with SSE transport supported for compatibility during the deprecation period.
5. Unsupported use cases — Exigyn does not do any of the following
Transfer money, cryptocurrency, or financial assets, or execute financial transactions on behalf of users. Generate images, video, or audio using AI models. Serve advertisements, sponsored content, or paid product placements. Read or query Claude's memory, chat history, conversation summaries, or uploaded files. Collect conversation data beyond what is necessary to route and fulfill a user's request. Operate in countries or regions not supported by Anthropic.
Key documents and contacts
Privacy: privacy@exigyn.com · Security disclosures: security@exigyn.com · General support: support@exigyn.com