RemoteLock MCP by usefulapi

MCP server · hosted · v1.0.1 · io.usefulapi/remotelock

Online · tested 2h agoNEW · 3h agoSeen in the registry 2h ago

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

What it does

RemoteLock MCP by usefulapi is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES

Local installNO

Live checkOnline · 20 tools

Version1.0.1

PriceNot in the registry

First seen30 Oct 2026

Last checked2h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2h ago (live check)

Hosted endpoint

https://remotelock.usefulapi.io/mcp streamable-http

In Claude Code: claude mcp add --transport http remotelock-mcp-by-usefulapi https://remotelock.usefulapi.io/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

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

Live check

Electra Index connected to the hosted endpoint 2h ago

ONLINE RemoteLock MCP by usefulapi answered an MCP connection on 30 Oct 2026 and introduced itself as remotelock-mcp 1.0.1 (MCP protocol 2025-06-18).

20 tools offered to AI assistants

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_list_locations · List the account's locations (properties/sites) with address and time zone. Use the ids to filter devices. GET /locations.
remotelock_get_location · One location by id. GET /locations/{id}.
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_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_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_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.
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 expire
remotelock_get_access_person · One access user or guest by id, with status, validity window and PIN / card number. GET /access_persons/{id}.
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 fir
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_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.

Show 8 more

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_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_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 recurr
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}/a
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_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 r
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}.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.

Fact	Value	Evidence	Source	Last confirmed
Hosted endpoint	https://remotelock.usefulapi.io/mcp	DECLARED	SRC-001 Official MCP Registry	2h ago
Local install (package)	no	DECLARED	SRC-001 Official MCP Registry	2h ago
Remote access (hosted)	yes	DECLARED	SRC-001 Official MCP Registry	2h ago
Website	https://usefulapi.io/remotelock/	DECLARED	SRC-001 Official MCP Registry	2h ago
Repository	https://github.com/m190/usefulapi-mcp	DECLARED	SRC-001 Official MCP Registry	2h ago
Registry status	active	DECLARED	SRC-001 Official MCP Registry	2h ago
Version	1.0.1	DECLARED	SRC-001 Official MCP Registry	2h ago
MCP server	yes	DECLARED	SRC-001 Official MCP Registry	2h ago

Change history

NEW30 Oct 2026
first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Is RemoteLock MCP by usefulapi still online?

Free alerts · no account

Do you run RemoteLock MCP by usefulapi? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor RemoteLock MCP by usefulapiLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Questions about RemoteLock MCP by usefulapi

How do I connect RemoteLock MCP by usefulapi?

Use the hosted endpoint https://remotelock.usefulapi.io/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does RemoteLock MCP by usefulapi offer?

When Electra Index connected on 30 Oct 2026, it listed 20 tools: remotelock_get_account, remotelock_list_locations, remotelock_get_location, remotelock_list_devices, remotelock_get_device, remotelock_lock_device, remotelock_unlock_device, remotelock_list_access_persons and more. The full list is in "Live check" above.

Is RemoteLock MCP by usefulapi online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 2h ago.