RemoteLock MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

RemoteLock MCP by usefulapi is answering right now. Last checked 11 min ago. It exposes 20 tools. Last commit 2 Nov 2026.

Read RemoteLock devices and guests; manage door access and physically lock or unlock doors.

Uptime history 69 hours of history

69 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

165 ms

Response time

average over 24h

Stars

last commit 2 Nov 2026

What changed 5

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 31 October 2026. No other catalogue keeps this.

2 Nov a tool changed version

31 Oct a tool changed version4 times that day

and 3 more, back to 31 October 2026

Nothing serious here today

Today is the operative word: we check RemoteLock MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add remotelock --transport http https://remotelock.usefulapi.io/mcp

Settings → Connectors → Add custom connector, then paste this address

https://remotelock.usefulapi.io/mcp

~/.codex/config.toml

[mcp_servers.remotelock]
url = "https://remotelock.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "remotelock": {
      "url": "https://remotelock.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "remotelock": {
      "type": "http",
      "url": "https://remotelock.usefulapi.io/mcp"
    }
  }
}

Available tools 20

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

remotelock

remotelock_create_access_guest

WRITE: creates an access guest whose PIN/card only works between starts_at and ends_at (local time of the lock). It creates the person only; use remotelock_grant_access to give them doors. The reply includes the PIN. POST /access_persons.

remotelock_create_access_user

WRITE: creates a permanent access user (an employee, resident or owner) with a PIN and/or card. It creates the person only; use remotelock_grant_access to give them doors. The reply includes the PIN. Check remotelock_list_access_persons first to avoid duplicates. POST /access_persons.

remotelock_deactivate_access_person

WRITE: deactivates an access user or guest, so their PIN/card stops working on every door. The person stays in the account (status deactivated) and is not deleted. Only do it when the user asked. PUT /access_persons/{id}/deactivate.

remotelock_get_access_person

One access user or guest by id, with status, validity window and PIN / card number. GET /access_persons/{id}.

remotelock_get_account

The RemoteLock account these credentials belong to: name, plan limits and settings. Use it to confirm which account is connected. GET /account.

remotelock_get_device

One device (lock) by id with its full state: connectivity, battery/power, lock state, auto-lock settings, model and location. GET /devices/{id}.

remotelock_get_event

One event by id (for example from a notification): type, time, source, status, the lock and the person involved, and the method used. The PIN or card used is not returned. GET /events/{id}.

remotelock_get_location

One location by id. GET /locations/{id}.

remotelock_grant_access

WRITE: gives an access user or guest access to a lock, a door group or a location, so their PIN/card opens it. RemoteLock then syncs the code to the lock(s). Optionally limit the hours with an access schedule (access_schedule_id, for recurring daily hours) or override a guest's start/end time of day on this door. POST /access_persons/{id}/accesses.

remotelock_list_access_persons

List the people who can open doors: access users (permanent) and access guests (time-limited), with name, email, status, validity window and their PIN / card number. By default only current and upcoming people; pass status to include expired or deactivated. GET /access_persons.

remotelock_list_device_accesses

List the access users and guests who have access to one lock (and whether the PIN is synced to it). GET /devices/{id}/access_person_accesses.

remotelock_list_devices

List devices: locks, access-control doors, thermostats, etc., with name, model, battery/connectivity state, lock state and location. Filter by type (e.g. lock) or location. GET /devices.

remotelock_list_door_groups

List door groups (named sets of locks you can grant access to in one step). GET /groups.

remotelock_list_group_items

List the items (locks) that belong to one door group. GET /groups/{id}/items.

remotelock_list_locations

List the account's locations (properties/sites) with address and time zone. Use the ids to filter devices. GET /locations.

remotelock_list_notifications

List notifications sent by notification subscriptions: each names the lock (publisher), the event type (unlocked, access_denied, jammed, power_level_low, ...) and an event_id. Only events that match a subscription appear. Get details with remotelock_get_event. GET /notifications.

remotelock_list_person_accesses

List the doors, door groups and locations one access user or guest can open, with sync state per device. GET /access_persons/{id}/accesses.

remotelock_lock_device

WRITE: sends the lock command to a lock (it locks the door). Locking an already locked door changes nothing. PUT /devices/{id}/lock.

remotelock_revoke_access

WRITE: removes one access grant (an id from remotelock_list_person_accesses), so the person's PIN/card no longer opens that door, door group or location. The person itself stays. Only do it when the user asked. DELETE /access_persons/{id}/accesses/{access_id}.

remotelock_unlock_device

WRITE, SECURITY-SENSITIVE: sends the unlock command to a lock, which physically unlocks the door. Only call it when the user explicitly asked to unlock this specific door, and set confirm to true. PUT /devices/{id}/unlock.

Endpoints

URL	Transport	State	Latency	Checked
https://remotelock.usefulapi.io/mcp	streamable-http	answering	96 ms	11 min ago

Alternatives to RemoteLock MCP by usefulapi

same job, measured the same way

Kisi MCP by usefulapi

by usefulapi

Read Kisi places, doors, users, groups, access rights and access logs (no unlocking).

20 tools answering

Tailscale MCP by usefulapi

by usefulapi

Read devices, users, keys, ACLs and DNS for a tailnet; manage devices, routes and auth keys.

22 tools answering

Operto MCP by usefulapi

by usefulapi

Read properties, reservations, guest access codes, smart locks and thermostats in Operto.

8 tools answering

Bsale MCP by usefulapi

by usefulapi

Read Bsale products, documents and stock; manage customers, prices, receipts and payments.

25 tools answering

OKSign MCP by usefulapi

by usefulapi

Read documents, signatures, contacts and credits; manage contacts and remove documents.

14 tools answering

ClassMarker MCP by usefulapi

by usefulapi

Read ClassMarker groups, links, exams and recent results; manage question bank and access codes.

15 tools answering

OwnerRez MCP by usefulapi

by usefulapi

Manage OwnerRez properties, bookings, guests, quotes and inquiries.

25 tools answering

Hostfully MCP by usefulapi

by usefulapi

Check properties, calendars, leads, quotes, guests and messages in Hostfully, and send replies.

20 tools answering

RemoteLock MCP by usefulapi — questions

Answers built from our own checks of this server.

What can RemoteLock MCP by usefulapi do?

It exposes 20 tools, read directly from the server on our last check. Among them: remotelock_create_access_guest, remotelock_create_access_user, remotelock_deactivate_access_person, remotelock_get_access_person, remotelock_get_account, remotelock_get_device and 14 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is RemoteLock MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 165 ms. The bar chart above shows every period we have measured.

How do I connect RemoteLock MCP by usefulapi?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does RemoteLock MCP by usefulapi need an API key?

No. RemoteLock MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 20 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is RemoteLock MCP by usefulapi?

It answers our handshake in 165 ms on average, which is faster than 79% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is RemoteLock MCP by usefulapi open source?

The code is open source: it is published under the MIT licence, written in JavaScript, 1 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at remotelock.usefulapi.io, which runs on its operator's own terms.