Gingr MCP by usefulapi
REMOTE · GINGR.USEFULAPI.IO
Read Gingr reservations, owners, pets, check-ins, invoices and timeclock for your pet-care business.
Available components
Last scanned (7 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 22 Oct 2026.
Category CRM and Sales
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3248 tokens (~129/item across 25 items; 25 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 Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 25 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 22 Oct 26 0
- Server version: 1.7.3 → 1.7.4 functional
- 21 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.5.0 → 1.7.3 functional
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “getting_started” functional
- Server version: 1.4.0 → 1.5.0 functional
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
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 22 Oct 2026 · Probed https://gingr.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of gingr.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://gingr.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://gingr.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://gingr.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://gingr.usefulapi.io/mcp |
| Authorisation server | https://gingr.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gingr.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/gingr/ |
| http (plaintext) | http://gingr.usefulapi.io/mcp | Inconclusive | 302 | http://gingr.usefulapi.io/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 →
gingr_get_animal_feeding Get a pet's feeding instructions ~53
Get the feeding information of one animal (food, amounts, schedule). Gingr: GET /api/v1/get_feeding_info.
| Name | Type | Req | Description |
|---|---|---|---|
| animal_id | integer | yes | Animal (pet) id. |
No output schema declared.
No examples provided.
gingr_get_animal_immunizations Get a pet's immunization records ~59
Get the immunization (vaccination) records of one animal, with expiration dates. Gingr: GET /api/v1/get_animal_immunizations.
| Name | Type | Req | Description |
|---|---|---|---|
| animal_id | integer | yes | Animal (pet) id. |
No output schema declared.
No examples provided.
gingr_get_animal_medications Get a pet's medications ~54
Get the medication information of one animal (medications, doses, schedule). Gingr: GET /api/v1/get_medication_info.
| Name | Type | Req | Description |
|---|---|---|---|
| animal_id | integer | yes | Animal (pet) id. |
No output schema declared.
No examples provided.
gingr_get_daily_summary Get the day's check-in / check-out summary ~69
Get the summary of reservations for one date: number of check-ins, check-outs and overnights (the widget at the top of the Gingr dashboard). Gingr: GET /api/v1/reservation_widget_data.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | The date (YYYY-MM-DD). |
No output schema declared.
No examples provided.
gingr_get_owner Get an owner ~123
Get one owner (customer) record by exactly one of: owner id, one of their pets' id, one of their reservations' id, cell phone or email. Gingr: GET /api/v1/owner. Passwords and payment-card references are removed.
| Name | Type | Req | Description |
|---|---|---|---|
| animal_id | integer | – | Find the owner of this animal (pet). |
| string | – | Email address. | |
| owner_id | integer | – | Owner id. |
| phone | string | – | Cell phone number. |
| reservation_id | integer | – | Find the owner of this reservation. |
No output schema declared.
No examples provided.
gingr_get_reservation_estimate Get a reservation's cost estimate ~50
Get the estimated cost of an existing (future) reservation. Gingr: GET /api/v1/existing_reservation_estimate.
| Name | Type | Req | Description |
|---|---|---|---|
| reservation_id | integer | yes | Reservation id. |
No output schema declared.
No examples provided.
gingr_get_subscription Get a subscription ~41
Get one subscription (membership package) by id. Gingr: GET /api/v1/get_subscription.
| Name | Type | Req | Description |
|---|---|---|---|
| subscription_id | integer | yes | Subscription id. |
No output schema declared.
No examples provided.
gingr_get_timeclock_report Get the staff timeclock report ~143
Get staff timeclock records (clock-ins/outs, hours) at a location between two dates (at most 31 days apart). Gingr: GET /api/v1/timeclock_report.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | Last day (YYYY-MM-DD). |
| include_clocked_in | boolean | – | true = include staff still clocked in. |
| include_deleted | boolean | – | true = include deleted records. |
| location_id | integer | yes | Location id (from gingr_list_locations). |
| start_date | string | yes | First day (YYYY-MM-DD). |
| user_ids | array | – | Only these Gingr user (staff) ids. |
No output schema declared.
No examples provided.
gingr_get_transaction Get a POS transaction ~56
Get one point-of-sale transaction with its items and payment details (card numbers, processor references and auth codes are removed). Gingr: POST /api/v1/transaction.
| Name | Type | Req | Description |
|---|---|---|---|
| transaction_id | integer | yes | POS transaction id. |
No output schema declared.
No examples provided.
gingr_get_whiteboard Get today's arrivals and departures (whiteboard) ~143
Get the pets checking in and checking out today at a location, by reservation type, with owner/pet names, times, run and status (Gingr's Digital Whiteboard). Gingr: GET /api/v1/back_of_house.
| Name | Type | Req | Description |
|---|---|---|---|
| full_day | boolean | – | true (default) = every reservation checking in/out today; false = use mins_future. |
| location_id | integer | yes | Location id (from gingr_list_locations). |
| mins_future | integer | – | With full_day=false: only the next/last this many minutes. |
| type_ids | array | yes | Reservation type ids to include (from gingr_list_reservation_types). |
No output schema declared.
No examples provided.
gingr_list_animal_reservations List a pet's reservations ~239
List the reservations of one animal (pet), optionally only pending requests, current, future, past or wait-listed ones, by dates or types. Only the location the API user is logged into is included (Gingr). Gingr: POST /api/v1/reservations_by_animal.
| Name | Type | Req | Description |
|---|---|---|---|
| animal_id | integer | yes | Animal (pet) id (from gingr_list_animals). |
| animal_ids | array | – | Only these animal (pet) ids. |
| cancelled_only | boolean | – | true = only cancelled reservations. |
| completed_only | boolean | – | true = only completed reservations. |
| confirmed_only | boolean | – | true = only confirmed reservations. |
| from_date | string | – | Only reservations from this date (YYYY-MM-DD). |
| limit | integer | – | Return at most this many reservations (1-200, default 50). |
| reservation_type_ids | array | – | Only these reservation type ids (from gingr_list_reservation_types). |
| restrict_to | string | – | Only reservations in this state. |
| to_date | string | – | Only reservations up to this date (YYYY-MM-DD). |
No output schema declared.
No examples provided.
gingr_list_animals List animals (pets) ~166
List animals (pets) with species, breed, birthday, weight, owner and notes, optionally filtered by owner, exact name, species or breed. Paged. Gingr: GET /api/v1/animals (filters as params[<field>]).
| Name | Type | Req | Description |
|---|---|---|---|
| breed_id | integer | – | Breed id (gingr_list_reference kind=breeds). |
| first_name | string | – | Exact pet name. |
| limit | integer | – | Records per page (1-200, default 50). |
| offset | integer | – | Skip this many records (paging; default 0). Use next_offset from the previous page. |
| owner_id | integer | – | Only this owner's animals. |
| species_id | integer | – | Species id (gingr_list_reference kind=species). |
No output schema declared.
No examples provided.
gingr_list_cancelled_reservations List recently cancelled reservations ~142
List the reservations that were cancelled between two dates (at most 31 days apart). Paged. Gingr: POST /api/v1/recently_cancelled_reservations.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | Last day of cancellation (YYYY-MM-DD). |
| limit | integer | – | Records per page (1-200, default 50). |
| location_id | integer | – | Location id (from gingr_list_locations). |
| offset | integer | – | Skip this many records (paging; default 0). Use next_offset from the previous page. |
| start_date | string | yes | First day of cancellation (YYYY-MM-DD). |
No output schema declared.
No examples provided.
gingr_list_checked_in List pets checked in now ~105
List the reservations that are checked in right now (the pets currently on site). Paged. Gingr: POST /api/v1/reservations (checked_in=true).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records per page (1-200, default 50). |
| location_id | integer | – | Location id (from gingr_list_locations). |
| offset | integer | – | Skip this many records (paging; default 0). Use next_offset from the previous page. |
No output schema declared.
No examples provided.
gingr_list_invoices List invoices or estimates ~197
List invoices (complete=true) or estimates (complete=false, Gingr's default) created on or after 2019-08-01, optionally closed only and by date range. Paged by Gingr: per_page + start (the 1-based number of the first result; the next page starts at start + per_page). Gingr: GET /api/v1/list_invoices.
| Name | Type | Req | Description |
|---|---|---|---|
| closed_only | boolean | – | true = only closed invoices. |
| complete | boolean | – | true = invoices; false (default) = estimates. |
| from_date | string | – | From date (YYYY-MM-DD). |
| per_page | integer | – | Results per page (1-100, default 25). |
| start | integer | – | 1-based number of the first result (default 1; page 2 of 25 = 26). |
| to_date | string | – | To date (YYYY-MM-DD). |
No output schema declared.
No examples provided.
gingr_list_locations List locations ~56
List the locations (facilities) of this Gingr app, as id (value) + name (label). Good first call: most other tools take a location_id. Gingr: GET /api/v1/get_locations.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gingr_list_new_modified_owners List new or changed owners ~137
List the owners (customers) created or modified between two dates (at most 366 days apart). Paged. Gingr: POST /api/v1/new_modified_owners.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | Last day (YYYY-MM-DD). |
| limit | integer | – | Records per page (1-200, default 50). |
| location_id | integer | – | Only owners whose home location is this location id. |
| offset | integer | – | Skip this many records (paging; default 0). Use next_offset from the previous page. |
| start_date | string | yes | First day (YYYY-MM-DD). |
No output schema declared.
No examples provided.
gingr_list_owner_reservations List an owner's reservations ~241
List the reservations of one owner (customer), optionally only pending requests, current, future, past or wait-listed ones, by dates, types or pets. Only the location the API user is logged into is included (Gingr). Gingr: POST /api/v1/reservations_by_owner.
| Name | Type | Req | Description |
|---|---|---|---|
| animal_ids | array | – | Only these animal (pet) ids. |
| cancelled_only | boolean | – | true = only cancelled reservations. |
| completed_only | boolean | – | true = only completed reservations. |
| confirmed_only | boolean | – | true = only confirmed reservations. |
| from_date | string | – | Only reservations from this date (YYYY-MM-DD). |
| limit | integer | – | Return at most this many reservations (1-200, default 50). |
| owner_id | integer | yes | Owner id (from gingr_list_owners / gingr_get_owner). |
| reservation_type_ids | array | – | Only these reservation type ids (from gingr_list_reservation_types). |
| restrict_to | string | – | Only reservations in this state. |
| to_date | string | – | Only reservations up to this date (YYYY-MM-DD). |
No output schema declared.
No examples provided.
gingr_list_owners List owners (customers) ~204
List owners (pet parents / customers) with contact details, balance and reservation counts, optionally filtered by exact first/last name, email, cell phone, ZIP or home location. Paged. Gingr: GET /api/v1/owners (filters as params[<field>]). Passwords and payment-card references are removed.
| Name | Type | Req | Description |
|---|---|---|---|
| cell_phone | string | – | Exact cell phone as stored in Gingr, e.g. (555) 555-5555. |
| string | – | Exact email address. | |
| first_name | string | – | Exact first name. |
| home_location | integer | – | Home location id. |
| last_name | string | – | Exact last name. |
| limit | integer | – | Records per page (1-200, default 50). |
| offset | integer | – | Skip this many records (paging; default 0). Use next_offset from the previous page. |
| zip | string | – | Exact ZIP / postal code. |
No output schema declared.
No examples provided.
gingr_list_reference List reference data ~173
List one kind of reference data of this Gingr app: species, breeds, temperaments, vets (veterinarians with details), retail_items (retail items for sale) or immunization_types (of one species; needs species_id). Paged. Gingr: GET /api/v1/get_species | get_breeds | get_temperaments | get_vets | get_all_retail_items | get_immunization_types.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | Which list to read. |
| limit | integer | – | Records per page (1-200, default 50). |
| offset | integer | – | Skip this many records (paging; default 0). Use next_offset from the previous page. |
| species_id | integer | – | Species id (needed for kind=immunization_types). |
No output schema declared.
No examples provided.
gingr_list_report_card_files List recent report card files ~79
List recently uploaded report card files (photos and videos shared with pet parents), newest first. Gingr: GET /api/v1/report_card_files.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Return at most this many files (1-200, default 50). |
| location_id | integer | – | Location id (from gingr_list_locations). |
No output schema declared.
No examples provided.
gingr_list_reservation_types List reservation types ~86
List the reservation types (services such as boarding, daycare, grooming, training) with their ids. Use the ids to filter reservations or to read a type's add-on services. Gingr: GET /api/v1/reservation_types.
| Name | Type | Req | Description |
|---|---|---|---|
| active_only | boolean | – | true = only active reservation types. |
| id | integer | – | Only this reservation type id. |
No output schema declared.
No examples provided.
gingr_list_reservations List reservations in a date range ~163
List all reservations (boarding, daycare, grooming, training…) between two dates, at most 30 days apart (Gingr's limit). Paged: total, next_offset, items. Gingr: POST /api/v1/reservations (checked_in=false).
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | Last day (YYYY-MM-DD), at most 30 days after start_date. |
| limit | integer | – | Records per page (1-200, default 50). |
| location_id | integer | – | Location id (from gingr_list_locations). |
| offset | integer | – | Skip this many records (paging; default 0). Use next_offset from the previous page. |
| start_date | string | yes | First day (YYYY-MM-DD). |
No output schema declared.
No examples provided.
gingr_list_services_by_type List add-on services of a reservation type ~86
List the additional services (add-ons) allowed for a reservation type, e.g. baths or nail trims on a boarding stay. Gingr: GET /api/v1/get_services_by_type.
| Name | Type | Req | Description |
|---|---|---|---|
| location_id | integer | – | Location id (from gingr_list_locations). |
| type_id | integer | yes | Reservation type id (from gingr_list_reservation_types). |
No output schema declared.
No examples provided.
gingr_list_subscriptions List subscriptions (packages) ~175
List recurring subscriptions (membership packages), optionally of one owner, location or package, by billing day, including cancelled ones if asked. Paged by Gingr (limit + offset). Gingr: GET /api/v1/get_subscriptions.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_day_of_month | integer | – | Only subscriptions renewing on this day of the month. |
| include_deleted | boolean | – | true = include cancelled/deleted subscriptions. |
| limit | integer | – | Records per page (1-100, default 50). |
| location_id | integer | – | Location id (from gingr_list_locations). |
| offset | integer | – | Skip this many records (paging; default 0). Use next_offset from the previous page. |
| owner_id | integer | – | Only this owner's subscriptions. |
| package_id | integer | – | Only this package. |
No output schema declared.
No examples provided.
How do I install the Gingr MCP by usefulapi server?
Gingr MCP by usefulapi is a hosted endpoint at https://gingr.usefulapi.io/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 · gingr.usefulapi.io
claude mcp add --transport http io-usefulapi-gingr 'https://gingr.usefulapi.io/mcp'
What is the Gingr MCP by usefulapi server?
Gingr MCP by usefulapi is listed in the public MCP registry as io.usefulapi/gingr. Read Gingr reservations, owners, pets, check-ins, invoices and timeclock for your pet-care business. This page covers its hosted endpoint (https://gingr.usefulapi.io/mcp).
Is the Gingr MCP by usefulapi server safe to use?
Gingr MCP by usefulapi scores 68 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 Gingr MCP by usefulapi server expose?
Gingr MCP by usefulapi exposes 25 tools: gingr_list_locations, gingr_list_reservation_types, gingr_list_services_by_type, gingr_list_reference, gingr_list_reservations, and 20 more. Their descriptions and schemas cost roughly 3,040 tokens of context every time the server is loaded.
Does the Gingr MCP by usefulapi server require authentication?
Yes. Gingr MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Gingr MCP by usefulapi server still maintained?
Gingr MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.