SavvyCal MCP by usefulapi
io.usefulapi/savvycalusefulapi.iostreamable-httpv1.40.4Scanned
Read and create SavvyCal scheduling links and booked events.
8 tools: 3 can delete or cancel things and 5 only read.
- Reads private data · 2
- Reads text others write · 0
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
3 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the SavvyCal MCP by usefulapi can do
The SavvyCal MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 8 tools. It can delete or cancel things (3 tools: savvycal_toggle_link, savvycal_duplicate_link and savvycal_cancel_event). 5 tools only read.
2 tools read private data (savvycal_list_events and savvycal_get_event).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.40.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Deletes or cancels 3Claude Code: deny
savvycal_cancel_eventCancel a booked event/meeting.No findings
Why it is in this group
- The name "savvycal_cancel_event" says "cancel": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Cancel a booked event/meeting. This notifies attendees and frees the slot. SavvyCal REST: DELETE /events/{id}.
Annotations the server declares
- title: Cancel event
- destructiveHint: true
savvycal_duplicate_linkCreate a copy of an existing scheduling link.No findings
Why it is in this group
- The name "savvycal_duplicate_link" says "link": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Create a copy of an existing scheduling link. SavvyCal REST: POST /links/{id}/duplicate.
Annotations the server declares
- title: Duplicate link
- destructiveHint: true
savvycal_toggle_linkToggle a scheduling link between active and disabled (changes whether the public booking page accepts bookings).No findings
Why it is in this group
- The name "savvycal_toggle_link" says "toggle": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Toggle a scheduling link between active and disabled (changes whether the public booking page accepts bookings). SavvyCal REST: POST /links/{id}/toggle.
Annotations the server declares
- title: Toggle link
- destructiveHint: true
Only reads 5Show 5 read-only tools
savvycal_get_eventGet a single booked event/meeting by id.Reads private dataNo findings
Why it is in this group
- The name "savvycal_get_event" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "meeting": it reads calendars.
Description, as the server wrote it Get a single booked event/meeting by id. SavvyCal REST: GET /events/{id}.
Annotations the server declares
- title: Get event
- readOnlyHint: true
savvycal_get_linkGet a single scheduling link by id.No findings
Why it is in this group
- The name "savvycal_get_link" says "get": a word for reading.
Description, as the server wrote it Get a single scheduling link by id. SavvyCal REST: GET /links/{id}.
Annotations the server declares
- title: Get link
- readOnlyHint: true
savvycal_get_link_slotsGet available booking time slots for a scheduling link.No findings
Why it is in this group
- The name "savvycal_get_link_slots" says "get": a word for reading.
Description, as the server wrote it Get available booking time slots for a scheduling link. Returns slots with start_at/end_at/duration/rank. SavvyCal REST: GET /links/{id}/slots.
Annotations the server declares
- title: Get link slots
- readOnlyHint: true
savvycal_list_eventsList booked events/meetings (paginated).Reads private dataNo findings
Why it is in this group
- The name "savvycal_list_events" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "meeting": it reads calendars.
Description, as the server wrote it List booked events/meetings (paginated). SavvyCal REST: GET /events.
Annotations the server declares
- title: List events
- readOnlyHint: true
savvycal_list_linksList the authenticated user's scheduling links (paginated).No findings
Why it is in this group
- The name "savvycal_list_links" says "list": a word for reading.
Description, as the server wrote it List the authenticated user's scheduling links (paginated). SavvyCal REST: GET /links.
Annotations the server declares
- title: List links
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://savvycal.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://savvycal.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://savvycal.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://savvycal.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http savvycal https://savvycal.usefulapi.io/mcpclaude mcp add --transport http savvycal https://savvycal.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__savvycal__savvycal_list_links",
"mcp__savvycal__savvycal_get_link",
"mcp__savvycal__savvycal_get_link_slots",
"mcp__savvycal__savvycal_list_events",
"mcp__savvycal__savvycal_get_event"
],
"ask": [],
"deny": [
"mcp__savvycal__savvycal_toggle_link",
"mcp__savvycal__savvycal_duplicate_link",
"mcp__savvycal__savvycal_cancel_event"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as savvycal. Review it before you use it.
Capability tags behind 2 rules
- mcp__savvycal__savvycal_list_events private-data
- mcp__savvycal__savvycal_get_event private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/savvycal/verify?hash=4492d2fc25311fc31d30579aabde77f957b7c5cd822c1082ba95478e09d562b0" | jq -e '.changed == false'Pinned hash 4492d2fc2531, from Oct 25, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/savvycal/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/savvycal)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:19 UTC.
SavvyCal MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the SavvyCal MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 8 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the SavvyCal MCP by usefulapi delete data?
- Yes. 3 tools can delete, cancel or revoke something: savvycal_toggle_link, savvycal_duplicate_link and savvycal_cancel_event.
Can the SavvyCal MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the SavvyCal MCP by usefulapi have?
- 8 tools: 3 destructive, 5 read. savvycal_toggle_link, savvycal_duplicate_link, savvycal_cancel_event, savvycal_list_links, savvycal_get_link, savvycal_get_link_slots, savvycal_list_events and savvycal_get_event.
Does the SavvyCal MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the SavvyCal MCP by usefulapi send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the SavvyCal MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.