Bookings and appointments
officernd
officernd was answering at the last check. Checked on 2026-10-05 (daily check).
Browse OfficeRnD members, bookings, memberships, invoices and tickets, with optional write access.
Agents use servers like this to check availability and book or move appointments.
15 read-only0 change data5 high risk
https://officernd.usefulapi.io/mcp
Follow (RSS): status changes, tool-list changes, new advisories and owner verification, in any feed reader.
Tools
20 tools: 15 read-only, 0 change data, 5 high risk (delete, pay, send or run code).
No tool name points to sending messages.
- read-only
- Only reads or looks things up. Safe for an agent to call on its own.
- changes data
- Creates, edits or sends something. Worth a person's approval the first time.
- high risk
- Can delete, pay, send on your behalf or run code. Hard or impossible to undo.
Connecting costs an agent about 6,219 tokens of tool definitions and a 543 ms handshake.
- high risk
officernd_create_memberWRITE. Add a new member (person) to a location, optionally attached to a company. Needs scope flex.community.members.create. OfficeRnD: POST /members. - high risk
officernd_update_memberWRITE. Update a member's name, email, phone, start date, billing/contact flags, tags or custom properties. Only the fields you pass are changed; `tags` replaces the whole tag list. Needs scope flex.community.members.update. OfficeRnD: PUT /members/{memberId}. - high risk
officernd_create_bookingWRITE. Book a resource (e.g. a meeting room) for a member and/or company. Unless is_free or is_tentative is set, the booking is charged per the resource's rate, and the member is notified unless is_silent. Needs scope flex.space.bookings.create. OfficeRnD: POST /bookings. - high risk
officernd_create_ticketWRITE. Open a helpdesk ticket on behalf of a member. type, priority and severity are ticket-option _ids from officernd_list_ticket_options. Needs scope flex.collaboration.tickets.create. OfficeRnD: POST /tickets. - high risk
officernd_add_ticket_commentWRITE. Post a comment on a helpdesk ticket. Public comments are visible to the member; comments attributed to members must be public. Needs scope flex.collaboration.ticketComments.create. OfficeRnD: POST /ticket-comments/{ticketId}. - read-only
officernd_get_organizationFetch the OfficeRnD organization these credentials belong to - name, slug and region. A cheap way to confirm the setup works. OfficeRnD: GET /api/v2/organizations/{orgSlug}. - read-only
officernd_list_locationsList the organization's locations (coworking spaces/buildings) with address, timezone and open/public flags. Location _ids are needed by most other filters and by officernd_create_member. OfficeRnD: GET /locations. - read-only
officernd_list_membersList members (people) of the workspace, filterable by exact email or name, location, company, status and creation/modification date. OfficeRnD: GET /members. - read-only
officernd_get_memberFetch one member by _id - contact details, company, location, status, billing details and custom properties. OfficeRnD: GET /members/{memberId}. - read-only
officernd_list_companiesList companies (teams/tenants renting space), filterable by exact name or _id, location and status. OfficeRnD: GET /companies. - read-only
officernd_list_resourcesList bookable/assignable resources - meeting rooms, desks, hot desks, private offices - with capacity, price, rate, floor and amenities. Resource _ids are needed by officernd_create_booking. OfficeRnD: GET /resources. - read-only
officernd_list_bookingsList bookings: one entry per one-off booking and one per recurring series (first instance only). Filter by member, company, location, resource, series start window and status. For every individual occurrence in a date window use officernd_list_booking_occurrences. OfficeRnD: GET /bookings. - read-only
officernd_list_booking_occurrencesList every individual booking occurrence between two times - one-off bookings plus each expanded instance of recurring series. The right tool for calendars, room availability and utilisation. Without pagination the window may be at most 1 year. OfficeRnD: GET /bookings/occurrences. - read-only
officernd_get_bookingFetch one booking by _id - resource, member/company, times, recurrence rule, fees, extras, visitors and status. OfficeRnD: GET /bookings/{bookingId}. - read-only
officernd_list_membershipsList memberships (recurring plans sold to members/companies) with plan, price, discount, start/end dates and calculated status. OfficeRnD: GET /memberships. - read-only
officernd_list_contractsList contracts (agreements for plans and resources) with totals, dates, notice period, status and lifecycle stage - e.g. find contracts up for renewal or serving notice. OfficeRnD: GET /contracts. - read-only
officernd_list_checkinsList member check-ins (who was on site, when, and via which booking or pass) - useful for occupancy and attendance. OfficeRnD: GET /checkins. - read-only
officernd_list_paymentsList billing documents - invoices, credit notes, overpayments - with totals, paid/pending amounts, due dates and status. Filter by member, company, location, document type, status, number and issue/due date (e.g. overdue invoices). OfficeRnD: GET /payments. - read-only
officernd_list_ticketsList helpdesk tickets (member requests/issues) with subject, message, status (open/new/pending/resolved), priority, severity and assignee. OfficeRnD: GET /tickets. - read-only
officernd_list_ticket_optionsList the helpdesk ticket options - the configured types, priorities and severities (each with an _id, category and label). Their _ids are required by officernd_create_ticket. OfficeRnD: GET /ticket-options.
Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.
Status
Newest check: answered with tools, from the daily check, 2026-10-05, 543 ms.
From one check a day over the last 1 day. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.
Last 30 days
2026-09-062026-10-05
answered with toolssign-in or payment askednot answeringnot checked
Compare: the most reliable servers in Bookings and appointments, ranked by days answering.
Trust and supply chain
No owner has verified this server yet.
No tool change since tracking began on 2026-10-05.
Badge
Live: status, days reachable, the tokens its tool list costs an agent. For a README:
[](https://7it.co.il/7maps/s/officernd.usefulapi.io/mcp)
Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).
Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=officernd.usefulapi.io%2Fmcp (add the same &style= for another style).
Own this server? Verify that it is yours.
Status widget
A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.
Script (renders where it is placed, in its own shadow DOM):
<script src="https://7it.co.il/7maps/widget/officernd.usefulapi.io/mcp.js" async></script>
Or an iframe:
<iframe src="https://7it.co.il/7maps/widget/officernd.usefulapi.io/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>
The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=officernd.usefulapi.io%2Fmcp.
Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.
For AI agents
Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.
7Maps by 7IT maps the MCP servers AI agents use, from public listings. Observations with a date, not a judgement. Methodology · How we collect, and opting out.