Sharpei MCP. Manage identity verification and billing workflows.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Sharpei connects identity verification and recurring payment logic to your backend systems. This MCP Server lets your AI client manage KYC workflows, list applications, view document details, and track subscription status for e-commerce platforms using direct tool calls.
What your AI agents can do
Check sharpei status
Confirms the API connection is active and ready for use.
Create application
Starts a new identity verification application record.
Get application
Retrieves all details for a specific user's verification application ID.
Initiates a new identity verification application for a user, generating an immediate ID that tracks their compliance status.
Lists all documents attached to an application or retrieves the specific details of one document upload for inspection.
Reads the current status of a verification process, noting if it's 'Pending,' 'Under Review,' or 'Approved.'
Retrieves details about specific user subscription plans or lists all available subscription records.
Shows which webhook endpoints are currently configured, allowing your agent to confirm data routing settings.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
Sharpei MCP Server: 10 Tools for Compliance & Billing
Use these tools to programmatically create applications, check document status, and manage user subscriptions within your AI agent's workflow.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Sharpei on Vinkius019dd159check sharpei status
Confirms the API connection is active and ready for use.
019dd159create application
Starts a new identity verification application record.
019dd159get application
Retrieves all details for a specific user's verification application ID.
019dd159get document
Gets the metadata and status of one uploaded document file.
019dd159get documents
Lists all documents submitted under a given application ID.
019dd159get subscription
Retrieves current details for a specific subscription plan or user account.
019dd159get verification status
Checks the live progress and status of a submitted verification application.
019dd159list applications
Fetches a list containing IDs and high-level status summaries for all user applications.
019dd159list subscriptions
Returns a list of available subscription plans and active accounts.
019dd159list webhooks
Lists the endpoints where Sharpei sends automated notifications on status changes or events.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Sharpei, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Sharpei. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Checking compliance and billing used to mean jumping between three different dashboards.
Today, checking a user's status is fragmented. You have to check the Subscription Portal for payment level, then open the KYC dashboard to see document uploads, and finally hit a separate 'Status Check' button just to confirm if it passed or failed. It’s three different systems talking to each other.
With Sharpei, your agent handles this in one sequence. You call `get_subscription` for billing context, then immediately follow up with `get_verification_status(app_id)`. The result is a single data object that tells you if the user can use the premium feature *right now*.
Sharpei MCP Server: Track identity and subscription status.
You no longer need to write complex multi-step API calls across different vendor systems. The agent executes `list_applications` first, giving you a clear list of IDs, then uses `get_application(app_id)` to pull all necessary metadata in one go.
The difference is speed and reliability. You get structured data directly from the tool call, making your entire backend process tighter and removing brittle dependencies.
What you can do with this MCP connector
Sharpei MCP Server: Identity & Subscription Tools
This server lets your AI client manage everything related to user identity compliance and billing cycles without needing a human in the loop. It hooks up directly with Sharpei, letting you run full KYC workflows right from your agent's tool calls.
Identity Verification Workflow
You gotta start by making sure the connection is good. You can run check_sharpei_status to confirm the API link is active before anything else. To kick things off for a new user, your agent uses create_application; this immediately generates an ID that tracks their compliance status.
To see what's going on with all your users, you can pull a quick summary list using list_applications. This function returns IDs and high-level status summaries for every application record. If you need the full scoop on one user's file, call get_application with their specific ID.
The verification process moves through stages, right? You track that progress by hitting up get_verification_status. That tells you if a submission is 'Pending,' 'Under Review,' or finally 'Approved.'
Document Management
When documents are involved, your agent handles the file flow. To see every piece of paper attached to an application, use get_documents and pass in the relevant application ID; that returns a list of all submitted files. If you need to inspect one specific upload—maybe check its metadata or status—you call get_document, which gives you detailed info on a single file.
Subscription and Billing Data
For managing recurring payments, the server provides two key tools. You can get a rundown of all available plans and active accounts by running list_subscriptions. If you need specific details—like checking what plan one user is currently on or viewing account specifics—you use get_subscription.
System Configuration
Finally, your agent needs to know where Sharpei sends automated alerts. You can confirm data routing settings by using list_webhooks, which shows you all the webhook endpoints that are currently configured for status changes or other critical events.
019dd159-404a-73f4-8889-84ff7d473772 
How Sharpei MCP Works
- 1 First, call
check_sharpei_statusto ensure the API is live. This prevents failures later. - 2 Next, if you need a new user checked, use
create_application(user_data)to generate an ID and start the record. - 3 Finally, pass the application ID into
get_verification_status(app_id)to get the current compliance status.
The bottom line is you direct your AI agent to call specific tools (like create_application or list_applications) and receive structured JSON data back, which it then uses to complete a workflow.
Who Is Sharpei MCP For?
Backend engineers building e-commerce platforms. Compliance officers who need programmatic access to KYC status. Product managers whose core feature relies on validating user identity before allowing premium features.
Uses list_applications and get_application to build endpoints that manage the entire lifecycle of a customer's profile, from sign-up to full compliance.
Invokes tools like get_documents and get_verification_status to automate manual review tasks, confirming document integrity before approval.
Uses list_subscriptions and get_subscription to programmatically check a user's current billing status against their feature access rights.
What Changes When You Connect
- Automate user compliance checks. Instead of waiting for manual status updates, your agent can run
get_verification_status(app_id)to get the real-time approval state. - Maintain accurate revenue logic. Use
list_subscriptionsandget_subscriptionto check a customer's billing tier before granting premium feature access. - Streamline onboarding flow. Your agent can use
create_applicationimmediately upon sign-up, kicking off the KYC process without needing manual API calls. - Audit user submissions easily. Use
list_applicationsorget_documentsto pull a full audit trail of every document and application ID for compliance review. - Verify system health before deployment. Run
check_sharpei_statusfirst. This guarantees your agent doesn't fail mid-workflow due to a simple API outage.
Real-World Use Cases
Onboarding new users for paid services
A user signs up, triggering an identity check. Your agent calls create_application first, then waits, calling get_verification_status(app_id) every few minutes. Once approved, it checks the billing status using get_subscription to ensure they have a paid plan before granting access.
Auditing compliance records
A product manager needs to know which users are pending review. The agent runs list_applications, filters by 'Pending,' and then uses get_documents for the top 5 applications to confirm they submitted all required ID types.
Debugging webhook failures
The billing system isn't receiving payment failure alerts. The agent runs list_webhooks to check the configured endpoints and verifies that the correct URL is listed, fixing data flow issues immediately.
Updating expired user access
A subscription lapses. The agent calls get_subscription(user_id) to confirm the expiry date. If it's expired, it flags the account and can use list_applications to see if KYC is needed before renewal.
The Tradeoffs
Assuming a single endpoint handles everything
Calling a general 'get user data' endpoint, hoping it includes both subscription status and document verification results.
→
Don't try to get everything in one go. Use dedicated tools: call get_subscription for billing info, and then use get_verification_status for compliance data.
Relying on outdated status checks
Writing code that only checks the application list once at startup, assuming all users are compliant forever.
→
Always check the live state. Use get_verification_status or list_applications to get the current compliance picture before allowing critical actions.
Ignoring required documents
Creating an application using only minimal data, assuming the user will upload everything later without prompting.
→
After running create_application, always check get_documents to ensure all necessary files (e.g., passport, utility bill) have been uploaded before marking the profile complete.
When It Fits, When It Doesn't
Use this if your workflow requires checking both a user's billing status AND their identity compliance. For instance, you need to know: 'Is the account paid?' (get_subscription) and 'Are they verified?' (get_verification_status). If you only care about one thing—just payment, or just verification—you don't need this whole server. If you only need a list of available plans without checking specific user status, list_subscriptions is enough. But if your feature gate requires both paid access and KYC clearance, use the full suite.
Common Questions About Sharpei MCP
How do I check if my API connection works with `check_sharpei_status`? +
Call check_sharpei_status() first. It returns a simple confirmation object, telling you immediately if the service is operational before your agent tries anything else.
What tools do I use to get all user applications? +
Use list_applications(). This tool gives you an ID and status summary for every application record associated with your platform.
Can I check a user's subscription details without knowing their ID? Using `get_subscription`? +
get_subscription() requires specific identifiers (like a user ID or plan name). You must provide the necessary context parameters when calling it.
What is the difference between `list_applications` and `get_application`? +
list_applications gives you a summary of many apps. get_application(app_id) drills down to get every single detail for one specific app.
Do I need to worry about webhook configuration? How do I check it using `list_webhooks`? +
Yes, running list_webhooks() confirms where Sharpei is sending event notifications. This is crucial for debugging data flow when an event fails.
When I call `get_document` for an application, what specific metadata fields should I expect in the response? +
The tool returns structured data about the document. You'll receive details like file type (e.g., PDF, JPEG), date uploaded, and a unique hash ID for integrity checks.
If a user verification fails, how do I get a specific reason or error code using `get_verification_status`? +
The status response includes an explicit failure reason field. Instead of just 'Failed,' you'll see the underlying cause—like 'Mismatching DOB' or 'Document expired.' This helps pinpoint necessary fixes.
What are the required parameters I need to pass when running `create_application`? +
You must provide at minimum a user identifier and their primary email address. The function requires this initial data to provision the application record before any document uploads happen.
Can my AI create a new verification application? +
Yes. Use create_application with the customer name and email. The agent starts the verification process and returns the application ID.
How do I check document verification results? +
Use get_document with the application and document IDs. The agent returns verification status, document type, and any flags.
Can I track the overall verification status? +
Yes. get_verification_status returns the current status of any application — pending, approved, or rejected.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.