StoreRocket MCP by usefulapi
io.usefulapi/storerocketusefulapi.iostreamable-httpv1.19.4Scanned
Read StoreRocket projects and store-locator locations; create and update locations.
6 tools: 1 can delete or cancel things, 2 change things and 3 only read.
- Reads private data · 1
- Reads text others write · 6
- Can send data out · 1
- 1 finding
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 StoreRocket MCP by usefulapi can do
The StoreRocket MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 6 tools. It can delete or cancel things (1 tool: storerocket_update_location) and create or change data (2 tools: storerocket_get_user and storerocket_create_location). 3 tools only read.
1 tool reads private data (storerocket_get_user); 6 tools bring in text other people can write (storerocket_get_user, storerocket_list_projects, storerocket_list_locations and 3 more); 1 tool can send data out of your system (storerocket_create_location). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Last scanned Oct 25, 2026, version 1.19.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.
6 tools
Deletes or cancels 1Claude Code: deny
storerocket_update_locationWRITE: change selected fields of one location with a partial update (PATCH): only the fields you send change, everything else is kept.Reads text others writeNo findings
Why it is in this group
- The name "storerocket_update_location" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it WRITE: change selected fields of one location with a partial update (PATCH): only the fields you send change, everything else is kept. The change shows on the live locator at once. Use null to clear phone, email, url, socials or cover; hours accepts single days (hours:{mon:'09:00-17:00'}), null for a day clears it, hours:null removes the whole schedule; fields and calls_to_action merge by name (a null value removes that entry); filters REPLACES the list ([] clears it). To take a location off the locator without deleting it, set visible=false. An invalid value saves nothing. Needs the location:update permission. PATCH /projects/{project_id}/locations/{location_id}.
Annotations the server declares
- title: Update location
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
Changes things 2Claude Code: ask
storerocket_create_locationWRITE: add a location to a project's store locator.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "storerocket_create_location" says "create": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.phone): what the tool writes goes there.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it WRITE: add a location to a project's store locator. name and city are required; supply lat and lng for a precise pin (otherwise StoreRocket geocodes the address, which can be off). It appears on the live locator immediately unless visible is false, so set visible=false for a coming-soon or draft location. Opening hours: omit, or give all seven days. Creating twice makes two locations, so check storerocket_list_locations before retrying after an error. Needs the location:create permission. POST /projects/{project_id}/locations.
Annotations the server declares
- title: Create location
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
storerocket_get_userThe StoreRocket user the API token belongs to: id, name, email and company.Reads private dataReads text others write1 finding
Why it is in this group
- The name "storerocket_get_user" says "get": a word for reading.
- The description's first verb is "store": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- private-dataThe description's first sentence says "email": it reads mail.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "store" and "email": it reads inbound email, which other people can write.
Findings
- Warn
The server marks "storerocket_get_user" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The name "storerocket_get_user" says "get": a word for reading.
Description, as the server wrote it The StoreRocket user the API token belongs to: id, name, email and company. GET /user.
Annotations the server declares
- title: Get user
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
Only reads 3Show 3 read-only tools
storerocket_get_locationOne location by id, optionally with its opening hours, search filters, custom fields and calls to action.Reads text others writeNo findings
Why it is in this group
- The name "storerocket_get_location" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it One location by id, optionally with its opening hours, search filters, custom fields and calls to action. Needs the location:read permission. GET /projects/{project_id}/locations/{location_id}.
Annotations the server declares
- title: Get location
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
storerocket_list_locationsList the locations of a project (name, address, city, coordinates, phone, visibility, location type, marker, cover image), 25 per page by default, with optional filters on name, ad…Reads text others writeNo findings
Why it is in this group
- The name "storerocket_list_locations" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it List the locations of a project (name, address, city, coordinates, phone, visibility, location type, marker, cover image), 25 per page by default, with optional filters on name, address, city, state, country and postal code and optional hours/filters/custom fields/calls to action. Needs the location:read permission. GET /projects/{project_id}/locations.
Annotations the server declares
- title: List locations
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
storerocket_list_projectsList the StoreRocket projects (store locators) the token's user belongs to: public id, name, number of locations, status and plan.Reads text others writeNo findings
Why it is in this group
- The name "storerocket_list_projects" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it List the StoreRocket projects (store locators) the token's user belongs to: public id, name, number of locations, status and plan. Use the id as project_id in every location tool. Location tools need a project on the Business plan (API access). GET /projects.
Annotations the server declares
- title: List projects
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: 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.
6 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write6
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__storerocket__storerocket_create_location"
]
}
}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 16, 2026, 14:33 UTC, unchanged since Nov 2, 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
- Nov 2, 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://storerocket.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://storerocket.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.
The server marks "storerocket_get_user" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The name "storerocket_get_user" says "get": a word for reading.
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://storerocket.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://storerocket.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.19.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http storerocket https://storerocket.usefulapi.io/mcpclaude mcp add --transport http storerocket https://storerocket.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__storerocket__storerocket_list_projects",
"mcp__storerocket__storerocket_list_locations",
"mcp__storerocket__storerocket_get_location"
],
"ask": [
"mcp__storerocket__storerocket_get_user",
"mcp__storerocket__storerocket_create_location"
],
"deny": [
"mcp__storerocket__storerocket_update_location"
]
}
}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 storerocket. Review it before you use it.
Capability tags behind 6 rules
- mcp__storerocket__storerocket_get_user private-data, untrusted-input
- mcp__storerocket__storerocket_list_projects untrusted-input
- mcp__storerocket__storerocket_list_locations untrusted-input
- mcp__storerocket__storerocket_get_location untrusted-input
- mcp__storerocket__storerocket_create_location untrusted-input, outbound
- mcp__storerocket__storerocket_update_location untrusted-input
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/storerocket/verify?hash=dc640df2a78cf439a46ec705599f958c536114cf84e6e0786e9949efbff852a4" | jq -e '.changed == false'Pinned hash dc640df2a78c, from Oct 25, 2026, 23:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/storerocket/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/storerocket)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:19 UTC.
StoreRocket MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the StoreRocket MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the StoreRocket MCP by usefulapi delete data?
- Yes. 1 tool can delete, cancel or revoke something: storerocket_update_location.
Can the StoreRocket 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 StoreRocket MCP by usefulapi have?
- 6 tools: 1 destructive, 2 write, 3 read. storerocket_update_location, storerocket_get_user, storerocket_create_location, storerocket_list_projects, storerocket_list_locations and storerocket_get_location.
Does the StoreRocket MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the StoreRocket MCP by usefulapi send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): storerocket_create_location.
Has the StoreRocket MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.