Pinsvit
connectspinsvit.com
Find and book local businesses on the Pinsvit map; discover and create posts, events and comments.
https://pinsvit.com/api/v1/mcpWebsiteOAuthMCP 2026-07-28v1.16.0last checked 4 Nov 2026spoke MCP on 100% of 88 checks (30 days)initialize in 204 msLast checked 4 Nov 2026
- ✓Answered the MCP handshake (MCP 2026-07-28)
- ✓Auth detected: OAuth
- ✓Lists 32 tools
- ✓No blockers or warnings
- ✓Spoke MCP on 88 of 88 checks (30 days)
Will my client connect?
Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.
✓Claude CodeConnects with setup
The registration flow this server advertises is not one Claude Code documents, so register a client with the issuer yourself and give Claude Code the client ID.
claude mcp add --transport http --client-id <your-client-id> --client-secret --callback-port 8080 pinsvit https://pinsvit.com/api/v1/mcpClaude Code docs · read on 2026-08-30
✓Claude (claude.ai & Desktop)Connects with setup
The registration flow this server advertises is not one Claude (claude.ai & Desktop) documents, so register a client with the issuer yourself and give Claude (claude.ai & Desktop) the client ID.
Settings → Connectors → Add custom connector, then paste https://pinsvit.com/api/v1/mcp. Under Advanced settings, enter the OAuth Client ID and Secret the issuer gave you.
Claude (claude.ai & Desktop) docs · read on 2026-08-30
✓ChatGPTConnects
The authorization server supports Client ID Metadata Documents, so ChatGPT identifies itself by URL with no registration step.
Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://pinsvit.com/api/v1/mcp.
ChatGPT docs · read on 2026-08-30
✓CursorConnects with setup
The registration flow this server advertises is not one Cursor documents, so register a client with the issuer yourself and give Cursor the client ID.
{
"mcpServers": {
"pinsvit": {
"url": "https://pinsvit.com/api/v1/mcp"
}
}
}Cursor docs · read on 2026-08-30
✓VS Code (Copilot)Connects with setup
The registration flow this server advertises is not one VS Code (Copilot) documents, so register a client with the issuer yourself and give VS Code (Copilot) the client ID.
{
"servers": {
"pinsvit": {
"oauth": {
"clientId": "<your-client-id>"
},
"type": "http",
"url": "https://pinsvit.com/api/v1/mcp"
}
}
}VS Code (Copilot) docs · read on 2026-08-30
How to authenticate
Checked against the endpoint by our probe on 4 Nov 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | OAuth |
|---|---|
| Issuer | https://pinsvit.com |
| Dynamic client registration | ✕Not advertised |
| Client ID Metadata Document | ✓Supported A client identifies itself by a URL to its own metadata, so no registration step is required. |
| PKCE | ✓S256 |
| Grant types | authorization_code, refresh_token |
| Scopes | account |
| Protected-resource metadata | ✓Published (RFC 9728) |
| Anonymous access | Handshake succeeds; 32 tools listable |
| Documentation | https://pinsvit.com/auth.md |
What the probe found
A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.
The server exposes a public surface before authorization: accept_booking, add_booking_note, cancel_booking, create_booking, create_comment, create_event, create_post, decline_booking, delete_comment, delete_post, find_booking_times, find_place_customers, get_booking, get_booking_bill, get_comments, get_current_country_code, get_current_user_details, get_month_availability, get_place, get_place_services, get_post, get_publishing_media_keys, list_my_bookings, list_my_places, list_place_booking_requests, list_place_bookings, mark_no_show, ping, record_bill_payment, search_events_near, search_places, search_posts_near.
Neither the reserved <endpoint>/server-card location nor the domain's /.well-known/ai-catalog.json describes this endpoint (SEP-2127), so a client that discovers servers by domain will not find it.
Tools
Contract history
Breaking: get_place
Instructions rewritten: get_place, get_place_services, search_places. The description an agent follows changed; the callable contract may not have.
Instructions rewritten: create_booking. The description an agent follows changed; the callable contract may not have.
Breaking: search_places
Instructions rewritten: search_places. The description an agent follows changed; the callable contract may not have.
Instructions rewritten: create_comment, create_event, create_post. The description an agent follows changed; the callable contract may not have.
Instructions rewritten: search_places. The description an agent follows changed; the callable contract may not have.
Instructions rewritten: search_places. The description an agent follows changed; the callable contract may not have.
Instructions rewritten: search_places. The description an agent follows changed; the callable contract may not have.
Instructions rewritten: accept_booking, create_booking, list_my_places. The description an agent follows changed; the callable contract may not have.
Breaking: search_events_near, search_posts_near
Instructions rewritten: create_comment, create_event, create_post, get_comments, get_current_country_code, get_current_user_details, get_post, get_publishing_media_keys, ping, search_events_near, search_posts_near. The description an agent follows changed; the callable contract may not have.
Watch this server
Save its public contract as a baseline and manage breaking-change email alerts.
Set up a watchRoute it through the gateway
Put this endpoint behind one find_tools / call_tool pair with the rest of your servers. Part of Pro.
Add to my gatewayOwn this server?
Sign in to claim this listing by proving control of its host.
Sponsor this listing
Pins it in a sponsor slot on the directory front page for 30 days, labelled Sponsored.
Sign in to sponsor · $59 / 30 daysStatus badge
Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.
[](https://mcpi.app/servers/pinsvit)<a href="https://mcpi.app/servers/pinsvit"><img src="https://mcpi.app/servers/pinsvit/badge.svg" alt="MCP status" height="20"></a>