# Account Closure Evidence Register AI Agent Connect

> Account Closure Evidence Register MCP manages the entire lifecycle of your account closure audits. It lets you register new requests, track their progress, and store formal proof once a service confirms a closure. You can use it to identify overdue tasks and keep your compliance records organized in one central place.

## Overview
- **Category:** productivity
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_ADYWA514cz5CSJwqmhxCIJLCLasr7OT4G6Vq6Ve3/ai-agent-connect
- **Tags:** account-closure, audit-trail, compliance-tracking, data-privacy, verification

## Description

Managing account closures shouldn't be a manual guessing game. This MCP gives you a centralized way to track every closure request from the moment it's initiated until you have hard evidence that the account is actually gone. Instead of digging through old emails or chat logs to prove a service was terminated, you record the formal evidence directly in the register. 

You can use your AI client to monitor the status of all pending requests or quickly pull up a list of accounts that need immediate attention because their follow-up date has passed. It's built to ensure nothing slips through the cracks during the offboarding or data privacy cleanup process. By keeping a structured log of requests and verified proofs, you maintain a clean, ready-to-use audit trail for compliance requirements.

## Tools

### record_closure_evidence
This tool updates a pending request with the formal proof of closure. Use it once you have received confirmation that an account is officially closed.

### get_register_summary
This tool provides a high-level overview of all current account closure request statuses. It's the quickest way to see how many requests are pending or verified.

### register_closure_request
This tool adds a new account closure attempt to your register. It ensures your follow-up date is set correctly after the initial request date.

### get_followup_list
This tool identifies all accounts requiring immediate attention. It pulls a list of requests where the follow-up date has already arrived.

## Prompt Examples

**Prompt:** 
```
Give me a summary of all pending account closure requests.
```

**Response:** 
```
There are currently 5 pending account closure requests in the register.
```

**Prompt:** 
```
Which account closures need my attention today?
```

**Response:** 
```
The following requests are overdue: AWS (Full Deletion) and Slack (Subscription Stop).
```

**Prompt:** 
```
I have received confirmation for the AWS closure. The reference is REF-12345.
```

**Response:** 
```
The request for AWS has been successfully updated to VERIFIED with confirmation reference REF-12345.
```

## Capabilities

### Request Registration
Your agent adds new closure attempts to the log with specific follow-up dates.

### Evidence Logging
Your agent attaches formal verification to pending requests to close the loop.

### Status Monitoring
Your agent pulls high-level counts to show how many closures are in progress.

### Overdue Detection
Your agent identifies accounts that missed their scheduled follow-up date.

## Use Cases

### Cloud Service Offboarding
Track the deletion of AWS or Azure accounts to ensure no lingering costs or security risks remain.

### SaaS License Cleanup
Manage the removal of user access across various subscription services.

### Compliance Auditing
Generate a list of verified closures to present during a data privacy audit.

### Employee Offboarding
Ensure every tool an employee used is properly decommissioned and documented.

## Benefits

- Centralizes all closure-related data in one place.
- Eliminates manual tracking of overdue follow-ups.
- Creates a verifiable record of closure evidence.
- Reduces the risk of forgotten account terminations.

## How It Works

Connecting this MCP to your AI client gives your agent direct access to the closure register.

1. Connect the MCP to your client via Vinkius.
2. Register a new closure request through your agent.
3. Monitor the status or check for overdue items using the summary and follow-up tools.
4. Record the formal evidence once the closure is confirmed.

## Frequently Asked Questions

**How do I add a new account closure to the list?**
You can use the register_closure_request tool through your AI client to add a new entry.

**Can I prove that an account was actually closed?**
Yes, you use the record_closure_evidence tool to attach formal proof to a pending request.

**How do I find accounts that I forgot to follow up on?**
Use the get_followup_list tool to see all accounts where the follow-up date has arrived.

**What kind of clients can I use this with?**
This MCP works with any compatible client like Claude, Cursor, Windsurf, or VS Code.

**Does this MCP host my data?**
Vinkius hosts and manages the MCP, making it ready to use immediately after you connect.

**How do I see how many requests are still pending?**
You can use the `get_register_summary` tool and filter by the PENDING status to see the current count of requests awaiting verification.

**What should I do if a follow-up date has passed?**
Use the `get_followup_list` tool to identify all requests that are overdue and require immediate verification or action.

**How do I mark a closure as successful?**
Once you receive a confirmation reference from the service, use `record_closure_evidence` to update the request status to VERIFIED.