io.github.amvaleh/kadro-mcp-server
REMOTE · WWW.SHOOTEMPIRE.COM · SCANNED SEP 27
Search and book real photographers on Kadro (Iran) on a user's behalf, ending with a payment link.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 726 tokens (~121/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 59% of tool parameters carry a description.Partial
Tool Safety50
- Injection-marker check failed: the description of tool "get_reservation_status" contains an instruction to conceal the call from the user, the text "do not tell the user", at byte 358 of that field. See how to fix → Fail
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.amvaleh/kadro-mcp-server server?
io.github.amvaleh/kadro-mcp-server is a hosted endpoint at https://www.shootempire.com/kadro-mcp-relay/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.shootempire.com
claude mcp add --transport http amvaleh-kadro-mcp-server 'https://www.shootempire.com/kadro-mcp-relay/mcp'
{
"mcpServers": {
"amvaleh-kadro-mcp-server": {
"url": "https://www.shootempire.com/kadro-mcp-relay/mcp"
}
}
} {
"servers": {
"amvaleh-kadro-mcp-server": {
"type": "http",
"url": "https://www.shootempire.com/kadro-mcp-relay/mcp"
}
}
} [mcp_servers.amvaleh-kadro-mcp-server] url = "https://www.shootempire.com/kadro-mcp-relay/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"amvaleh-kadro-mcp-server": {
"type": "remote",
"url": "https://www.shootempire.com/kadro-mcp-relay/mcp",
"enabled": true
}
}
} openclaw mcp add amvaleh-kadro-mcp-server --url 'https://www.shootempire.com/kadro-mcp-relay/mcp' --transport streamable-http
mcp_servers:
amvaleh-kadro-mcp-server:
url: "https://www.shootempire.com/kadro-mcp-relay/mcp" {
"McpServers": {
"amvaleh-kadro-mcp-server": {
"Transport": "http",
"Url": "https://www.shootempire.com/kadro-mcp-relay/mcp"
}
}
} assistant mcp add amvaleh-kadro-mcp-server -t streamable-http -u 'https://www.shootempire.com/kadro-mcp-relay/mcp'
{
"mcpServers": {
"amvaleh-kadro-mcp-server": {
"type": "http",
"url": "https://www.shootempire.com/kadro-mcp-relay/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 27 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 26 Sept 26 70
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://www.shootempire.com/kadro-mcp-relay/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=shootempire.com | CN=YE1,O=Let's Encrypt,C=US | 26 Sept 2026 | 25 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 69f87b3d529d629c2b60668ebd71c1a388e |
| SANs: shootempire.com, www.shootempire.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.shootempire.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| shootempire.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.shootempire.com/kadro-mcp-relay/mcp | Verified | 200 | |
| http (plaintext) | http://www.shootempire.com/kadro-mcp-relay/mcp | HTTPS enforced | 301 | https://www.shootempire.com/kadro-mcp-relay/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_reservation Create a guest photographer reservation ~276
Book a specific photographer for a specific package, date/time, and address on the user's behalf — no login required. This only places a 15-minute hold; it does NOT charge any money and does NOT require or accept any payment information. Immediately follow this with get_payment_link and give that URL to the human — they open it themselves to verify their phone number and pay. start_time must be an ISO 8601 timestamp at least 6 hours in the future. Pass a stable idempotency_key if you might retry this call, so a retry can't create a second reservation.
| Name | Type | Req | Description |
|---|---|---|---|
| address_detail | string | yes | Human-readable address text for the shoot location. |
| address_latitude | number | yes | – |
| address_longitude | number | yes | – |
| city_id | integer | yes | – |
| guest_display_name | string | – | The customer's name, if known. |
| idempotency_key | string | – | A key you generate to make retries safe. Reuse it only when retrying the exact same request. |
| package_id | integer | yes | – |
| photographer_uid | string | yes | – |
| shoot_detail | string | – | Free-text notes about the shoot for the photographer. |
| shoot_type_id | integer | yes | – |
| start_time | string | yes | ISO 8601 timestamp, at least 6 hours from now. |
No output schema declared.
No examples provided.
get_payment_link Get the payment link for a reservation ~97
Get a URL for the human to open in their own browser to finish this reservation: verify their phone number by SMS code and pay. This is the last step this server ever takes — never ask the user for a card number, OTP code, or password, and never try to open, submit, or complete this URL yourself. Just hand the URL to the user.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The slug returned by create_reservation. |
No output schema declared.
No examples provided.
get_photographer_packages Get a photographer's packages and prices ~87
List the real, currently bookable packages (with prices, in Toman) a specific photographer offers for a given shoot_type_id. Rejects the shoot_type_id if that photographer doesn't actually offer it. Use the returned package id with create_reservation.
| Name | Type | Req | Description |
|---|---|---|---|
| photographer_uid | string | yes | A photographer uid from search_photographers. |
| shoot_type_id | integer | yes | – |
No output schema declared.
No examples provided.
get_reservation_status Check a reservation's status ~114
Check whether a reservation has been paid and confirmed. IMPORTANT: status values are 'awaiting_payment', 'expired', 'paid_awaiting_photographer_confirmation', 'confirmed', and 'rejected'. 'paid_awaiting_photographer_confirmation' means the customer paid but the photographer has not yet accepted the booking and could still decline or ask to reschedule — do not tell the user their booking is final until status is exactly 'confirmed'.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The slug returned by create_reservation. |
No output schema declared.
No examples provided.
search_photographers Search Kadro photographers ~94
Find real, bookable photographers for a given shoot_type_id (from search_shoot_types), optionally narrowed to a city_id. Returns each photographer's uid (needed for every later call), display name, rating, review count, and city.
| Name | Type | Req | Description |
|---|---|---|---|
| city_id | integer | – | Optional Kadro city id to narrow the search. |
| shoot_type_id | integer | yes | A shoot_type_id from search_shoot_types. |
No output schema declared.
No examples provided.
search_shoot_types Search Kadro shoot types ~58
List the photography/videography service types Kadro offers (e.g. wedding, industrial, portrait), each with a numeric shoot_type_id. Call this first if you don't already know the id for the kind of shoot the user wants.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.amvaleh/kadro-mcp-server server?
io.github.amvaleh/kadro-mcp-server is listed in the public MCP registry as io.github.amvaleh/kadro-mcp-server. Search and book real photographers on Kadro (Iran) on a user's behalf, ending with a payment link. This page covers its hosted endpoint (https://www.shootempire.com/kadro-mcp-relay/mcp).
Is the io.github.amvaleh/kadro-mcp-server server safe to use?
io.github.amvaleh/kadro-mcp-server scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.amvaleh/kadro-mcp-server server expose?
io.github.amvaleh/kadro-mcp-server exposes 6 tools: search_shoot_types, search_photographers, get_photographer_packages, create_reservation, get_payment_link, get_reservation_status. Their descriptions and schemas cost roughly 726 tokens of context every time the server is loaded.
Does the io.github.amvaleh/kadro-mcp-server server require authentication?
No. We connected to io.github.amvaleh/kadro-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.amvaleh/kadro-mcp-server server still maintained?
io.github.amvaleh/kadro-mcp-server is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.