Book Fence
v1.0.1Book fence services through Lokuli MCP. Use when user needs to find and book fence. Triggers on requests like "book a fence", "find fence near me", or any fence service request.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name and description match the included JSON-RPC examples (search, check_availability, create_booking) against an MCP endpoint, so the capability is coherent in concept. However the SKILL.md provides no explanation of how the agent authenticates or which credentials (if any) are required to call the Lokuli MCP API — a booking API would normally require authentication.
Instruction Scope
Instructions show example JSON-RPC payloads and an MCP endpoint but are underspecified: they do not explain auth headers/tokens, do not instruct the agent to prompt for and confirm customer details before creating a booking, and include hard-coded example data (zipCode, customer info, dates). The transport description mixes SSE and POST/JSON-RPC in a way that is technically inconsistent (SSE is usually a GET event stream). This vagueness could lead the agent to make incorrect or unintended requests.
Install Mechanism
Instruction-only skill with no install spec and no code files — lowest risk from install mechanism perspective. Nothing will be written to disk by an installer.
Credentials
The skill declares no required environment variables or credentials, yet it targets a remote booking API where authentication would typically be required. Absence of any declared primary credential is suspicious (either the API is publicly open — unusual for bookings — or the SKILL.md omitted necessary auth requirements).
Persistence & Privilege
always is false and the skill is user-invocable; it does not request persistent presence or elevated platform privileges.
What to consider before installing
Before installing or enabling this skill, ask the publisher how authentication to https://lokuli.com/mcp/sse is performed (API key, OAuth, platform-managed token). Confirm whether the skill will prompt you for and require explicit user confirmation before creating bookings and before sending personal customer info. Ask the author to fix or clarify the transport details (SSE vs POST/JSON-RPC) and remove hard-coded example data so the agent uses the user's location and contact info. If bookings may incur charges or expose personal data, test in a sandbox account or staging endpoint first and avoid providing real payment/PII until the integration and auth are validated.Like a lobster shell, security has layers — review code before you run it.
latest
uook fence
Book fence services through Lokuli's MCP server.
MCP Endpoint
https://lokuli.com/mcp/sse
Transport: SSE | JSON-RPC 2.0 | POST requests
Tools
search
{
"method": "tools/call",
"params": {
"name": "search",
"arguments": {
"query": "fence",
"zipCode": "90640",
"maxResults": 20
}
}
}
check_availability
{
"method": "tools/call",
"params": {
"name": "check_availability",
"arguments": {
"providerId": "xxx",
"serviceId": "yyy",
"date": "2025-02-10"
}
}
}
create_booking
{
"method": "tools/call",
"params": {
"name": "create_booking",
"arguments": {
"providerId": "xxx",
"serviceId": "yyy",
"timeSlot": "2025-02-10T14:00:00-08:00",
"customerName": "John Doe",
"customerEmail": "john@example.com",
"customerPhone": "+13105551234"
}
}
}
Comments
Loading comments...
