Summary
There is currently no way to verify that authentication is working without calling a data-returning tool (e.g. list_collections). A get_user tool gives a lightweight, unambiguous auth check and returns useful account metadata.
Raindrop.io API
GET /user — returns the authenticated user's profile: name, email, pro status, registered date, etc.
API reference: https://developer.raindrop.io/v1/user
Proposed tool
@mcp.tool()
async def get_user() -> dict:
"""Get the authenticated Raindrop.io user's profile. Use this to verify the token is working."""
return await _client.get_user()
Use cases
- First thing to call after setup to confirm the token works
- Checking whether the account is free or Pro (useful context for feature availability)
- Claude can proactively call this when an auth error occurs to provide a clearer diagnosis
Implementation
One new client method, one new tool — simplest possible addition. Can go in a tools/user.py file or be added to an existing module.
Summary
There is currently no way to verify that authentication is working without calling a data-returning tool (e.g.
list_collections). Aget_usertool gives a lightweight, unambiguous auth check and returns useful account metadata.Raindrop.io API
GET /user— returns the authenticated user's profile: name, email, pro status, registered date, etc.API reference: https://developer.raindrop.io/v1/user
Proposed tool
Use cases
Implementation
One new client method, one new tool — simplest possible addition. Can go in a
tools/user.pyfile or be added to an existing module.